Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

LineageOS + OnePlus 6 #56

Closed
kaffeeringe opened this issue Jan 16, 2023 · 15 comments
Closed

LineageOS + OnePlus 6 #56

kaffeeringe opened this issue Jan 16, 2023 · 15 comments
Assignees
@tsterbak
Labels
bug Something isn't working
Milestone
Release Alpha 0.3.3

Comments

@kaffeeringe
Copy link

Installer
I donwloaded the latest nightly of LineageOS 20.0 and 19.1 - both don't seem to be the right version. What am I doing wrong?
@tsterbak tsterbak self-assigned this Jan 16, 2023
@tsterbak tsterbak added the bug Something isn't working label Jan 16, 2023
@tsterbak tsterbak added this to the Release Alpha 0.3.3 milestone Jan 16, 2023
@tsterbak
Copy link
Member

Hey, first of all, thank you for your interest in the project! And thank you for reporting this issue.

I guess I can see the reason for this bug. It's related to how OnePlus treats their devices device_code.
The device_code of that device is "OnePlus6" and the official code name of the device is "enchilada". For most vendors this seems to be the same thing. I'm checking in the tool if the device code matches the code name specified in the LineageOS zip. In this case they happened to not match...

I will address this in the next release later this week. If you want to progress in the mean time, you can update the "pre-device" field in the LineageOS zip, in the text file META-INF/com/android/metadata from "OnePlus6" to "enchilada". Then the compatibility checks should let you continue. (And hopefully this doesn't hurt LineageOS in some otherway...) The safest way would be to wait for the release and try again on the weekend :)
Let me know if you have any questions! I'm super happy for all the feedback I can get! :)

@tsterbak tsterbak mentioned this issue Jan 17, 2023
Merged
tsterbak added a commit that referenced this issue Jan 17, 2023
@tsterbak
Implemement a fix with alternative device code resolution (#57)
4141b22 
This PR fixes the issue with devices where vendor device code is not the
official device code.
Mostly present in One Plus devices so far. #56
@tsterbak tsterbak mentioned this issue Jan 17, 2023
Merged
@kaffeeringe
Copy link
Author

Hej! Thank you for the quick answer and of course for this software. I struggled for a long time with the process without this software. It took me years to get my old tablet to LineageOS. And now it's only a few clicks!? Awesome!

Your workaround worked! (With LOS 19.1 - with 20.0 it didn't)

But: The next step starts the bootloader. That works I see the menu and I see, that my phone is still locked. But the next step doesn't work. The fastboot-window opens but nothing happens.

@tsterbak
Copy link
Member

Hey :) Thanks for your kind words! I hope I'll get your issue resolved and make the process really easy for you :)

Thanks for persisting and trying the workaround. (Curious that it didn't work for LOS20)

Are you trying the tool on windows? Could you attach the log file here? (The file should be in the same directory as the executable) Then I can further investigate. :)

tsterbak added a commit that referenced this issue Jan 19, 2023
@tsterbak
Release v0.3.3-alpha (#51)
db206ed 
This PR adds:
- progress bar do show the progress of the flashing.
- force light mode to address (#54)
- a fix with alternative device code resolution (#56)
- support for new devices (#52) :
    - Motorola moto g6 plus
    - Motorola moto g 5G plus / one 5G
    - Motorola moto g 5G / one 5G ace
    - Motorola edge
@kaffeeringe
Copy link
Author

Oh no! Now:

serving: 'H:\LineageOS\lineage-20.0-20230110-nightly-enchilada-signed.zip' (~47%) adb: failed to read command: No error
$adb shell twrp wipe dalvik

@kaffeeringe
Copy link
Author

Uh, But it boots anyway. And it seems to work. I was able to set it up.

@kaffeeringe
Copy link
Author

Some apps don't seem to work. And "android.process.media" fails on startup. Thus gallery and music don't start.

I guess, this should be fixed with an update.

@kaffeeringe
Copy link
Author

Sadly no. The update didn't fix that. I guess, this is a LineageOS-problem.

@kaffeeringe
Copy link
Author

But thank you! The tool works pretty well.

@kaffeeringe
Copy link
Author

Factory-reset helped.

@tsterbak
Copy link
Member

Hey, thank you for your effort and your feedback! :) It helps me a lot!

serving: 'H:\LineageOS\lineage-20.0-20230110-nightly-enchilada-signed.zip' (~47%) adb: failed to read command: No error
$adb shell twrp wipe dalvik

This issue actually happens with most LineageOS versions and with regards to the LineageOS documentation, is expected but not a problem for the process. Seems to be an adb issue.

So you got LineageOS 20 successfully installed? Would you say a general hint towards using a factory reset would help users? I try to do that automatically in TWRP, but that usually fails/only partially succeeds for A/B-partitioned devices...

@kaffeeringe
Copy link
Author

Yes. I guess a factory reset should always help. I read some posts. This error seems to be a common problem and the solutions seems to be to delete the app cache. A factory reset seems to do the same.

It would be cool, if your installer optionally installed F-Droid. I guess, that is the first thing, most people do.

@tsterbak
Copy link
Member

Very good point! I haven't thought about F-droid so far. I'm currently working on a solution to optionally flash Gapps or microg, but F-droid actually should be more straight-forward (because of less OS dependencies) and very useful immediately.
So hopefully that will be possible sometime next month :)

@kaffeeringe
Copy link
Author

MicroG and GApps would be cool too for people who want to pass the phone on to someone less experienced.

@famo
Copy link

famo commented Jan 22, 2023

FYI
https://lineage.microg.org/

@tsterbak tsterbak closed this as completed Feb 8, 2023
@tsterbak
Copy link
Member

tsterbak commented Feb 8, 2023

Closing this since the conversation is mostly resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tsterbak tsterbak

Labels
bug Something isn't working
Projects
None yet
Milestone
Release Alpha 0.3.3
Development

When branches are created from issues, their pull requests are automatically linked.

56-oneplus-device-code-issue openandroidinstaller-dev/openandroidinstaller
3 participants
@kaffeeringe @famo @tsterbak