yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Zeh John:
Indeed it doesn't, I suppose as long as attention is paid to the setup wizard on a new installation, to make sure to not leave a dedicated option for updating recovery checked.

I've installed the newer version of LineageOS 18.1 over the old one and I've noticed that TWRP did NOT have an option to update Recovery...

My guess is (and I don't know if that will work or not), if needed, boot into TWRP afterwards and restore only the Recovery partition.

Also, going to the options menu in Lineage's updater from settings and disabling recovery updates there afterwards is an option.

This! This is very important.

Since I thought my older version of 18.1 would never get any new update, I've frozen the Updater. After upgrading to 19.1 and having no root, I had a lot of apps frozen that I could not unfreeze to use.

Now back on the latest 18.1 I've unfrozen the Updater and indeed there is that precious option. Thanks for bringing this to my attention.

Since it's the first time anyone encountered issues

Eheheh! Typical me stepping on crappy land no one ever stepped on... :]

My pleasure, and with your fix this is my tiny contribution to this project, since I can't code.

Lineage recovery was used officially on 18.1, so having it unset then was fine, but here since Android 12+ recoveries aren't fully functional, it has become relevant.

I've just finished backing up the December 2023 version of LineageOS 18.1 and soon will start experimenting with 19.1 better and there's a beta version of 20.0 with Android 14 for this device. Thanks for all this advice and I'll be paying closer attention to the Recovery thingy. Bumpy roads ahead for fun and testing but I think I'll remain on 18.1 unless I find a new GUI since I find the newer ones way to flashy and ADHD with things always jumping and moving around...

By the way, my 19.1 version was done with a dirty update and unrooted, but I've noticed the CPU speeds were always on deep sleep or, when used, almost at 1.6GHz even with power saving enabled (see attached printescreen), making the phone too hot and the old battery dropping very quickly, making the phone unusable outside home without power bank. With 18.1 it is much more cooler but slower, making the UI noticeably slower but making it a functional compromise having the phone only being charged 2 or 3 times a day with the original battery.

Cheers.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] PatoKuaKua271q:
Hello, how is it that there is an android 14 beta for this device? And where can I get it?
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Zeh John:
Hello, how is it that there is an android 14 beta for this device? And where can I get it?

EDIT: Do NOT use this ROM, it's not for this phone and you WILL brick it. Apologies for erroneously posting it here.

You can get it from here:

https://xdaforums.com/t/unofficial-lineageos-21-0-android-14.4649772/

I didn't read much from it but be aware:

- It's still in beta.

- From the last page of the thread, it seems Google has changed a lot of stuff lately that basically has broken portability to old phones. So I don't even know if there are available downloads that actually work.

So read the thread carefully and until the end before jumping into flashing. And, of course, have a reliable backup and tools if you need to do a restore. My last posts were a valuable lesson to me as I got stuck in a working but unrooted ROM without even the Play Store (my bad!) very fast and smooth but hot on my phone and draining the battery, and unable to boot into TWRP to restore my backup. Boy I'm glad I had a backup!

Cheers.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
Please be extremely careful with compatibility. That's for regular Galaxy S5's, which have the Qualcomm Snapdragon 801. These Neo's have an Exynos 7580, so those builds are completely incompatible.

Also:

The option isn't in any recovery itself, but in the setup wizard you get on a new installation and I guess major Android version updates (though for the latter, it might be simplified, unsure).

The Android system itself has its own (Lineage) recovery image that it installs/updates recovery from on boot, and the option in both that setup wizard and Lineage's updater enables/disables the updating.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Zeh John:
Thank you very very very much for bringing this to my attention!

When I went through the download folders I found the names funny and didn't download anything until reading more about it, and you've saved me a lot of time from having to read it when it doesn't even apply to my phone and would brick it. Thanks again.

