yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] retiredtab:
Thanks for reporting back. I added this one line to the installation instructions in post #1.

"You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP."

PS. If you want to use my 18.1 T710 rom, it's over at

https://xdaforums.com/t/unofficial-rom-beta-lineageos-18-1-for-sm-t710-may-12-2022.4430339/
[Galaxy Tab S2 Android Development] cammykool:
Thank you! That was actually the plan! Running it now and posted in the other thread!
[Galaxy Tab S2 Android Development] laolang_cool:
Thank you for nice work, I've installed it on my T715, it works very well, just now my device is recognized as T710 too. Could you please provide a build for T715? As the function of adb/mpt doesn't work on all of twrp for T715 too.
[Galaxy Tab S2 Android Development] keyap:
Was running LoS 16 and decided to update. Went to stock 7.0 then LoS 18.1 using this version of TWRP without any problems or the issues some other versions of TWRP have! Thanks 👍
[Samsung Galaxy Note 9 Questions & Answers] Bones519:
I went into my recent files folder on my note 9 today in my file explorer and found several zip files every hour named SAEmergencyJsonFile followed by a string of numbers. Each one containing a bunch of private documents and their actual location is

/storage/emulated/0/Android/data/com.samsung.accessory.contacts/send/SAEmergencyJSONFile1649682077396.zip

There are also some SALogsJsonfile zips in

/storage/emulated/0/Android/data/com.samsung.accessory.contacts/send/SALogsJSONFile1649701311871.zip

And the same as above only with _REQUEST.zip at the end.

I've never seen this before. Is it something I need to be worried about?
[Galaxy Tab S2 Android Development] retiredtab:
Initial public build called lineage-18.1-20220411-UNOFFICIAL-gts28wifi.zip. The sha256sum file is provided as well to ensure integrity of download.

lpedia has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

April 11, 2022

1. YOU MUST read posts 1-4 if you haven't already

2. First public BETA release of selinux enforcing T710 build.

3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04

4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ Q11.
[Galaxy Tab S2 Android Development] ananjaser1211:
Congratulations on the awesome release!
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-18.1-20220512-UNOFFICIAL-gts28wifi.zip

lpedia has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

May 12, 2022 release notes

1. YOU MUST read posts 1-4 if you haven't already

2. Added overlay for led capacitive led buttons as per https://github.com/retiredtab/andro...mmit/83551570e4627a0e353e358787f83aa65484b528

3. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05

4. If you are upgrading from the April 11 build, you may dirty flash the May 10 build. If you are NOT coming from the April 11th, 2022 build, you MUST BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA. You cannot dirty flash at all. See FAQ Q11.
[Galaxy Tab S2 Android Development] kimrosebush:
Hi there, thanks for your ROM. I would like to report a bug with using it.

May 12, 2022 release "lineage-18.1-20220512-UNOFFICIAL-gts28wifi" with "open_gapps-arm-11.0-pico-20220503".

All factory resetted through TWRP, after flashing and booting the device it is stuck on "Just a sec..." when selecting set up offlie. If you try to set it up over wifi it is stuck on "Getting your tablet ready."

I've included my logcat, if you need more info or another reproduction please let me know.

Thanks!

Kim
[Galaxy Tab S2 Android Development] lpedia:
Hi, @kimrosebush. Thank you for sending a logcat.

This kind of problem is often because the gapps package isn't quite right for some reason. Google Setup needs the underlying Google Play services to be present and working properly. This line from your logcat suggests they are not:

05-12 22:29:54.077 4147 4225 W GooglePlayServicesUtil: com.google.android.setupwizard requires Google Play services, but they are missing.

A few questions about the process you followed:

1. What OS was on the T710 before you began? If it was stock Android, was it the latest version available?

2. Did you install the correct version of TWRP (see Q5 in the FAQ)?

3. When you say "All factory resetted through TWRP", what did you actually do?

4. When did you install the gapps package? Just after the ROM, before first boot?

Have you checked whether everything else is working? In particular, is wifi connecting and working properly? [Pressing the Home button should get you out of the stuck Google Setup.]
[Galaxy Tab S2 Android Development] kimrosebush:
Hey @lpedia thanks for the reply.

1. LineageOS 17.1 I believe was the build.

2. Yes I installed the provided version.

3. I formatted all partitions except SD, flashed the images and then formatted the SD to ensure a completely wiped device.

4. Just after the ROM.

I tried a few times further, then I decided to go for the 'full' OpenGApps package; once I used this one and attempted the offline setup again I was able to proceed further in configuring the tablet.

Thanks for the hint in the right direction. :) Am glad to be on Android 11 now.

Kind Regards,

