yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Original Android Development] tech_user_here:
Good day, new user here..

My device is Samsung Galaxy Tab 4 SM-T530 running on stock android 4.4.2, with build number KOT49H.T530KXU1ANG5.

Using Odin 3.14.1, done installing TWRP, twrp-3.7.0_9-0-matisse.img..

Installed lineage-18.1-20231023-UNOFFICIAL-matissewifi.zip, first without gapps, stuck on boot screen with the words

Set Warranty Bit: kernel

on the top left. Stuck in boot screen for hours, so I decided to repeat the steps this time, with gapps, still stuck in boot screen with the words Set Warranty Bit: kernel..

Using Odin, I flashed the stock rom, the tablet boot normally like nothing happened.

So I repeated the steps, still used twrp-3.7.0_9-0-matisse.img, flashedlineage-17.1-20231018-UNOFFICIAL-matissewifi.zip. still stuck in boot screen with

"Set Warranty Bit: kernel".

Went back to stock rom, flashed same twrp-3.7.0_9-0-matisse.img and used lineage-16.0-20230718-UNOFFICIAL-matissewifi.zip, still with stuck boot screen...

All of those steps repeated, from flashing the custom ROM to stock rom, but using

twrp-3.5.2_9-0-matisse.tar, then

twrp-3.6.0_9-0-matisse.tar, with still same results..

Stock rom working on the tablet, however apps are no longer supported, and browsing thru chrome or Samsung browser happens to to problematic, since it can no longer load websites. So best choiceis to install custom ROM.

Please help.

Thank you guys.
[Galaxy Tab 4 Original Android Development] Dan TBA:
Well, try clearing the Data, Dalvik Cache, Cache and System partitions (NOT INTERNAL STORAGE, it will remove all of your local files like documents, pictures and downloads!) in Wipe > Advanced Wipe when before and after trying to install a custom rom. It works for me and I have not went in bootloop when installing the latest 16.0 lineageos for my Galaxy Tab 4 10.1 3G (matisse3g) with Twrp 3.7.0_9.0-matisse.zip. Hope this little trick solves ypur bootlooping problem.
[Galaxy Tab 4 Original Android Development] Sisqo:
What I’m am i doing wrong? Any thoughts? Thanks
[Galaxy Tab 4 Original Android Development] T4V0:
You must install the official Lollipop ROM first before flashing the custom ROMs. Find the one for your model here and flash it with Odin (I used the 3.13.3 version). Flash this version of TWRP, then wipe Data, Dalvik and Cache, flash the ROM and gapps, wipe Dalvik and Cache again and reboot into the system.
[Galaxy Tab 4 Original Android Development] tech_user_here:
@T4V0 thank you so much for pointing it out to me. My tablet now runs on Android 9.. I find to to be a little more responsive to use Android 9 than Android 11..

Maybe somebody might have the same problem like mine. Mine is Samsung Galaxy Tab 4 SM-T530 Korean version..

To flash custom ROM, you have to flash the Android 5 (lollipop) version using Odin v3.14.4. as pointed out by @T4V0, I downloaded Lollipop rom from this list. Despite being a Korean variant and not seeing Korea in the list, I was able to install the UK variant with no problem. After flashing the UK variant , I then flash TWRP V3.0.7.9, using this version.

Using TWRP, I then wiped "Data, Dalvik, and Cached". Then flashed Matteo0026's custom ROM found here, then flashed gapps.

Thank you so much for the help in giving life again to our old devices...

Long Live and Prosper Mate.

Take care. Cheers
[Galaxy Tab 4 Original Android Development] punkle:
do i have to root?

i set up a tab 4 for a friend to do some note taking on, (word / outlook) delighted with 18.1 so far, i havent flashed magisk and all seems ok. Will be using a bluetooth keyboard so thinking i will need to do the fix copying from stock but i havent the keyboard to test yet.

thanks for all the work
[Galaxy Tab 4 Original Android Development] matteo0026:
If you want root, you have to flash magisk, otherwise it can stay without.
[Galaxy Tab 4 Original Android Development] davestuarts:
Lineage 18.1 on my Tab4, amazing!!

