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

Rebooting to payload from l4t causes emummc patching to fail #498

Closed
AuroraWright opened this issue Oct 13, 2020 · 1 comment
Closed

Rebooting to payload from l4t causes emummc patching to fail #498

AuroraWright opened this issue Oct 13, 2020 · 1 comment

Comments

@AuroraWright
Copy link
Contributor

AuroraWright commented Oct 13, 2020 •
edited
Loading

Booting latest l4t Ubuntu (3.2.0), rebooting within the OS, and then launching emummc causes a failure in emummc patching. Continuing to boot launches sysmmc with redirected Nintendo folder (?).
Launching sysmmc and rebooting to payload makes emummc bootable again.
Enabling logs just before launching the emummc yields this:
image
For comparison, this is a successful boot.
Screenshot_20201013-074529

Not sure if relevant but I'm using a genuine Samsung 512GB Evo Plus card which I just set up with the Hekate partitioning tool
@AuroraWright
Copy link
Contributor Author

Closing as it seems to be caused by the r2p hekate payload bundled with l4t being outdated.

@AuroraWright AuroraWright mentioned this issue Oct 14, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AuroraWright