Kim
[Galaxy Tab S2 Android Development] retiredtab:
I will be removing opengapps from the FAQ because for several months now (starting around Oct 2021), the opengapps project has been releasing UNTESTED builds that results in bootloops or non working gapps services. Despite numerous requests/posts from the community to slow down the releases and actually TEST THEM BEFORE release, the latest May 3, 2022 shows there is still room for improvement.

This thread in the opengapps forum is just the latest example. Details of UNTESTED builds are also in the same megathread below.

https://xdaforums.com/t/gapps-daily...rsions-devices.3098071/page-367#post-86885091

It's also shown up in other roms like

https://xdaforums.com/t/exynos-unofficial-lineageos-17-1-04-30-2022.3937956/page-100#post-86885353

This would be a good time for user to do their own research on which gapps is best for them or use NONE at all. I use Aurora Store myself.

Just a reminder that the builds we release are TESTED and verified to have all the functionality as listed in post #1.
[Galaxy Tab S2 Android Development] lpedia:
Good to hear!

Note that you don't have to be quite so brutal about wiping absolutely everything for a 'clean' flash. I manually wipe Dalvik / ART Cache, Cache, and System, and then Format Data. I have never reformatted the SD.

If you have any further trouble, I suggest you try starting again with a clean flash and a different gapps package, or try doing without any gapps, as @retiredtab has recommended in the post above.

In my experience, some gapps packages, or sometimes just a particular version of a gapps package, don't work with some ROMs. I have not tried opengapps, but I can confirm that BiTGApps-arm-11.0.0-R45_signed.zip does work on my T710 with this particular ROM version.

I personally like BiTGapps because it installs only the bare minimum needed (Google services and Play Store; doesn't even automatically run Google Setup) and doesn't have to be installed before first boot. So it's possible to install LOS, boot the system, make sure everything's working, then go back into TWRP and install gapps. If any problems turn up, this approach also makes it easier to tell whether it's something to do with LOS or with gapps.

You could also try running LOS without any gapps, and if you decide you want gapps after all, install BiTGapps without having to clean-flash and start again. 🙂
[Galaxy Tab S2 Android Development] Dr_MC:
I just installed this rom two days ago. It has been working great. Today, however, I noticed that Trust gave me a message about the build having public keys. Yesterday, I don't recall getting that message. Also, root checker says "root access is not properly installed." The last time I checked, it was not rooted. Finally, my CRAVE (a Canadian streaming service) app won't play videos but gives a "device is rooted" message. Netflix works however.

Would you have any idea what is going on or how I should deal with this?

Thanks,

MC
[Galaxy Tab S2 Android Development] retiredtab:
On April 6, @lpedia and I had a PM discussion about signing builds.

lpedia wrote

"About signing builds ... an issue with just using the default test-keys signature is that someone can easily create
their own builds and pass them off as someone else's, possibly adding malicious or just plain bad code, and their
package would look just like the original."

I replied

"For our purposes, maybe we should just include the sha256sum and recommend that the users verify
them to ensure the file downloaded correctly and it wasn't modified?"

To get stop seeing that trust message, goto settings, privacy, trust, turn off build signature.

I can't see the Crave app in Aurora Store. I use the app devcheck to check for root access and the screenshot clearly shows it's not rooted.

There's nothing in my code to enable root. In fact, I don't even want root on my devices.

For Crave, you can try using Magisk and it's hide root function to see if that will fool Crave into thinking the device is not rooted.
[Galaxy Tab S2 Android Development] retiredtab:
I did installed the above root checker app and got the same message. That is, the T710 rom, by default is NOT rooted. I don't know why Crave would say it's rooted.

I believe root checker's main function is to verify that your rom is "rooted" so when it says "root access is not properly installed.", it's trying to tell you that your attempt to use Magisk or similar type app to root the rom was unsuccessful.

BTW, you are better off using devcheck as it's an excellent ad-free utility that I use on a regular basis to help develop this rom vs the ad-infested root checker app. While devcheck isn't open source, it's written by flar2 who is a xda member here.
[Galaxy Tab S2 Android Development] lpedia:
Root Checker Basic says "Sorry! Root access is not properly installed on this device" when asked to confirm root status on an unrooted device. So as far as that app's concerned, it just means "I can't confirm it's rooted". Which is to be expected if it isn't rooted and you haven't even tried to root it.

If that isn't the app you're using, see if you can find out what it means to your particular root-checker app.

Did the CRAVE app work on this device when it had the stock Samsung ROM? Do you have to register devices to receive this service? If so, might it need to be re-registered? Because its device ID will have changed.
[Galaxy Tab S2 Android Development] Dr_MC:
Thanks for suggesting devcheck. It says I'm unrooted. Perhaps Crave noticed the unlocked bootloader or the custom ROM.
[Galaxy Tab S2 Android Development] Dr_MC:
It did work with stock. It was registered, twice in fact. I deleted both, registered it again. The ap still says I'm rooted. Oh well, that's ok, I can use crave through a browser.

BTW do you know where I can find the stock keyboard?

Thanks
[Galaxy Tab S2 Android Development] lpedia:
If you mean the Samsung keyboard - sorry, no, I don't. I switched to a different keyboard years ago. Google's GBoard has similar functionality, I think. MS SwiftKey is OK, too - has the best (most relevant) suggested text of any of the keyboards I've tried.
[Galaxy Tab S2 Android Development] keenick:
ROM working fine for me after trial and error with various gapps. FWIW I ran into the "just a sec " with opengapps. I finally had some joy by flashing the rom, but not gapps. Boot the ROM and completely setup it up Lineage. Then I restarted and flashed open gapps. When I rebooted everything came uo fine and has been solid eversince. Kudos your you gentlemen for fixing the Wifi ! Its been nice to have it work stably.
[HTC Oxygen] loebis:
My brother give me Xda Neo with Germany language. Is it possible to upgrade my Xda Neo to WindowsMobile 6.0 or 6.1 with english language? I hope for somebody help me. :)
[HTC Oxygen] FLORINOX:
you are in the wrong place. you should go here : http://xdaforums.com/forumdisplay.php?f=250 . your phone is htc prophet
[Android General] hachelfig:
thank you for this tutorial I routed my phone but I have orange state at each start which lasts 30 seconds then starts normally what is the problem please and thank you again
[Android General] AdalisVaxeler:
I've tried to find more about that because it kinda annoyed me too, but at the end, it seems to be some sort of "indicator" that you were able to successfully unlock your phone's bootloader. In any case, I'll keep searching and the guide will be updated if I find a way to remove that message.
[Android General] hachelfig:
I used this tutorial https://www.droidwin.com/how-to-remove-red-and-orange-state-warning-in-mediatek-devices/ and it works well thank you
[Android General] mrprefect:
Which vbmeta.img file am I using, when I unpac the file there are:

