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.
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
Can’t boot into lineageOS 16 (Android 8.1) #521
Comments
it does me the same but me i can't even start Athmosphere |
The new maj broke everything |
First thing to try (for Atmosphere problems): rename/remove atmosphere/contents and replace it from the release zip. If it works, your issue is with a theme or something with a boot2.flag in it (like nx-ovlloader). If it doesn't fix anything, check for kips that don't come with the current release, and remove those. |
@JteMonteEnDerby as always with every major HOS version and not, you need to clean your content folders. Removing themes, removing incompatible with HOS sysmodules and incompatible with new Atmosphere sysmodules. @FatalPunisher88 which lineageos android version? |
@CTCaer i have try with only atmosphere file and it don’t work too |
@CTCaer it is I usually boot Atmosphere,Sxos and Android from Hekate and it has all been working fantastic until I updated.i am just checking again and it is only LineagaeOS that gives me the black screen when booting from Hekate.and I have to restart the switch.atmosphere and sxos boot just fine from hekate. Edit:atmosphere and sxos 3.10 boot fine from Hekate as usual.only Lineageos gives me black screen. |
Yea yea there is definitely a thing because I ask to a YouTuber who show smash mod if he got problem and he say yes |
Android 8.1 is not supported. It uses an ancient and broken uboot/kernel combo (1.5 years old). As I stated in switchroot discord, Android 8.1 must die. If you want further comments or help about it, @bylaws can help you. |
Can’t boot into LineageOS anymore since update.
Firmware 11.0.0/AMS 16.0
Hekate 5.5.0
Screen just goes black and I have to restart my switch.
The text was updated successfully, but these errors were encountered: