Kit PSUs, recovery images, and the retail USB that bricks a desk
Classifieds photos crop the power brick. That is how a 203W retail Slim PSU ends up on a kit that wanted a different connector or a different budget of amps, or the reverse: a roaring XDK brick on a Corona that does not need it. I log this because “it powered on once” is not a compatibility chart. Kits already sound like aircraft. Wrong PSU makes them smell like aircraft.
Bricks are part of the SKU
Retail Phat, Slim, and E bricks are a known matrix (and a known market of fire-hazard clones). Kit bricks are labeled like they were never meant to sit in a living room. If the seller cannot show the brick, price the kit as incomplete. Do not “just use the Slim brick from the RGH3 Trinity on the same shelf.” Neighborhood will not fix a sagging 12V rail.
Recovery is not dashboard 17559 from a Bad Update stick
Retail recovery and kit recovery are different rituals. A USB that installs NXE 17559 so Bad Update 1.3 can run is a retail story. Pointing that at an XDK because “it’s also a 360” is how archives get quieter. Keep kit recovery images named with the hardware type, not update.zip. Keep retail dumps on the retail PC user profile. I have watched a well-meaning friend “update the loud one” after reading a Corona Notes tab.
SDK installers on a modern Windows host are their own museum: old Visual Studio eras, old Neighborhood, certificates that expired in spirit if not on disk. That does not make a kit into an RGH3. It does not inject kv.bin. See SDK and unsigned code.
If the machine in the photo is actually a Slim, stop reading kit PSU threads and go back to retail vs XDK. Most emails are retail.