Hardware Need help troubleshooting an O3DS

  • Thread starter Deleted User
  • Start date
  • Views 1,254
  • Replies 8
D

Deleted User

Guest
OP
My friend gave me his O3DS and told me if I fix it, I can keep it. Pretty nice of him considering I'm poor as hell. Problem is, it doesn't read 3DS games, and if I open Settings it tells me "An Error Has Occurred" after 10 or so seconds. It does the same on the home screen too but after 30 or so seconds.

I'd update it through the button press on boot but I can't stay on settings long enough to put in my internet settings, and it's bang on 9.2.0-20E, so I'd like to mod it.

What could be causing it, and how would I fix it?
 
Last edited by ,
D

Deleted User

Guest
OP
I don't seem to have the correct size screwdriver, so I'll head out tomorrow and get one, then post pics.
 
D

Deleted User

Guest
OP
Finally got it open. Here's a pic plus close ups. 1481398138670297397709.jpg 1481398164003-1487583363.jpg 1481398138670297397709.jpg 1481398164003-1487583363.jpg 1481398190653-523689536.jpg
 
D

Deleted User

Guest
OP
sounds like your friend tried to downgrade it and failed.
He said it's completely stock, and I believe what he said. The screws weren't marked and there wasn't any sign of it being open before.
 

nero99

Well-Known Member
Member
Joined
Sep 18, 2014
Messages
3,135
Trophies
1
Age
31
XP
3,729
Country
United States
He said it's completely stock, and I believe what he said. The screws weren't marked and there wasn't any sign of it being open before.
just because it wasn't opened before doesn't mean they couldn't have tried to downgrade from 10.x to 9.2 and ended up with a franken firmware. the system won't just throw that error for no reason, and if the cables were broken or out of place, the system would not boot up past a black screen.
 
D

Deleted User

Guest
OP
just because it wasn't opened before doesn't mean they couldn't have tried to downgrade from 10.x to 9.2 and ended up with a franken firmware. the system won't just throw that error for no reason, and if the cables were broken or out of place, the system would not boot up past a black screen.
I guess so. How should I go from here? There's no obvious damage, but the problem is still there.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Xdqwerty @ Xdqwerty: good night