Got this, @PatoKuaKua271q? Don't install it! Apologies for my bad advice.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] PatoKuaKua271q:
I understand, @K9100ii 0 Possibility of building A13 or 14 for this device right?🫠
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
Not without sacrificing functionality (no network traffic monitoring (including data usage stats) + support for any form of data encryption since support for FDE was removed, and the kernel doesn't support FBE).

Those sacrifices aren't anything I'm truly interested in. Both are important to me personally.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] PatoKuaKua271q:
oh okay that's understandable
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] whiteindian:
How to skip that?
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
It's clearly detecting that your phone "is running a custom ROM". That's a generic custom ROM/root access issue, possibly as Google's safetynet isn't passed or the app also has extra checks for either. You'll have to look into (do research on) how to get safetynet passed, and if that isn't enough, also how that could be bypassed specifically for that app (I guess both would involve tricks with Magisk).

Someone else might be able to help more on that here, but that isn't directly related to my builds. Questions here should be limited to the functioning of my builds, not on any apps that might detect a custom firmware (ROM) or root access, or any other generic problems that could appear on any other device.

Keep that in mind, and please do try doing your own research first.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Beta123MAX:
... also sacrificing painless granular per app network permission without root/iptables/script.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Zeh John:
I've been fiddling with my S5 again trying to get this ROM to work without installing it from scratch (because I don't want to reinstall and configure everything again) and this is what I have more to report.

Keep in mind: I am not an Android programmer neither I know about its innards and gizzards, so the things I describe here are certainly not the best way to do things. If you see me writing nonsense here, please educate me, thanks!

After my previous attempt of doing a dirty install of LOS 19.1 over 18.1 I was left with an unrooted OS draining the battery hot and fast and kinda stuck because I also couldn't get the ADB authorization to pop up (so no ADB pairing) and no TWRP because LOS' Recovery kept on overwriting TWRP's installation.

But with folks here here I was able to get TWRP to run and restore my previous 18.1 backup.

So to get root and TWRP on LOS 19.1 I've done a dirty install of it over 18.1, then installed the GApps, and still on TWRP without rebooting I've restored just the boot and recovery partitions of my previous 18.1 backup.

After rebooting I ended up with a smooth functional rooted OS with TWRP booting just fine.

But one critical thing isn't working: I can't get it to connect to the Internet using 4G data.

I have no idea if by restoring the LOS 18.1 boot partition over 19.1's I've overwritten the kernel or the modem drivers or something else critical for 4G data to work.

Again, I'm definitely not an Android connoisseur.

I'm back to my working 18.1 install but if anyone knows how to get the 4G data connection to work please let me know and I'll try it and report back. As always, thanks.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
Trying that cannot be recommended and is likely to end in error.

I expect that my 19.1 builds use different signing keys compared to available 18.1 builds, unless they're also using the same public signing keys. That alone causes huge problems when switching between builds. Always backup your data and do a clean installation when switching to my builds, or any others with different signing. Otherwise, expect such huge problems.

Edit: Whoops, so the 18.1 build you were using before was signed with public keys after all, and you said all was otherwise functional. I missed that the only issue was non-functional mobile data in the end; Faulty skimming. In any case, use the boot image from my build for reasons further on.

If it's working also on 18.1, LTE should be working fine and indeed it does here. But of course, that's assuming you have a properly working installation.

Note also, with any support around connectivity, I assume you have the latest modem and bootloader firmware versions for your specific model, though it should be fine even if you don't.

I'm surprised that boots at all. The 18.1 boot image contains an Android 11 'init' binary that I'd presume is incompatible with Android 12+ (in its 'ramdisk').

I've made changes within my kernel sources which are necessary for my 19.1 builds. That includes a change that is required for mobile data connections to work properly at all, since updates of 'RIL' blobs, which handle mobile networking, to some rather modern ones especially to fix a particular problem on Android 12.

It's quite predictable that would be broken.

It is never a good idea to replace such things from other, especially older, builds to other, especially newer, builds, and then expect everything to work fine. Such a replacement should always be a bad idea, and I'm unsure why you'd do one in the first place. Edit: Even if it's for something like retaining root access, you should never cut corners and go through with any such replacements, and install on top of new components (the boot image) properly.

