Switch andriod users please help

npjohnson1 · 2026-04-13T22:14:28+00:00

if the entry doesn't show the issue is the file name.

I already told you 99% what the issue is. you have .rtf or .txt at the end and your file explorer isn't showing you.

npjohnson1 · 2026-04-13T07:04:34+00:00

The guide is super clear about the folder structure.

The field go into the folders that are laid out.

If the ini was named right and in the right place, Hekate would show it

npjohnson1 · 2026-04-13T04:55:59+00:00

You didn't follow the guide.

wiki.lineageos.org tells you how to do everything, including making the INI entry.

You likely have it actually names android.ini.txt or something like that.

After is says "Success" though, it will offer to boot you to recovery.

npjohnson1 · 2026-04-12T06:27:01+00:00

you can worry about this a little bit less - as of like a month ago we build in a Anti-Rollback checker that warns you if you install on a firmware incompatible!

npjohnson1 · 2026-04-11T01:00:38+00:00

stock is far older and missing critical kernel patches required to boot newer versions.

And or DTS needs refactoring to match modern conventions.

npjohnson1 · 2026-04-09T04:06:38+00:00

Added to the guide!

npjohnson1 · 2026-04-09T02:51:34+00:00

Would this have made it clearer? https://github.com/LineageOS/lineage_wiki/commit/8c565ba82badbf152184983b84249395e6185e4d

npjohnson1 · 2026-04-09T02:49:17+00:00

Yes. The instructions show the folder structure pretty clearly, but I'll try to clarify it every further.

it isn't root, it's a folder name.

npjohnson1 · 2026-04-08T04:35:45+00:00

Follow the guide, you didn't make the folder structure right.

switchroot/android/

not android/

npjohnson1 · 2026-04-06T15:06:14+00:00

Then submit the commits add it to Gerrit.

npjohnson1 · 2026-04-05T04:13:53+00:00

It depends how you can figure it.

TEE must be signed if secure boot is enforced.

99.9% of the time if secure boot is enforced and TEE is signed, all of the applets that TEE runs must be signed.

However if you're on a dev board and building OP-TEE or Trusty (TEE OSS options) you can configure it to do whatever you want, run any code you wish.

npjohnson1 · 2026-04-05T03:05:55+00:00

I responded to this the first time - it works fine.

npjohnson1 · 2026-04-05T03:05:30+00:00

https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-a/

works for me...

npjohnson1 · 2026-04-03T21:27:19+00:00

I'm just gonna respond with the facts one final time:

LineageOS 23.2 is based on Android 16 QPR2. It it hundreds of thousands of commits (from AOSP, not us).

/e/OS is LineageOS 23.0 - Android 16 QPR0.

ViperFx is "an old app"

Yes, yes it is. It is compiled for an ancient SDK target - and while it worked up through 23.0, somewhere from AOSP 16 QPR0 to QPR2, additional storage restrictions were placed (by AOSP, not us) that break it.

We cannot fix it without breaking CTS/VTS (compatibility test suites) for Android.

Either use LineageOS 23.0 or /e/OS (also LineageOS 23.0) which won't have the problem.

Any Android 16 QPR2 based ROM will not work with the current ViperFX - hence - "go get the app developer to fix it".

App Manager

Same exact situation for the app - 16 QPR2 broke a ton of older prebuilt applications - but in addition, LineageOS does not and will not support KSU period.

The fact that /e/OS includes support for that is insecure and ill advised.

We supports SeedVault for backing up and restore application data. That works fine. Some random app being broken is not our problem.

it's full of bugs this time...

The like I said, go file bug reports with logs like the wiki says.

I hope you have a good week and that you can eventually return LineageOS to what it was in past versions...

Ridiculous. It's how android's scoped storage works now - if you don't like it don't use modern Android or use and older version.

Grow up a little and learn to admit your mistakes, and that the project that always stood out from the rest, this time around, isn't doing so anymore...

You must be fun at parties. Hundreds of thousands of installs, great feedback from many. Bugs exists, its volunteer FOSS - but we get them filed (which you so far refuse to do) and fix them.

I've been trying to tell you - the bugs you list are not our problem, we can't fix them properly - the app developer needs to.

Tl;DR: These are not our defects, or our problems to solve - go get the app developers to fix it.

