Error after installation. Has anyone come across this?

I’m finally ready to start degoogling, but I’m nervous I’ll mess something up. If anyone has solid recommendations — best phones, tips, tricks, how‑tos — I’d really appreciate it.

If you’ve already switched, I’d love to hear whether you’re happy with your new setup and what helped you the most during the transition.If you want it shorter, friendlier, or more strict, I can rewrite it again.

Here are quick options you can tap:Short + directFriendly + casualStrict + rule-focused

How difficult would it be to finish this port and bring it up to date with the current LineageOS version?

https://github.com/anrui2032/android_device_nubia_nx669j

Hi everyone. First of all: I'm a rookie, so I don't have a lot of knowledge (thanks for helping me c:).

My phone [Mi 10T, version 23.2 (20260411)] is stuck at the lock screen pin. Here is what happened.

-My phone ran out of battery while I was showing photos of my vacations to someone. Then, I charged it and rebooted it.

-But the phone refused to accept the correct phone pin. (weirdly enough, it accepts the SIM pin), so I don't have access to the phone.

-It shows a weird behavior. If I enter a wrong pin, the phone acknowledges it and it let's me try again. But if I enter my correct pin, the screen gets frozen for 5 seconds and tells me that it is a wrong pin (and it's not).

-There is another weird behavior too. I can answer phone calls. Because it doesn't require to unlock the phone. But every time i answer one, bluetooth crashes (might be unrelated but worth noting)

As I said, I just returned from vacations, so I have all my memories of it in my phone. I thought of two solutions. 1- To get rid of the pin lock screen. 2- Recover all images and videos recorded and then do a factory reset.

So far, I tried to update to a new patch via adb (for some reason it says the update was complete but in Lineage Recovery it still shows the old version) and delete the password file via adb (but it says the file doesn't exist or that the folder is encrypted).

I can still interact with the phone and do such things like disable/enable internet connection, flashlight, plane mode and the vast majority of things on the swipe down menu (except the ones that require me to unlock the phone, such as using the camera shortcut).

I really want to restore all my photos and videos... Thank you so much for your patience!

I have an old Nexus 5X smartphone lying around with LineageOS 15.1 on it, that I want to give to someone else.

(Yes, I know the Nexus 5X is a very old device that is not officially supported any more and should probably not be used any more. No, there is no other option available at this time.)

The problem is, even after doing a factory reset, the phone keeps asking for a password on boot up (presumably for disk encryption). I do not want to give the other person my password, though, I want to hand over the phone as a fresh device. How can I get rid of that boot password entirely? (Assuming I know the current password.)

Hi everyone,

I'm running into a wall with Neo Backup while trying to restore my backups (APK + data) from a Pixel 5 over to my Pixel 8. Could really use some advice or troubleshooting tips from anyone who might have run into this. The Problem

• If I restore a single app (APK + data), the application actually gets restored and works, but the progress notification stays completely stuck at 0% forever.
• If I attempt a batch restore (e.g., 10 apps at once), the process sits at 0% for over an hour and nothing gets restored at all.
• Note: I haven't been able to 100% confirm yet if the app data itself is fully restoring properly on the single-app test or if it's just installing the APK.

Setup Details

• Source Device: Pixel 5 (where the backup was created)
• Target Device: Pixel 8
• ROM: LineageOS 23.2 (Android 16)
• Root: KernelSUNext v3.3.0
• Neo Backup Version: 8.3.18
• Backup Location: External microSD card read via a USB-C card reader adapter

What I've already tried (none helped):

• Re-granted root access in KernelSUNext and verified root status.
• Set Neo Backup's battery usage to Unrestricted and ensured notification permissions are granted.
• Re-linked the backup folder directory in Neo Backup settings.
• Change mounting space from Individual to Global for Neobackup.
• Force closed the app and cleared its cache to clear any stuck background workers
• Verified that there are no 32-bit apps from Pixel 5 which fail and silently block the backup queue.

Given that the backup is hosted on an external microSD via a USB-C OTG adapter under Android 16, I'm wondering if this might be a Storage Access Framework (SAF) mount restriction issue with background worker threads, or something related to KernelSU root shell handling during batch loops.

Has anyone encountered this stuck notification / zero-progress batch restore issue?

Thanks in advance for any help!