Coming from 16, did a clean install.

I updated TWRP within TWRP.

Cleaned/cleared as per usual

Installed latest 18.1 (millet)

Installed open gapps pico-20210130-TEST

Installed magisk 23 as zip.

Waited a few minutes and boom! So far, runs as smooth as butter and fairly nippy considering the base specs and age.

I've only run/tested the basics. Installed Firefox&ublock and Mixplorer.

Thank you matteo0026 for keeping the device alive, really appreciate your efforts.
[Galaxy Tab 4 Original Android Development] macbroom:
I have been watching development on this for years and finally canned my old debloated stock 5.1 install.

Install went smoothly as I had older twrp (Philz touch) installed, new twrp, wipe, openGapp pico......bam.....android 11.

Runs well considering the old chipset. Great work Matteo!
[Galaxy Tab 4 Original Android Development] busa_blade:
I haven't been able to get the July build to start up. I am able to get the June build to start just fine. The July build just sits on the boot screen indefinitely.

No complaint, just feedback. Thank you for breathing life back into the dead tablet.
[Galaxy Tab 4 Original Android Development] matteo0026:
It works here, I've just done a clean install. I don't know why it boots, probably blame gapps. I know that this last build has been made by @crazydrive22, but it just works, it has been done as I do them.
[Galaxy Tab 4 Original Android Development] Achsel:
Tip: Simultaneous charging of the Samsung Galaxy Tab 4 tablet and a 3-way USB 2.0 HUB Ethernet adapter (tested only on the SM-T530 with 10.1")

1. Connect a modified OTG adapter:

I use a the OTG adapter ADAPTARE 40228 with additional female micro USB socket for external power supply. The micro USB male connector of the OTG Adapter has usually a solder bridge between PIN 4 (ID PIN) and PIN 5 (ground) to detect the OTG mode. Then you can only supply the USB device with power. Without the additional micro USB female socket the power directly comes from the tablets (phones) akku. If you solder in a resistor instead with approx. 80kOhm (specially for the Tab 4 tablet, for the Samsung Galaxy S4 phone 65kOhm) between PIN 4 and PIN 5 of the micro USB male connector, then you can supply the USB device and the tablet (phone) with power at the same time.

Because there is no solderable PIN 4 in the micro USB male plug of the ADAPTARE OTG adapter, I bought individual micro USB male plugs with all 5 pins for soldering.

https://www.amazon.de/40228-Adapter...icro-USB-2-0-gerade-Extra-Strom/dp/B00EJP5XR2

https://www.amazon.de/dp/B01G6OYTS2...88ad-322db71d5961&ie=UTF8&qid=1513864976&sr=1

2. Connect the USB 2.0 HUB Ethernet adapter:

I recommend the UGREEN adapter with 3x USB 2.0 ports (Ships from China, third choice, model no. 20264, ASIX AX88772 chipset for Ethernet), because the Tab 4 tablet (S4 phone) only supports USB 2.0, and "not" the USB 3.0 version (model no. 20265, ASIX AX88179 chipset for Ethernet), because there may be dropouts in the transmission. It may be too fast for the Tab 4 tablet (S4 phone). The required "ASIX" Ethernet driver is already activated in the LineageOS 18.1 kernel.

https://de.aliexpress.com/item/3240...earchweb0_0,searchweb201602_,searchweb201603_

3. Important for the Tab 4 tablet: Connect the charger at the end!

Otherwise the UGREEN adapter, all connected USB devices and the Ethernet connection will not be recognized. I don't know why that is. Maybe the OTG driver won't load. With the S4 phone, it doesn't matter when you connect the charger.

Goog luck with testing!

Axel
[Galaxy Tab 4 Original Android Development] matteo0026:
Crazy project! Congratulations!
[Galaxy Tab 4 Original Android Development] matteo0026:
New build of LineageOS 18.1 is online!

Changelog:

- August 2021 security patches

- For millet*: fixed inverted audio channels through jack
[Galaxy Tab 4 Original Android Development] Herschenglime:
Crazy timing, I just flashed TWRP to my device!

Are the links on android file host already updated, or should we wait a bit for the new builds to show up?

Thanks!

Edit: Oops, I didn't see the big download button.
[Galaxy Tab 4 Original Android Development] matteo0026:
Probably mirrors still have to create. Wait for some hours
[Galaxy Tab 4 Original Android Development] Herschenglime:
Is gesture navigation available in the settings for you? It doesn’t show up for me, but I’m not sure if it’s because that’s just how the rom is or if it has something do to with what I’ve added on top of it.
[Galaxy Tab 4 Original Android Development] matteo0026:
Probably, by using hardware buttons, those settings are disabled. To re-enable them, put in /system/build.prop file: qemu.hw.mainkeys=0 and software buttons and gestures settings should come up.
[Galaxy Tab 4 Original Android Development] Herschenglime:
That was it, thanks! The hardware buttons still work, too, which I wasn't expecting.
[Galaxy Tab 4 Original Android Development] MarCello61:
This is kinda exellent work :), thank you for bringing this to us !
[Galaxy Tab 4 Original Android Development] Achsel:
@matteo0026