Not to mention that keeping the same boot image means keeping the same old kernel without new fixes or changes.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Beta123MAX:
Activating root is OT here, as not related to the build. Anyway, just a short hint.

Installing Magisk in recovery (renaming apk to zip) works, as the device is old. So really no need to restore unsuited boot from backup to get root.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Zeh John:
Many many thanks for this valuable hint, it's absolutely handy. Cheers!
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] sooperior:
I'm afraid that's on Lineage/Android hands, nothing that developer can do
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Zeh John:
I kinda expected that. Modern frameworks, mmkay... I'll look for some other topics regarding the possibilities of theming.

Many thanks for the clarification, and cheers.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
Hmm, yeah, okay.

Sounds like it's okay.

For some regions, the last of Samsung's stock firmware (ROM) versions were released in 2018, for others there are more recent versions with a GPS fix. Won't be meaningful to do the update with a GPS fix firmware.

Regardless, you can check the modem firmware version in 'About Phone' in settings. Some device info apps will most easily tell you the bootloader version. Then check the versions against a firmware downloading tool (for example, Frija) or a website (like samfw.com), with a researched 'CSC' code for your country. If they're not up-to-date, you can then download and extract the latest stock firmware, and then install only the 'BL' and 'CP' parts in Samsung's Odin tool in their slots, with all other options unchanged, and with your phone in download mode.

Locked high? Hmm, I guess I think I know what you mean.

In the kernel in my builds, I removed an 'input booster' driver from Samsung, which pegged the CPU quite high on every interaction, and I did myself notice the pegging caused quite some extra heat. CPU frequency scaling does seem fine here now, I guess you should check if it's fine as is.

Yes, that's all down to what's under AOSP. It's just what stock Android 12L looks like, as per Google's own design decisions.

I'm just in the position where I plainly ship what Lineage, with its 'purer' AOSP base, publishes. So, making any such changes to theming isn't my thing.

Also, I don't have knowledge, and don't really have strong feelings, for making theming changes. Others might also not like any changes, and probably I couldn't plainly call these builds 'LineageOS' builds.

As for theming without touching builds, I've never followed what's going on there. But I thought overall interest dropped off years ago. I don't have much help to offer there, sorry.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] ilovesmartphones:
Very good build, but i havent seen a always show info tab and if i search i get the result to go to the tab lock screen but it isnt there, only ambient display. is there a way to enable it or could you possibly implement it?
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
Not sure what that would be, but anyway, I don't implement anything extra.

Any functionality is as per whatever Lineage (and AOSP, being the base) publishes, and also if it's relevant to the device. Since I'm not sure what that feature would be, I also wouldn't know if there would be some sort of configuration to set for it.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] ilovesmartphones:
i guess its the device then, always show info is lineages way to say always on display
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] AssyrianHero:
Thank you for the work you've done! But I have one issue here I kept on trying to install twrp recovery that you mentioned it works it didn't work for me, when I'm trying to enter recovery mode is only showing me Lineage recovery.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Beta123MAX:
If overwriting TWRP is your issue, this was already clarified by K9100ii. Currently needs attention to disable it. Updating recovery will probably set disabled in the next build.

LineageOS 19.1 for s5neolte (SM-G903F, SM-G903W, and SM-G903M)

This is LineageOS 19.1, which is based on Android 12L, for the Samsung Galaxy S5 Neo, codenamed s5neolte, with models SM-G903F, SM-G903W, and SM-G903M. LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android...

xdaforums.com
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
New build for 20240711

Download: https://drive.google.com/file/d/1Jzw2C2Pb3aBKzH9VxD7QQP2-eDzAkIKX

Changelog:

Latest updates from LineageOS, including the 20240605 Android security updates.

Build now signed with my own release-keys - This build contains the signing migration patch here.

Recovery updating(/replacement with broken Lineage recovery) has been disabled entirely - Replacement won't happen anymore even if the mistake where the recovery updating option in the setup wizard isn't disabled is made.

Some security patches have been applied to the kernel.