vbmeta_product.img

vbmeta-sign.img

vbmeta_system.img

vbmeta_sysem_ext.img

vbmeta_vendor.img

Which one should I be using to root?
[Android General] Smollky:
Oops galeta, would it not have a custom rom or GSI compatible with the Umidigi A11 pro max? I've been looking for something like this for days and I haven't found anything like this, do you know something like this?
[Android General] Patrickcnnp:
Usei este método! porém meu smatphone morreu! não da sinal de nada
[Android General] Patrickcnnp:
Foi tudo coreto! ai dei o FASTBOOT REBOOT e não liga mais
[Android General] marisaleh:
I am just wondering if anybody has managed to root the

Umidigi A13 Pro Max 5G
[Android General] Patrickcnnp:
Ainda não tive êxito!
[Android General] Mchlbenner51:
UMIDIGI A13 Pro Max 5G is it a dual slot device?
[Android General] marisaleh:
Be aware guys,

I followed the same procedure above to root UMIDIGI A13 Pro Max 5G

I adapted the procedure to my phone, obviously

It didn't work, ended up with a completely damaged phone.

The only way to recover it was to flash it with the SPFT tool

using firmware mode of flashing,,,

I am just wondering if anybody has managed to

root UMIDIGI A13 Pro Max 5G YET....
[Android General] Mchlbenner51:
I believe this might be a dual slot device this work only if it is.
[Android General] marisaleh:
Yes you are right I have just confirmed that using Treble Check app,

it is a dual slot device.

I will now give it another go, and report back

Thanks for you help
[Android General] marisaleh:
Yes Yes Yes

I have just finally succeeded in rooting the Umidigi A13 Pro Max 5G

Yes it is a dual slot device

I rooted it using this simple procedure:

flashed the latest stock rom from Umidigi

Patched boot.img using the latest version of Magisk Manager (magisk_patched.img)

With the phone unlocked and in fastboot mode, I run the following:

fastboot flash boot magisk_patched.img

Fastboot flash vbmeta vbmeta.img

fastboot set_active a

fastboot reboot

The phone rebooted, I completed Magisk install

I now have full root

The orange state warning that pops up on reboot is annoying

and I don't know how to get rid of it yet.

I will be grateful if anyone can help!!!
[Android General] Mchlbenner51:
Does it say your bootloader is unlocked!
[Android General] marisaleh:
It says your device has been unlocked

and cannot be trusted

I'll be grateful if you can help me

get rid of it, it's annoying
[Android General] Mchlbenner51:
I don't have this phone yet l.

I was pretty sure how to root it so left directions on how to do that.

I would for know l would leave it alone.

When get this phone I will see what I can do about that.