My Device: Tab 4 with 10.1" (SM-T530), my installation: LineageOS 18.1, BiTGApps-arm-11.0.0-R28_signed.zip + BiTGApps-addon-tts-R16_signed.zip and Magisk-v23.0.zip installed via twrp-3.5.2_9-0-matisse.tar. Today I copied the lineage-18.1-20210808-UNOFFICIAL-matissewifi.zip to the external SD card, started the device to TWRP recovery, choosed "wipe/advanced wipe" and there only "cache", installed the update ZIP file of LineageOS, finally "wipe cache/dalvik" and restarted system. Then I had no problems, I just had to reinstall the LesserAudioSwitch app as expected. See my installation guide in the last post 20 on page 1. Important: I always do a full system backup before and after via TWRP.

PS: The "Updater" under "System/Advanced" does not work directly on the tablet. With the Samsung Galaxy S4 phone and LineageOS 18.1, however, the "Updater" also works on the device itself.

Thanks Axel
[Galaxy Tab 4 Original Android Development] Original Noob:
I tried to fix Bluetooth using ur method but it keeps crashing what should I do:unsure:
[Galaxy Tab 4 Original Android Development] Original Noob:
Thank u for the work your doing sir on SM-T531 I really appreciate it keep up the gud work
[Galaxy Tab 4 Original Android Development] matteo0026:
Wow, it was a lot of time since I've never heard this issue. So it has to stay there, confirmed. What if you try to do the same thing using LOS16?
[Galaxy Tab 4 Original Android Development] Houyhnhnm:
It runs very smooth!

But I'm having a weird issue with the Play Store. I can't install any app whatsoever, everytime I try it says there's not enough storage. I tried clearing cache and data in the Google Play Services and Play Store apps , rebooted but it doesn't work. I thought the problem were BitGapps so I went to TWRP, wiped system, data, cache, dalvik/art cache and internal storage, flashed the ROM again, then OpenGapps but it's still not working.

Any idea how to deal with this?
[Galaxy Tab 4 Original Android Development] matteo0026:
Just to know, which version of TWRP do you have?
[Galaxy Tab 4 Original Android Development] Herschenglime:
Would you be fine with rooting and using the Aurora store? I’ve had luck installing microg through flashing nanodroid after magisk and then following the steps here for android 11 to set up signature spoofing. Magisk says safetynet isn’t passed, but microg says it’s working and I was able to install and use the Netflix app.
[Galaxy Tab 4 Original Android Development] Mushroom22:
Hello, I'm using Lineage OS 18.1 on my Note 4, and I have an 8400mAh extended battery. I used a ZeroLemon kernel when I was on the stock ROM (Android 6.0.1), but it doesn't work anymore on Lineage 18.1 (Android 11). Do you have any tips to maximize the capacity of my battery? I feel like it's not really charging to 100%. Thank you. Any suggestions will be greatly appreciated.
[Galaxy Tab 4 Original Android Development] KORKKOKO:
I am using the Korean LGU+ SM-T335L model.

