Fix disk space error during multi-firmware extraction with debug mode #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The firmware extraction fails with "Error 70 : Write error : cannot write decoded block" when unpacking SM-S938B after SM-S916B. The main firmware extraction consumes 6-8GB, leaving insufficient space for lz4 to decompress the next firmware's super.img (requires 3GB for streaming: 1-2GB compressed input + 1-2GB decompression buffer).
Changes
Debug Infrastructure
LOG_DEBUGfunction that outputs whenDEBUG_BUILD=true(enabled via--debugflag)Disk Space Management
FETCH_FILEtmp_*files owned by current user onlyError Detection
Error [0-9]+ : Write errorImplementation
The cleanup is conservative: never uses
rm -rf /tmp/*, only removes files matchingtmp_*pattern owned by current user, with 5-minute age threshold for /tmp to protect concurrent operations.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.