I can't say, I've never seen this kind of error before on a 3DS that hasn't been hacked with. I think €30 is pretty much for a non-working 3DS, considering that here in the Netherlands, working 3DS from the first model are sold for €50 or less.
I saw earlier in this thread that both the gauge and length of the wire can affect your success. You might want to check that.already tested with SD reader Sandisk Kingston tested with SD and USB No player 'm finding that nand this fire because it does not recognize .
The strange that he is with black screen
now I caught a sd reader samsung
Okay thanks I read it on some forums that som people had this issue and took the battery out and rebooted the 3DS normally. But I will take your advice and not buy it. I just wanted a 2nd system to have CFW and toy around to see what the system can do.I'm gonna guess that never has taking the battery out and replacing it fixed a boot rom error. Save your money, it's not happening. Sorry.
Sent from my A0001 using Tapatalk
I can't say for sure, but if they're not gonna let you try it first then don't give them money. You can get a working used 3ds at pawnshops etc for very little more. As far as I know, when you get one of those blue screens your pretty much beat unless you have a backup.Okay thanks I read it on some forums that som people had this issue and took the battery out and rebooted the 3DS normally. But I will take your advice and not buy it. I just wanted a 2nd system to have CFW and toy around to see what the system can do.
yeah unless you can get it dirt cheap this error isn't guaranteed to be caused by the GW brick code, its basically just means the 3DS can't boot, if they are saying they just swapped the battery and it did that then its probably not GW related and would be something else wrong, possibly water damage that took a while to kick in, if you can get the system for so cheap that it is worth the value in parts, and you may get luck and its just a simple fix like a loose wifi card or something (although iirc a loose wifi card gives a black screen, but you get the idea)
Just means that communication with the eMMC/NAND was not possible. It could be broken for good, or you could have a problem with your wiring.Hi community!
I have not managed to Dumper a HITACHI thgbmbg4.par usb reader usual
At best windiskmanger see the disk, but error 483 at the dump.
I wanted to use alternate point then black screen, then stops, as low screen HS
Carry out several tests, certain it is the motherboard.
Then use PI for unlock, unbrick, but more access to nand
Switch boot / SD then I get loed blue but not init
Could you tell me what this error is?
The nand is HS ?, Brick?
Thank's you so much
thank you for your reply.
I understand.
Can I be sure of it in any way?
Very kind to you to confirm me
--------------------- MERGED ---------------------------
I check resistance of the important point and compare to those of a functional 3ds.
To the multimeter nothing alarming, except that the CLK oscillates but does not give good tension.
In any case no C.C.
Would it be a hope? If only to successfully dump
I read some pars that fed the nand with other 3DS was possible, I would like to try ... I know more or follow the lesson ... diagram ...
Do you know where to find the page?
From what I read a long time ago gateway changed the brick code unlock key method used on all FW's after 2.0b2@bkifft, hey mate!
Here I am bringing an old topic back to life!
3 years after we have seen your (and @krisztian1997's) program I have received another console bricked like that! It's almost 2 years since my last Gateway brick.
So I dusted off my old RPi 1 (which was safe in a place along with the USB and SD I used to do such work) and proceeded to unbrick this console.
I can read the NAND successfully and see the MMC is locked but when I try to unlock it I get the same error @Jad67tony got (CTO_ERR and ERR = 1).
I know the hardmod is working properly because I can see Windows mounting a drive letter when I plug the console in and because RPU can read the MMC state.
Can you help me with any ideas?
PS: the cable is reeeealy short. Probably 7-8cm long.
EDIT:
I don't know if this will help (or if it matters) but the NAND chip brand is SAMSUNG.
Does this chip work with RPU code?
EDIT 2:
well, force erase worked!
Good thing I had the NAND backup
Still, I would like to understand why the UNBRICK option didn't work.
@bkifft, any advises is heavily appreciated!
From what I read a long time ago gateway changed the brick code unlock key method used on all FW's after 2.0b2
Just wondering if you have more info on how the console bricked, was it using a dstwo or someone messing about trying to hack the GW launcher?
i second "lock/unlock key changed".
And to my knowledge noone has looked into it any further
This new type of brick is due to DSTWO PLUS use.@bkifft, hey mate!
Here I am bringing an old topic back to life!
3 years after we have seen your (and @krisztian1997's) program I have received another console bricked like that! It's almost 2 years since my last Gateway brick.
So I dusted off my old RPi 1 (which was safe in a place along with the USB and SD I used to do such work) and proceeded to unbrick this console.
I can read the NAND successfully and see the MMC is locked but when I try to unlock it I get the same error @Jad67tony got (CTO_ERR and ERR = 1).
I know the hardmod is working properly because I can see Windows mounting a drive letter when I plug the console in and because RPU can read the MMC state.
Can you help me with any ideas?
PS: the cable is reeeealy short. Probably 7-8cm long.
EDIT:
I don't know if this will help (or if it matters) but the NAND chip brand is SAMSUNG.
Does this chip work with RPU code?
EDIT 2:
well, force erase worked!
Good thing I had the NAND backup
Still, I would like to understand why the UNBRICK option didn't work.
@bkifft, any advises is heavily appreciated!