P2JB takes very long or seems stuck
Low risk~ ReportedWhat you see
- P2JB keeps running for tens of minutes with no clear sign of progress.
What it means
This is about P2JB builds used with Y2JB. In tests shared in the Y2JB autoloader discussion, users report runs that take tens of minutes, around 50 minutes in several cases. These are user reports, not a confirmed time for every console or firmware.
What to do
Compare your log and the wait with the notes for your exact build
In that discussion, the progress bar is described as only an estimate set for about 50 minutes, so a run can end a little earlier or later.
Consider another chain only if it clearly supports your firmware
If another chain explicitly supports your firmware, you can look at it as an alternative. Keep a copy of your current setup first.
When to stop
There is no fixed time
The reported time is not a rule for every firmware. This guide cannot promise that the run will finish, or how long it will take.
Sources
- Y2JB Autoloader: P2JB testing discussion (#7) (Oct 31, 2026)
Last reviewed: Oct 31, 2026
← Troubleshooting