Start with the current job card, inspect the named device, and complete only the required repair steps before the final check. A review calling the shop dirty is different from a device part that will not reach its cleaning target. Use the relevant branch below rather than buying another tool or restarting the save without identifying the problem.
Keep your place while you work
Progress is stored only in this browser and is never uploaded.
Cleaning problem router: identify the surface before retrying
Do not treat every unfinished cleaning objective as the same bug. Read the task wording, identify the exact object still named, and change only one variable at a time. The routes below point to existing evidence-aware guides; they do not claim that every symptom is a confirmed defect.
| What is still dirty or blocked? | Check next | Evidence boundary |
|---|---|---|
| Shop floor, wall, counter or room cleanliness | Open the shop-rating guide and inspect the named shop surface | This is not a device-part or paint-progress problem |
| Removed component or hidden edge still shows dirt | Rotate the part, inspect both faces and use the matching cleaning tool | Do not replace a working part only because dirt remains |
| Item is inside the Sonic Bath | Wait for the completed cycle, then use the Sonic Bath guide | Current-build behavior and older lost-item reports must stay separate |
| Airbrush moves but paint remains at 0% | Use the Airbrush troubleshooting guide | Painting is not cleaning; do not merge the two symptoms |
| Order remains incomplete after all visible dirt is cleared | Record the exact task text, object name, build and a screenshot before reloading once | No universal fix is claimed without a reproducible case |
All parts already clean? No dirt appearing
Separate no visible dirt from visible dirt with a cleaning meter stuck at 0%. A dated Reddit case describes about two hours with no dirty parts, including an Atari dust ticket, on a self-described 2017 MacBook Pro. It does not isolate a cause or recovery. Protect the save, compare the ticket with the opened device, inspect both faces and check whether every new order or only one model is affected. Record build, macOS, GPU, model and ticket. Use the cleaning router for visible dirt and the Airbrush guide for paint progress; do not treat reinstalling or changing graphics as an established fix.
Player report — “Dirt bug” (October 17, 2026)
| What you see | Use this route | Evidence boundary |
|---|---|---|
| No dirt on any part | Preserve the save; record build, device and ticket text | Single player report; cause and fix unconfirmed |
| Dirt is visible, cleaning stays at 0% | Use the cleaning symptom router | Different symptom |
| Paint objective stays at 0% | Check the required palette, then use the Airbrush guide | Different tool and objective |
Keep removed parts visible and grouped by layer. Use the recorded order as a reference; if your Notebook shows something different, follow the game.
Shop says dirty, dusty, smelly or rats — but nothing is left to clean
First separate a shop-review complaint from a dirty device part. Players report that some three-star reviews mentioning dust, smell, rats or a dirty shop can occur during a story sequence and later clear as the story advances; other players had simply missed removable clutter such as the paper above a shelf. Neither report proves a universal trigger. Do one slow room pass, check far-left and far-right shelves and removable trash, then read the active To-Do and finish the current story job before spending money on more cleaning tools or decorations. If a specific device part is stuck below 100% clean, rotate and zoom that part, note the model and build, and treat it as a separate repair issue. Do not restart a save or promise that one purchase fixes every case.
| Check | What to record |
|---|---|
| Scope | Room rating or one device part |
| Room pass | Removable clutter, shelf edges and both sides of the shop |
| Story state | Active To-Do and the review after the current story job |
| Persistent case | Build, story step and exact review text |
Part shows as missing while it is in the Sonic Bath
Check whether the part is currently inside the cleaning machine before treating it as lost or buying a replacement. Players report that the parts list can mark items in the Sonic Bath as missing until cleaning finishes and they return to the bench. This is a UI report, not proof that the part was deleted. Count what entered the bath, let the cycle finish, empty it, and recheck the Notebook.
Hidden or missing part — cannot complete an order
Use this as a troubleshooting checklist, not as a guaranteed official fix. First rotate the device and inspect behind it and along the workbench edge. Compare the Notebook part list with the device and inventory, check the Sonic Bath, then restore a copied protected save. If the part is still absent, record the build, device, order, missing part and a screenshot before reporting it.
- Behind or underneath the device
- Workbench edge and visual occlusion
- Notebook part list
- Inventory and donor boxes
- Sonic Bath
- Copied protected save
- Bug report with build, order and missing-part name
Brick Game: no part-placement highlight
In a September 13 Steam case, NuclearDystopia could not get a placement highlight during an ordinary Brick Game repair. Rose Brigade suggested checking panel → screen/buttons → green board → orange board → back panel, then batteries and cover, and described six screws per board and six on the back panel. Those are the reply’s counts, not this site’s current device census. Check the current layer and visible screws first. Leaving and returning to the bench, then restarting after a safe save, was a suggestion without a success reply. Keep this case separate from competition boxes and Yui’s painting job.
NuclearDystopia / Rose Brigade — Steam, 2026-09-13
| Evidence | Recorded detail |
|---|---|
| Original report | No highlight; every part reportedly tried |
| Reply suggestion | Check assembly order and all visible screws; re-enter bench, then safely restart |
| Result / build | No original-poster success confirmation; build unspecified |
| Useful next evidence | Order type, To-Do, current layer and screws, build and before/after result |
The core repair loop
The official game description identifies disassembly, cleaning, replacing faulty parts, and reassembly as the heart of restoration.
- Accept and review the device
- Inspect and identify the likely fault
- Disassemble in a controlled order
- Clean accessible components
- Source and install the needed part
- Reassemble and complete the order
How to solder: normal mouse input or inactive grey lines?
For the normal PC interaction, select the soldering iron, move to an active guide line, hold the mouse button while tracing the line, then release. DankWestern described this sequence in an August 7, 2026 Steam reply (UTC); Meep also pointed to selecting the iron from the tool bag. Follow the controls displayed by your build rather than assuming a keyboard shortcut or a Steam Deck button.
If the line stays grey or the soldering prompt never appears after cleaning, that is a different problem. The original poster, NekoiNemo, explicitly distinguished this fault from learning the normal interaction. Use Soldering Not Working for the separate troubleshooting route and dated workarounds. Putting a part down and picking it up again is not a required first step for every normal soldering task. These are historical player descriptions, not a current-build test by ReStory Helper.
Do not turn every repair into a parts order
Cleaning and inspection exist for a reason. Confirm what the job actually needs before committing money to a replacement.
Treat organization as a tool
When several covers, boards, and fasteners are on the bench, finish one logical layer at a time. A calm order is faster than hunting for one forgotten screw at the end.
When a repair appears stuck
Re-check the task wording, inspect all reachable surfaces, confirm no fastener is still holding a layer, and verify that the replacement matches the fault. Save-and-reload advice will be documented only when a reproducible release-version issue is confirmed.
Diagnose before you remove parts
Start by reading the customer request and inspecting the assembled device. A symptom is not always the same thing as the failed component, so avoid buying a replacement merely because its name sounds related. Rotate the device, look for every fastener, and note which surfaces are still blocked. The useful question is not “what can I click?” but “what layer must come off before the next operation is possible?”
Once the device is open, preserve a consistent order. Work from the outer shell toward internal assemblies, finish one layer before starting another, and keep removed parts visually organized. ReStory simplifies real electronics work, but the game still rewards the same calm sequencing that makes a physical teardown understandable.
Cleaning is part of diagnosis
Official descriptions place cleaning between disassembly and replacement. Clean exposed pieces methodically instead of brushing random surfaces until the interface changes. If progress seems stuck, check whether another cover or component is hiding the remaining area. A visually small patch can be easy to miss when the device is rotated at an awkward angle.
The automatic ultrasonic bath is a later convenience confirmed by its associated achievement, but launch notes also mention gadgets becoming stuck in the sonic bath. When that happens, record the device and build before relying on an old workaround. Manual cleaning remains a useful fallback while checking current patch notes.
Replace only a supported fault
A replacement part costs money and can send you back to the browser, marketplace, or inventory. Confirm that the order or diagnosis supports the swap, then verify that the part matches the device. If the new part will not seat, re-check orientation, remaining fasteners, and whether an adjacent piece must be installed first.
Soldering and reprogramming appear as distinct progression systems in the public achievement list. They should not be treated as universal answers for every repair. Use the operation the job calls for, with the required equipment, and return to the normal assembly sequence once it is complete.
Recover from a repair that will not finish
First compare the task list with the current physical state of the device. Look for an uncleaned surface, a missing screw, a cable or board that has not been returned, or a replacement that is present but not fully installed. Rotate the object back to a neutral view and trace the teardown in reverse.
If the state appears correct, save the game and document the exact step before restarting. Check the official known-issues post and the Steam technical discussion board for the current build. Launch reports include firmware problems, an IDM device disassembly error, ultrawide disassembly issues, and gadgets stuck in the sonic bath, so a reproducible bug should not be confused with a missing repair step.
Bench-side diagnostic checklist
When a repair resists completion, troubleshoot in a fixed order. First, return to the ticket and confirm whether the requested outcome is cleaning, replacement, customization, firmware work, soldering, or a combination. Second, inspect the assembled exterior and count visible screws, covers, doors, cables, and removable modules. Third, open the device from the outside inward and stop after each layer long enough to see what became reachable. Fourth, clean every newly exposed target before assuming that a component must be replaced. Fifth, compare the observed fault with inventory and browser listings; a familiar-looking part from another device family may not be valid. Sixth, perform special operations only when the correct component is exposed and the required equipment is available. Seventh, rebuild in exact reverse order, checking orientation and seating before adding the next cover. Eighth, compare the restored device with the original assembled state and re-read the remaining task indicator. If those checks pass but the job remains blocked, document the platform, build, display mode, device, order source, part, and interaction. Then consult the newest official announcement and Steam technical discussions. This is particularly important for launch reports involving Guitar Legend or MyPod firmware, IDM disassembly, competition inventory, ultrawide views, and sonic-bath removal. A reproducible software issue needs different treatment from a forgotten screw, and recording the boundary saves other players from repeating the same dead end.
- Ticket: identify the requested operation and customer context
- Exterior: count fasteners and removable layers before disassembly
- Interior: expose one assembly at a time
- Cleaning: inspect every reachable face at a neutral camera angle
- Parts: match the device and demonstrated fault
- Special work: confirm soldering, firmware, or tool requirements
- Reassembly: reverse the teardown without skipping orientation checks
- Bug report: include build, platform, resolution, device, and exact blocked step
PC controller cursor and input checks
For a slow joystick cursor or a mapping that breaks rotation and cleaning, use controller-settings for a reversible, one-change-at-a-time checklist. It separates PC external controllers from Deck compatibility and does not promise a universal preset.
First Pokia cleaning: match the selected part to its dirt objective
Before choosing a brush, match the dirty component in the notebook to the part you have selected. Gab Smolders' launch-period recording shows Hashimoto's Pokia 3310 CLEAN order, a selected Front Panel moving toward the cleaning target beside the pencil cup, and a brush drawer opening. The panel's To-Do displays Remove dirt: 0%; the earlier reviewed sequence then shows 37% on that same panel. Use the selected part's name and dirt progress to distinguish an interaction that has not opened from brushing that makes no progress. A brush sound alone does not confirm success. Later footage switches to the Keyboard, so its percentage must not be counted as the Front Panel's result. This recording does not establish a current-build entry or exit shortcut, an explicit 100% result for the panel, or completion of the whole phone order. Follow the controls displayed by your build and record the part, objective and build if progress stays unchanged; do not delete your save or buy another tool as a promised fix.
Watch Gab Smolders’ original Pokia sequence from 4:51 (launch-period third-party footage)
