-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
(darcy) Device Does Not Boot After Patching Boot.img #8297
Comments
Old issue that was never reopened for some reason: #8285 |
Same issue on Nvidia Shield TV 2019 Pro |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as abuse.
This comment was marked as abuse.
You are using a custom ROM, please ask the ROM builder to contact us. |
LineageOS Gitlab issue created: https://gitlab.com/LineageOS/issues/android/-/issues/7545 |
Looks like LOS team doesn't want anything to do with it either: https://gitlab.com/LineageOS/issues/android/-/issues/7545 Oh well... |
I would say, their refusing is reasonable. Unless, we provide an evidence that prove the bug is related to LOS. |
I agree. Unfortunately, we are at the mercy of the developers. |
LineageOS is does not support root so we cannot get any support on their end. Is there any reason you believe it is an issue with the ROM? Something I can provide the devs there at-least? Right now we are at a dead end... Also, I see another open issue with someone else using LineageOS and you tried providing support for their device? I don't understand why our issue is being dismissed when we are also on LOS..? |
Without help from the ROM builder, troubleshooting the issue could be challenging. Can you get kmsg? #7390 uploaded kmsg so we know what happened. |
@vvb2060 Hi, thank you for your support. This is Unsuccessful boot And this is successful boot I'm ready to be a volunteer to install any modified Magisk file(s) to overcome this issue. Device: Nvidia Shield TV 2019 Pro Thank you! |
Don't use canary, install debug version and upload kmsg. |
@vvb2060 Also the result of Finally, the result of Note: result Are these okey? |
https://source.android.com/docs/core/ota/dynamic_partitions/implement#system-as-root-changes |
@vvb2060 I unpacked the boot.img file ( Thank you. |
@vvb2060 Thank you for your reply. Thank you. |
Workaround: LineageOS/android_kernel_lge_sdm845@026011c |
@aviraxp Thank you for your help but I couldn't understand what you mean. |
This comment has been minimized.
This comment has been minimized.
Hi, It's working. Thank you! I also attached the |
The fix has to be reverted because it breaks more legacy sar + 2si devices. Pleaseet maintainer pick LineageOS/android_kernel_lge_sdm845@026011c into kernel instead. |
But unfortunately the maintainer said that he wasn't interested in applying any changes to support Magisk! |
@vvb2060 Do you update your version recently? Can I update magisk with your release? Thank you. |
Device: Nvidia Shield TV 2017 (darcy)
Android version: lineage-21.0-20240805-nightly-foster (Android 14)
Magisk version name: Magisk Canary
Magisk version code: 27006
Trying to boot device after patching/flashing boot.img via fastboot/bootloader causes device to return to bootloader interface. Fails to boot.
Magisk Debug Logs + Patched Boot.img.zip
The text was updated successfully, but these errors were encountered: