Thanks — and since you are rewriting that line anyway, one plea from the other side of the screen.

A counter tells me where it stopped, not what went wrong. "Bootstrapping 4/10" is still a sentence that hides the reason, and the reason is the only thing I can act on. If the splash has room for one line of real text, print the operating system's own error string underneath the step. That is the difference between me sending you a screenshot of a progress bar and me sending you the logcat line you actually need.

The install itself is the other half, and this thread already showed the shape of it: the failure moved the moment the download source changed, while storage was never the cause. So before the error gets a friendlier label, it is worth hashing the APK once it lands and comparing it against what the server offered. A truncated download looks exactly like a broken app, until you check the bytes, and then it looks like nothing at all.

I will try the next build and, if setup dies again, you get the exact step and the real message instead of a guess.