This build is signed with release-keys since Google now requires that for passing Safetynet. Those who update regularly can update as usual, since I've made a slight compromise for security with the migration patch.

For more technicalities (mostly copy and pasted from here)....

Spoiler content hidden.

For those who don't update regularly, when I release my first 'non-migration' build, I'll add a note about needing to update to a 'migration' build first, boot it, and only then update to a 'non-migration' build.

Enjoy.
[Moto G 5G Questions & Answers] jets1961:
Hi All,

This is probably my second or third post here at XDA but I have been working with custom ROMs for a few years now, mostly eOS.

My question is can I change the firmware of Motorola Moto G 5G (also know as Ace 5G), firmware change from XT2113-3 to XT2113-2?

The later has more bands and is better compatible with my provider Bell in Canada. So is the hardware of the two: XT2113-3 to XT2113-2 the same and the firmware controls the bands, anyone know?

TIA, jets
[Moto G 5G Questions & Answers] RETIEF:
As far as I know, the -3 is a mediatek device and is incompatible with -2 ROMs.
[Moto G 5G Questions & Answers] jets1961:
The XT2113-2 and XT2113-2 are both Qualcomm SM7225 Snapdragon 750G 5G (8 nm) chipset also same CPU and GPU so that is not an issue.
[Moto G 5G Questions & Answers] RETIEF:
According to the Telegram channel, the -3 is RETEU version. If so, the -2 ROMs should work. I am unsure if the hardware will allow whatever bands you are looking for.

I have run the stock RETEU rom on my RETUS phone. I know that works. My experience is that if you unlock the bootloader, AT&T will block you from getting 5G service.
[Samsung Galaxy S21+] LongestyCandy:
Olá pessoal XDA, eu tenho um S21 + 5G Live Demo Unit e gostaria de ajuda para transformá-lo em um dispositivo funcional com um SIM, como ele reconhece a minha operadora, ele até aparece para eu contratar seus serviços, muito comum aqui no Brasil, eu já fiz root nele e eu já testei Samsung TFT, uma ferramenta que encontrei na web, mas ainda não funcionou, tenho medo que não tenha a pasta EFS, preciso da sua ajuda, o que faço?

**Mod Translation**

Hello XDA people, I have an S21 + 5G Live Demo Unit and I would like some help to turn it into a functional device with a SIM, as it recognizes my operator, it even appears for me to contract its services, very common here in Brazil , I've already rooted it and I've already tested Samsung TFT, a tool I found on the web, but it still doesn't work, I'm afraid I don't have the EFS folder, I need your help, what do I do?
[Samsung Galaxy S21+] V0latyle:
@LongestyCandy Welcome to XDA. When you created your account, you agreed to follow the Forum Rules. Since you have not already done so, please read them now:

📚 XDA Developers Forum Rules 📚

XDA-Developers FORUM RULES List of Forum Moderators, click HERE Delete Your XDA Account HERE 1. Search before posting. Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new...

xdaforums.com

Please pay special attention to Rule 4.

As a courtesy, I have translated your post.
[Samsung Galaxy S21+] LongestyCandy:
Sorry @V0latyl
[Samsung Galaxy S21+] LongestyCandy:
Hello people from XDA, I bring you new news after exploring the EFS folder I found that it has the files and IMEI and everything, however, I discovered something else.

There is a code that you type on the phone *#0011# that shows the status of your chips, and when I go to see mine they are like this:

View attachment 5967535

In other words, my theory was confirmed, it already has an internal IMEI, but Knox or something like that is making it activate some signal for the Samsung rom that recognizes that it is an LDU and does not allow the IMEI to be used.

There is a tool that deactivates the Demo Live Mode which is the EFT Dongle Pro, it is a tool that depends on paid licenses but apparently it is worth it, but I have a problem and all G996B LDU users who are seeing this tutorial too, which is the following, the tool only performs this "live demo unlock" on Android 10, and the G996B LDU is Android 11, in addition to the fact that after deactivating the live demo mode, you cannot update or reset, that is, this method it doesn't work for us.