Do not try the remedy that is in this post it could brick your phone.
[Android General] marisaleh:
Thank you very much

I have rooted it with your help

You can see the procedure I

Followed, it's really easy

It's the orange state warning that

I don't know how to remove

I'll wait for you help on that
[Android General] marisaleh:
Good news, I have just managed to remove the orange state warning

Used a Hex editor, modified the stock lk.img and flashed it in fastboot

fastboot flash lk lk.img

Very simple worked perfectly

I am still having a problem with changing selinux mode from

Enforcing to permissive.

I have tried all existing methods and workarounds

I even tried terminal commands like getenforce and setenforce

Nothing will work to change it to permissive

I think it's android 12 security

I will be grateful if anybody can help

Some mods like viper4android will only work if

selinux is in permissive mode
[Nubia Red Magic 6S Pro] S3XY#TSLA:
Hi there

I'm on 3.15 and I was prompted with a new update (weird already as when it prompted it said 3.15 again instead of 3.18 or 3.20). I tried to click download and install but after 5 seconds of not going past 0% it would just go back to the same "Download and update" button. I even got the download on my notification bar still showing 0%...

So I decided to check how to do it manually (yes I backed up everything already) but realized the three dots aren't even here to try to flash it?

Any suggestions on how I am supposed to flash the new version?

View attachment 5585317View attachment 5585319
[Nubia Red Magic 6S Pro] Terrorigel97:
Easy

First download the Activity Launcher

Search for "System-Update" click on it and then "Local-Update" then you can manualy update your phone
[Nubia Red Magic 6S Pro] S3XY#TSLA:
I did that, (didn't need to download as was already installed) it opened exactly the same thing as in the screenshots and behaved the same way.

Edit: Nevermind I think I found it. Just searched for "local update".
[Nubia Red Magic 6S Pro] Terrorigel97:
I'm glad I could help you :)
[Nubia Red Magic 6S Pro] S3XY#TSLA:
With so much excitement I forgot to thank you, so thank you!

Hope you're well, kind regards
[Xiaomi Mi A1 Questions & Answers] mtenseven:
I request all those who are using the Indian Version of MI A1, Please give me the original 00028874 bin file as I deleted it by mistake, I will be really thankful to anybody who helps.
[Black Shark 4] nilzwsx:
I have the same issue from the past update and it does not fix with the mp5 update. I can not make the bluetooth to Auto Connect with any kind of earphones. I already restarted the setting, clear the cache and data but still the same. Anyone have a solution for this?
[Galaxy Tab S2 Android Development] retiredtab:
Initial public build called lineage-18.1-20220410-UNOFFICIAL-gts210wifi.zip. The sha256sum file is provided as well to ensure integrity of download.

Yogi555 has tested all the functionality as to what works as per post #1 before uploading the build. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

April 10, 2022

1. YOU MUST read posts 1-4 if you haven't already

2. First public BETA release of selinux enforcing T810 build.

3. Incorporates April 5th security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04

4. BACKUP your data because YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA after as this is the first release of this build. You cannot dirty flash at all. See FAQ Q11.
[Galaxy Tab S2 Android Development] dcaffeine8d:
Tried the beta build and everything seems to be working. I'll observe once it goes into deep sleep and see if WiFi will lose connection (usually 24 hours) on the other 18.1 build. Loaded all my paid apps without issues. Only gripe is the Netflix with DRM L3. Will look into another thread where they spoofed it.
[Galaxy Tab S2 Android Development] leendert47:
I'll give it a try. Other LOS 18.1 roms wifi not working.
[Galaxy Tab S2 Android Development] bmwdroid:
@retiredtab, @ananjaser1211, @lpedia, @Yogi555 and @CuckooPenguin thx very much for your work.

Until yesterday mine was on ripees build from 20211103 which was stable and working but didn't seem to get any further updates than 20211208.

Clean installation went well although I didn't follow "Q5" and used latest TWRP which is 3.6.1_9-0.

Flashed it with Magisk 23. (wanted to make sure that Gapps didn't interfere)

1st boot was fast, setting it all up.

Looking in settings for button backlight duration but didn't find it (using it in the night and want them to light up as short as possible).

Wifi connection there as soon as it wakes up.

So I gave BitGapps a go and flashed ARM64 which worked (isn't specified in "Q12" and as far as I remember only ARM worked on ripees build).

Fiddling around a bit installing paid apps and others.

Everything seems to be fine especially for a beta version.

For others who want to change from ripees version to this one:

On mine it worked to restore "Data" via TWRP (partition got wiped again before) what makes it much easier to switch.

Each app I use seems to be working under the new ROM without problems.

Fun fact: button backlight after restoring is as short as it was set in the prior ROM.