Hacking HELPPPPPP, GATEWAY problem !!

  • Thread starter Thread starter CyHo
  • Start date Start date
  • Views Views 2,954
  • Replies Replies 10

CyHo

Well-Known Member
Newcomer
Joined
Oct 28, 2016
Messages
79
Reaction score
9
Trophies
0
Age
30
XP
219
Country
Malaysia
my friend have installed config.cia into Gateway emunand, 3ds was hang after install, after power off, I can't power on 3ds even remove gateway. Don't even have a blue light when boot. Any idea?

HELPPPPPPPPP
 
Don't blame your friend at first.
Does it start without a SD card?
yes, is already remove the gateway and SD
What boot method did it use before? (Please don't say Gateway Fastboot...)
not fastboot, normal boot with Setting, profile, ds profile

EDIT:
It is a hardbrick? need to use hardmod to flash the nand.bin back
 
Last edited by CyHo,
yes, is already remove the gateway and SD

not fastboot, normal boot with Setting, profile, ds profile

EDIT:
It is a hardbrick? need to use hardmod to flash the nand.bin back
Ew~ MSET.
You will most likely need to restore a NAND backup the emuNAND. Chances are the CIA you flashed corrupted the emuNAND. If they don't have a NAND backup, I honestly suggest ditching the emuNAND/Gateway and going with A9lH+CFW
https://3ds.guide/
 
But does it WORK without the SD? AS in you can use everything but Gateway? If so, it's not bricked. It's just a corrupted EmuNAND. You have to make a new one, but you'll lose all your saves.
 
It sounds to me like either the New 3DS's lithium-ion battery has run out or is not connected. If a blue light doesn't come on, it usually means there's no power supplied to the system itself.

But if the battery is fully charged and the light still doesn't come on, then I'm really sorry to say, that your New 3DS's MCU has been destroyed (in other words, a component on the N3DS motherboard). And if this really is the case, then I'd say someone installed an incorrect DevMenu.cia for the wrong system, as there are different ones for each system. There's ones for PANDA units (Original 3DS), and there's ones for SNAKE units (New 3DS). If someone was trying to install a DevMenu.cia, it needs to be for the correct system.

But if it really was a config.cia, it's quite possible that one from a O3DS was installed onto a N3DS (which can destroy the MCU).
 
Ew~ MSET.
You will most likely need to restore a NAND backup the emuNAND. Chances are the CIA you flashed corrupted the emuNAND. If they don't have a NAND backup, I honestly suggest ditching the emuNAND/Gateway and going with A9lH+CFW
https://3ds.guide/
He did have nand.bin backup, but is only hardmod can flash the nand.bin back right.
But does it WORK without the SD? AS in you can use everything but Gateway? If so, it's not bricked. It's just a corrupted EmuNAND. You have to make a new one, but you'll lose all your saves.
No, didn't work even take out the SD
It sounds to me like either the New 3DS's lithium-ion battery has run out or is not connected. If a blue light doesn't come on, it usually means there's no power supplied to the system itself.

But if the battery is fully charged and the light still doesn't come on, then I'm really sorry to say, that your New 3DS's MCU has been destroyed (in other words, a component on the N3DS motherboard). And if this really is the case, then I'd say someone installed an incorrect DevMenu.cia for the wrong system, as there are different ones for each system. There's ones for PANDA units (Original 3DS), and there's ones for SNAKE units (New 3DS). If someone was trying to install a DevMenu.cia, it needs to be for the correct system.

But if it really was a config.cia, it's quite possible that one from a O3DS was installed onto a N3DS (which can destroy the MCU).
Yea, i feel weird on this as well
 
Last edited by CyHo,

Site & Scene News

Popular threads in this forum