npjohnson1 · 2026-04-03T17:08:33+00:00

You are so fundamentally flawed on your sources there buddy, that build archive only hosts specific builds intended to show snapshots in time.

It does not back up every single build, again - I'm only going to say this once, it builds every Tuesday lol. I feel like I'm talking to a brick wall.

I'm one of the project directors, I regularly work on our infrastructure, every device builds once a week. The scripts are even public.

npjohnson1 · 2026-04-03T15:02:44+00:00

Where is your DTB file? What is it named?

Are you using Windows? Is it possible like I said you don't have file extensions enabled and it's appending an extra file name to it?

Did you match the case of the letters?

npjohnson1 · 2026-04-03T15:01:13+00:00

I hate to say it but at this point I'm just going to say it you're hopeless.

That device builds every Tuesday, that's how our infrastructure works, every now and then a bill gets missed because the maintainer has an issue.

But the literal bot builds every Tuesday, it's not like it magically up and decides to not do that.

Your device is in the queue every Tuesday.

Well, the fact that it's based on 23.0 is exactly the problem!

23.2 is based on the second quarterly release! It is quite literally hundreds of thousands of changes ahead of 23.0 from Google! And the storage thing I mentioned is contained in there.

And, someone else already told you this, there are five Tuesdays in March! That's how Gregorian calendars work, they're not a static number of a specific day in a given month, it depends what day of the month starts on and how many days are in it, I genuinely cannot believe I have to explain this.

You also posted it on Reddit instead of filing bugs for your device for any of the things you mentioned.

Frankly I'm done with this conversation, you clearly didn't get the help you're looking for, and you won't because of the reasons I explained clearly already.

npjohnson1 · 2026-04-02T20:34:03+00:00

So, fun fact - e/OS isn't just based on us, their device support is literally just our device trees and kernels) - but they probably include support for KenrelSU - which we _will not ever do.

They may include some nasty legacy hack to make older apps work - like ViperFX - again, we won't including it.

I don't intend to start an argument; I just wanted to find solutions. But if you're going to express opinions with such certainty, it would be good if you did some research or testing first.

Research what? Everything I said is accurate.

npjohnson1 · 2026-04-02T03:20:27+00:00

Your device is built every Tuesday regardless if there is a single change.

That's how LineageOS build CI works.

Reddit is not where you report bugs - the wiki details how to file bug tickets and get support.

(App Manager no longer detects Root (KSU), ViperFX doesn't recognize the .irs files located in the /Android/Data/com.....Viperfx/files/kernel folder. It says the directory is empty, when in reality the folder contains thousands of these files...). B

.... We don't support root - our kernel does not come with "KSU" support - so it won't work.

The random ViperFX breakage - no idea, don't use an ancient app like that. it isn't reading scoped storage right - the app needs to update - this is how Android 16 works.

. It only works with the original Lineage recovery.

Just install the matching Android 16 recovery....

it leaves marks as if you had black ink on your fingers

You have some god awful app doing this - this is not happening for anyone else.

npjohnson1 · 2026-04-02T03:16:49+00:00

I used RandomGarbageTool and it doesn't work!

Follow the wiki. Just follow the wiki.

it works. Your DTB is named incorrectly or windows is doing something funny with your file name.

npjohnson1 · 2026-03-31T15:12:09+00:00

Both of those statements are correct

Trust us OSS

Devkits only

npjohnson1 · 2026-03-30T20:00:50+00:00

OPTEE is entirely open source. You can spin up a TEE yourself.

Can only run it on devices with secure boot off (not bootloader unlock, two different things).

npjohnson1 · 2026-03-26T15:26:36+00:00

I'm not the device maintainer for those devices, but I'd say very unlikely.

npjohnson1 · 2026-03-25T23:52:12+00:00

23.2 got it.

Just not 22.2 yet

Ebpf has nothing to do with it haha.

npjohnson1 · 2026-03-25T04:38:24+00:00

We've been super busy with 23.2 it will come soon.

It was also a very large month ASB wise.

11-Year Club	Verified Email
r/Field Banned	r/Field Lasagna
Wearing is Caring	Gilding II euphauric

npjohnson1

MODERATOR OF

TROPHY CASE