The option we have left is some Custom ROM that ignores this "signal" or some Magisk module that does that, something that doesn't seem to be difficult, the most annoying thing will be finding out where this signal comes from, I suspect it's from Knox, anyway, we enlisted the help of the Custom ROM developers to see if they can help us. I started to analyze the EFS folder of a normal G996B and a G966B LDU to see the differences and if anything I'll come back with news, that's it for now, see you guys.
[Android Software/Hacking General [Developers Only]] aldoseballs:
hey im new to this i was rooting my moto g pure and when i was flashing the magisk patched boot.img i guess i typed the file location wrong and now the phone is just cycling between the phone boot screen and the unlocked bootloader wanrning thing page
[OnePlus 11R (Ace 2)] sylentears:
Hi everyone into this post thread.

We all know that converting chines ace 2 to oxygen os has some issues. We are trying our best to fix such issues, therefore trying different techniques. I had the same issue too, i read one post that flashing ocdt.img of 11R ll fix the issue, therefore, i took step to do it. After flashing 2487 ocdt.img, i restarted bootloader to normal. Phone booted, but still gets black, flicking and then goes black. I tried to restart it with keys, and phone wont detected by pc, even the bootloader was unlocked and usb debugging was enabled too. I tried enough to start in fastboot mode. But nothing, then i forcely start into EDL mode, and it deteceted. I purchased official authentication key to flash it back to coloros 13. The official tool failed to flash with error that image and product code mismatched and i loss money. Now dont know if i purchase a other authentication or wait for the developers to figure out issue.i have a complete flash tool logs, which is very useful for the developer.

Because in the stock image, they have made tachtis to keep users afftected and pay them to bring the devices back.

Pro opinion and fix is needed for everyone affected by this.
[OnePlus 11R (Ace 2)] ehsan90a:
you need to flash china version (Ace2) ocdt.img again in your phone

make sure you have unlocked bootloader ( i know you have black screen). then go to fastboot and flash this file.

download file

power off ...

power on +( vol - )

connect cable

then in cmd write

fastboot flash ocdt ocdt.img

you have not orher way .. only this way can work 100%.

in OFP we have not OCDT image . so do not waste your time and money
[OnePlus 11R (Ace 2)] sylentears:
I had tried enough to boot into fastboot, but phone dont boot, and dont know even this is booting or not due to black screen, i only know theat attaching cable vibrate the phone but it wont detected. Tried combination keys to boot i to bootloader, but no luck. I keep phone as it is to see if battery get drain and ensure that its power off and will try afternoon.

Thanks forsharing stock ocdt for this model.i would request you to kindly rename the file to this specific model, so people know about it. The flashing way is a same.
[OnePlus 11R (Ace 2)] ehsan90a:
you need to keep all 3keys togather...

after 15sec it will go to EDL mode.. connect cable

after that ..

keep power + (vol- ).. after 15 sec it will go to fastboot
[OnePlus 11R (Ace 2)] chenysimple:
I face the same issue, I did wrong that FLASHING 11 (not 11 R) OCDT.IMG, The after-sales staff were unable to restore my phone, so they directly gave me a new one.
[OnePlus 11R (Ace 2)] sylentears:
Tried this, phone disconnect and vibrate, then not boot to fastboot.
[OnePlus 11R (Ace 2)] mariospsp:
i got in the same situation with you. What i did was

1) Get into recovery mode and wipe everything

2) Get a usb-c hub or otg cable and connect a usb mouse. You should be able to go into startup setup without any black screen issue.

2.1) If you dont have a usb hub you can do it but is harder way. Wipe everything again and in the startup setup screen you should be able for a split second before the screen goes black to slowly continue with the setup. Every choice you make you have to wait 30 seconds for the phone to be locked and then unlock with the button. It very time consuming but you can eventually setup your phone.

3) The state i am in now is that when i plug the phone to the pc the screen is going black and i cant authorize the phone with the computer to flash back the old ocdt.img

4) I hope that helps you and someone else help us.

EDIT - Do not open camera or the phone keyboard. The phone will go immediately in black screen!

Good luck!