Closed npjohnson closed 4 years ago
+1
My XL is locked right now, but I will attempt M1cha's manually appended FDT method when I next decide to unlock the device. It will likely fix the issue and let us boot LK (still not UEFI though, as manually appending FDT only works to boot LK right now, and using it on UEFI just results in the system rebooting).
I'll be providing weekly updates like this on the device's I am currently trying to port the project to.
Wait... Sorry, my XL is locked too. What do you mean with M1cha's manually appended FDT method??
On Mar 13, 2017 7:35 PM, "Nolen Johnson" notifications@github.com<mailto:notifications@github.com> wrote:
My XL is locked right now, but I will attempt M1cha's manually appended FDT method when I next decide to unlock the device.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/efidroid/projectmanagement/issues/86#issuecomment-286265227, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALQyqXsdLF0J7q2G3GPsckeM2PxyNtSzks5rlcTHgaJpZM4MWWbW.
Oh, ok. I thought it was another way to unlock Pixel Devices.
Also, I know this might me a bit off topic, but, do you know any app like BootUnlocker that works in Pixel (for locking the bootloader with root)?
On Mar 15, 2017 6:52 AM, "Michael Zimmermann" notifications@github.com<mailto:notifications@github.com> wrote:
@GabrielTKhttps://github.com/GabrielTK #89 (comment)https://github.com/efidroid/projectmanagement/issues/89#issuecomment-286063675
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/efidroid/projectmanagement/issues/86#issuecomment-286692997, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALQyqSIAt6GFR0OMyD-cE4SQ3hVeb-TAks5rl7TngaJpZM4MWWbW.
No progress this week.
ARCH: MSM8996 OEM: "Google" (HTC) Branch used to build: LA.UM
Whether booted or flashed to the Boot partition, LK doesn't initialize, and it hangs at the Google (aboot) logo. No LK access over USB.
This is likely due to the looming "LK doesn't boot on 64-bit devices" we don't understand yet.