I am very satisfied with the firmware.

No Korean SIM

WIFI OK

Is there no way?

Korea (KT, SK, LGU+) SIM card recognition is required. It doesn't work.

Is there no way?

I look forward to your abilities.
[Galaxy Tab 4 Original Android Development] masoudlizard:
Hello

It is my tablet t531.

I installed lineage-18.1-20231023-UNOFFICIAL-matisse3g.zip.

But when I connect to Wi-Fi, it gives an error of limited connection.
[Galaxy Tab 4 Original Android Development] Catzy96:
Hello again @matteo0026, i was the one who asked you this in TWRP post,

[RECOVERY][3.7.0_9][UNIFIED][matisse*][millet*][rubenslte] TWRP Recovery

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...

xdaforums.com

So i've actually flashed it to 5.1.1 KSA build before with Odin 3.13.1, and my IMEI still did not exist in that one, any idea? like my IMEI and the sensors only exist in my 4.4.2 stock firmware, but when i tried to flash it to 5.1.1 and LOS or even crDroid which based on LOS they were gone... and FYI in my 4.4.2 i have the IMEI and my device can recognize my SIM card, but only emergency call, cannot use the service no matter how many SIM cards i tried, for the sensors, i installed AIDA64 on 4.4.2 and it shows all my sensors, tried *#0*# all sensors worked... but they are not exist in other roms
[Galaxy Tab 4 Original Android Development] matteo0026:
Try to flash stock firmware including pit file. If it doesn't fix, I don't know how to fix that. Try LOS 16 too.

Anyway, someone else reported that issue too, but since I don't have neither the time to debug the issue and another tab 4 with sim, I can't fix that.

This is a message for everyone, be careful and backup your EFS partition in TWRP before flashing these ROMs.
[Galaxy Tab 4 Original Android Development] Catzy96:
HI @matteo0026 , i actually backed up my 4.4.2 with TWRP before i flashed it to LOS 18.1, so i have all the data, including EFS files, i'm now in 4.4.2 again since i restored it to the previous state of my device. The only problem with this 4.4.2 now is the emergency call only, like i had on the very first time i reset this device to factory settings, but all the sensors work, i cannot test GPS since it requires me to update google services, which is not available anymore for 4.4.2.

i've tried to restore only EFS data with TWRP to my LOS 18.1 or 5.1.1 but no luck (idk if it's even gonna work at the first place), so do i need to try to flash it back with Odin to 5.1.1 including the pit file now?? and then i can try to flash any custom rom like LOS 18.1? actually i've tried LOS 16 too from your repo but it has the same results... Thank you again for helping, it's really frustrating, i mean it's not even my device, but my curiosity doesn't let me return this device to the owner with this issues even tho i think they wouldn't mind it haha

crazydrive22 from crDroid has been helping me too and suggested me to re-partition the device when i flash the stock rom but haven't tried it yet

[ROM][UNOFFICIAL][matisse][millet] CypherOS 11

This is Cypher. An extension to pure Android. Cypher tries maintain the purity of Android while offering useful features for users. The goal is to give the highest level of performance whilst achieving Simplicity. /* * Your warranty is now void...

xdaforums.com
[Galaxy Tab 4 Original Android Development] Catzy96:
Hello @matteo0026 , i've already succeeded in installing android 5.1.1 on this device with the re-partition method using the pit file, and my tablet can now recognize my IMEI and the sensors, even tho my grip sensor is not listed on AIDA64, i tested on *#0*# and it's working, so i tried google map on chrome and it can detect my location. The only problem left is that even though my IMEI exists now on 5.1.1, it's always in the emergency calls only state, the same problem with 4.4.2. When I tried to restart my device, it recognized my service provider for about 5 seconds and got back to emergency calls only. Do you know what is wrong with this?? i tried to manually select the service provider in settings, but with no luck. Thank you.
[Galaxy Tab 4 Original Android Development] matteo0026:
Can something be wrong with the CSC of the firmware you've flashed? Did you try to flash a firmware with the CSC of your country? Add some more details. That behavior sounds like the modem isn't working fine
[Galaxy Tab 4 Original Android Development] Catzy96:
so i'm from Indonesia, and i cannot find any stock rom 5.x for this region, so I installed the KSA 5.1.1 build from https://samfw.com/firmware/SM-T331 with the pit file. However, i had this emergency call issue even with 4.4.2 before which was the factory stock rom... what do you think???
[Galaxy Tab 4 Original Android Development] Catzy96:
Hi @matteo0026 , so i'm from Indonesia, and i cannot find any stock rom 5.x for this region, so I installed the KSA 5.1.1 build from https://samfw.com/firmware/SM-T331 with the pit file. However, i had this emergency call issue even with 4.4.2 before which was the factory stock rom... what do you think???
[Galaxy Tab 4 Original Android Development] Tchetlanin:
Hi. I have only 4 fonts in the settings on the sm-t331, how do I install additional fonts in Lineage OS 18.1?
[Galaxy Tab 4 Original Android Development] jakubm:
How to install on t-533?
[Galaxy Tab 4 Original Android Development] jakubm:
It any rom for mattisevewifi? I have this tablet but it very slow on stock, I tried to install LOS, but it didn't worked. I don't have system at this moment. It any custom, or back on stock?
[Galaxy Tab 4 Original Android Development] davestuarts:
Hi matteo0026, hope all is well. I was wondering if you're still updating these tablets?

I normally download updates from telegram but as nothing new was uploaded I came here. Thanks
[Galaxy Tab 4 Original Android Development] jason95:
Hi I'm From South Korea and I'm trying to install the latest(2023 Lineage18.1)for my Galaxy Tab 4 10.1(SM-T530)

and also My TWRP is Latest Version Now(3.7.0_9-0)

I followed your Install Instructions (Wipe=>Install)

but when Device is Booted It shows Factory Hard Reset Message Box and goes to Recovery mode automatically So I Reboot it and Repeats to Recovery mode infinite repetition Please Help with this....
[Galaxy Tab 4 Original Android Development] d_a_ugono:
Hi! I was on the February 2023 version and I tried to update to the October 2023 version (the latest version) using the OTA updater, and I was stuck in a bootloop then kept booting back to TWRP. I wiped System, Dalvik, and Cache, and tried to install the February 2023 version I had before, and I keep getting a signal 7 error: "Updater process ended with signal: 7". I then wiped Data along with Dalvik, Cache, and System, and reinstalled the February 2023 version, and I still keep getting the signal 7 error. Does anyone know how to fix this?
[Galaxy Tab 4 Original Android Development] Lequim:
Hi there!

First of all, a very big thank you for all the work supporting old devices!

I'm struggling and don't know what could be wrong. I installed the TWRP recovery but the ROM doesn't boot, actually, none ROM boots. I tried to downgrade TWRP a couple of version but no luck. It gets stuck in the boot image "Samsung Galaxy Tab 4 powered by android" and won't ever boot. Anyone knows what is happening? It's a galaxy tab 4 matisse LTE. I have searched for someone with the same issue with no luck :).
[Galaxy Tab 4 Original Android Development] d_a_ugono:
@matteo0026
[Galaxy Tab 4 Original Android Development] matteo0026:
Hi everyone,

I'm sorry I left you in the middle of nowhere with your asks, but I'm not having any time to follow this project. Even when I tried to make some updates, I've struggled a lot because I had some issues with every build. So... don't expect from me any new builds. I could come back suddenly in the future, but I can't promise this.

All the builds that I publish I know that they boot, and I really don't know why in your case they don't boot. My advice is to flash stock lollipop firmware and restart clean. You can also try the other ROMs not made by me. Bye!
[Galaxy Tab 4 Original Android Development] d_a_ugono:
Do you know how I can fix this "Updater process ended with signal: 7" error I've been getting when trying to install the February 2023 build I had before after uninstalling the October 2023 build (which didn't boot)? I even did a clean wipe and it didn't fix it. The February 2023 build is the only ROM file I have downloaded.
[Galaxy Tab 4 Original Android Development] retiredtab:
I just released a LineageOS 20 ALPHA build for SM-T530NU ONLY at

https://xdaforums.com/t/unofficial-...r-galaxy-tab-4-sm-t530nu-apr-14-2024.4667032/

YOU MUST read posts #1-4 BEFORE even deciding to try it.

I WILL NOT build anything else other than SM-T530NU as that is all I have.
[Galaxy Tab 4 Original Android Development] BeeJ1109:
I see LOS20 ROM for only SM-T530, what is required for SM-T330. Are they not similar with 10.1" screen vs 8.0" screen.

Would nice to have someone other than matteo0026, whom now appears to be too busy to now update from LOS 18.1 Development.

Thanks for ALL his efforts over the past years on ALL Mattisse & Millet Tab 4 models.

Cheers BJ.
[Galaxy Tab 4 Original Android Development] Enzo_P:
I have installed the lineage 16 (20220209) on my matisse wifi.

But the "Hey Google" isn't working.

The message says: "Hey Google is not supported on this device"

The is a built that it works? on any lineageOS 16, 17 or 18?

Thank you, i am trying to make a this tablet a smart device, to replace the Alexa.
[Galaxy Tab 4 Original Android Development] high_yield:
Hello,

I have a SM-T530 stock and need to find out what is the correct firmware to install, matisse or matissewifi?

matteo0026 says here that SM-530 is matisse, but there are plenty of posts on this topic where people say that they flashed matissewifi. I'm confused, please help me. Thank you.

Later edit: I've managed to do it. In the end, I used heimdall (under Linux) to write twrp image for matisse. After many attempts, I managed to boot into twrp (I'm not sure how, but eventually I did it). From twrp, i wrote the ROM for matissewifi and gapps ARM for Android 11 variant mini (anything larger failed due to lack of space). The tablet booted lineageos and I was able to complete the welcome wizzard.

Thank you for your work.
[Galaxy Tab 4 Original Android Development] matteo0026:
Yes, it should be fine. In Android 11, I don't know the reason why safetynet isn't passed. In 9 and 10 it's fine.
[Galaxy Tab 4 Original Android Development] Herschenglime:
Ah whoops, I had meant that as a suggestion in response to houyhnhnm since his play store wasn’t working, but I didn’t click the button to reply to his post.
[Galaxy Tab 4 Original Android Development] Houyhnhnm:
3.5.2_9-0
[Galaxy Tab 4 Original Android Development] matteo0026:
That's fine. Then... I really don't know which can be the problem. Me and other users never had this issue
[Galaxy Tab 4 Original Android Development] Houyhnhnm:
Thanks for the alternative, I didn't know about Aurora store. I'll try that in my own phone.

I flashed the files again, formatted the SD in FAT32 and as I chose to use it as internal storage, it throws this error:

Attempt to invoke virtual method 'java.lang.String android.os.storage.VolumeInfo.getId()' on a null object reference.

So for now I can install apps from the Play Store in the internal memory and I'll use the SD for external storage.
[Galaxy Tab 4 Original Android Development] matteo0026:
I think you won't be able to use sd as internal memory. But, do you really need to use SD card as internal storage? If not, it would just slow down the experience.
[Galaxy Tab 4 Original Android Development] cbouillot:
Hello

Congrats for this ROM. it is working fine. Ok a little bit slow but usable

The only issue I have is for the battery jauge that is not working properly.

Do someone encounter the same issue ?
[Galaxy Tab 4 Original Android Development] matteo0026:
"A little bit slow" because it's Android 11 too. If you try LOS 16 (Android 9), you'll see it's a little bit faster.

What do you mean by battery jauge? The percentage?