Hardware Help needed with 2 broken DSi

[Naendow]

Hey

I've ordered some DSi's from Japan for an insanely cheap price. Surprisingly most of them work and look pretty good. Two of them have a few problems.

The first one immediately showed an error message after boot. After replacing the Wifi module, it boots and shows the boot animation. After pressing any button it shows an error message again. I am sure that the WiFi module works this time, but I have no clue what else could be the problem. I also tried to put the mainboard into another console without any luck. A modding related brick would be possible I think, but that would be pretty bad because Unlaunch doesn't seem to be installed.
The second device behaves really weird. It boots and work like a charm when I remove the back case, but doesn't when it is reassembled. I tried to start the device and put it together at the same time, which resulted into a glitching screen and a pretty loud noise that sounded like a broken menu music loop. No idea what happens there.


If anyone has an idea how I could save at least one console, I would be very grateful. Even if this was an insanely good deal (50 Euro with shipping included for 6 DSis and 1 DSi LL, all of them working besides the 2 described above), it would be a bummer to have 2 junk consoles.

 

[xonn]

Recently, I have repaired a DSi that thrown an error just after start any program. The problem was in bios/wifi module, not the module itself but the connection, I think the console access inside before launching an app, and if there's any problem in communication, it abort operation and shows the error.
The solution was looking a good position for this piece, putting some paper underneath to tilt it slightly (trial and error method). Now it works flawlessly!

 

[Naendow]

Thanks for your tip. I'll try this when I get back from work.

 

[Amez]

For the first one, the camera can cause the issue of it showing an error message after boot up.

The second one, sounds like a short, try the bottom from the other console it, if it still happens - try swapping the bottom screen.