Hacking 3DS unbricking progress

  • Thread starter Thread starter krisztian1997
  • Start date Start date
  • Views Views 376,341
  • Replies Replies 1,233
  • Likes Likes 32
Status
Not open for further replies.
Guys,

I'm trying the Rasp method since my Arduino still didn't arrive. I still don't have any bricked 3DS but I decided to give a shot with my own. It's not bricked so I'll only run the s (status) command.
I flashed the SD and my USB with the kernel image and put the RPU.zip (formally master.zip) into the USB.

Plugged the HDMI, the USB and the keyboard. Turned the Rasp on and after some time I looged in and ran the 3dsunbrick command. Some seconds later I was presented with the options.
Then I removed the SD, plugged my cable (4 wires) into my not bricked 3DS and turned it on. Blue screen came in, so I plugged the SD cable into Rasp and typed s (lowercase) and hit ENTER.
Then I got this screen and I, honestly, don't know it it's ok or not.

https://www.dropbox.com/s/6h267pmwacb37lu/IMG_20140201_143918.jpg

Can anyone tell me if this is the expected output for a not bricked 3DS status?

Thanks in advance!

For some reasons it failed to get the CSD (did you unplug the card or hit it accidentally ?), but everything else is fine.
Edit: Whoops, didnt saw that two errors are set to 1... look like CCRC error bit is set, bkifft can tell you why that happened, but I have no idea about it
 
Guys,

I'm trying the Rasp method since my Arduino still didn't arrive. I still don't have any bricked 3DS but I decided to give a shot with my own. It's not bricked so I'll only run the s (status) command.
I flashed the SD and my USB with the kernel image and put the RPU.zip (formally master.zip) into the USB.

Plugged the HDMI, the USB and the keyboard. Turned the Rasp on and after some time I looged in and ran the 3dsunbrick command. Some seconds later I was presented with the options.
Then I removed the SD, plugged my cable (4 wires) into my not bricked 3DS and turned it on. Blue screen came in, so I plugged the SD cable into Rasp and typed s (lowercase) and hit ENTER.
Then I got this screen and I, honestly, don't know it it's ok or not.


...

Can anyone tell me if this is the expected output for a not bricked 3DS status?

Thanks in advance!
Delete this photo!
Don't show your CID number.
 
Delete this photo!
Don't show your CID number.

Because all those eMMC chips were mass manufactured and only installed by ninty and not made by themselves, I dont think that its traceable or that ninty keeps a database of every chip and every serial number... they dont even keep the serial of the mobo, if you lose your case with the serial on it they cant recover your 3DS account or transfer it if your console broke.
 
Guys,

I'm trying the Rasp method since my Arduino still didn't arrive. I still don't have any bricked 3DS but I decided to give a shot with my own. It's not bricked so I'll only run the s (status) command.
I flashed the SD and my USB with the kernel image and put the RPU.zip (formally master.zip) into the USB.

Plugged the HDMI, the USB and the keyboard. Turned the Rasp on and after some time I looged in and ran the 3dsunbrick command. Some seconds later I was presented with the options.
Then I removed the SD, plugged my cable (4 wires) into my not bricked 3DS and turned it on. Blue screen came in, so I plugged the SD cable into Rasp and typed s (lowercase) and hit ENTER.
Then I got this screen and I, honestly, don't know it it's ok or not.

https://www.dropbox.com/s/6h267pmwacb37lu/IMG_20140201_143918.jpg

Can anyone tell me if this is the expected output for a not bricked 3DS status?

Thanks in advance!

That's strange indeed... I'll have to lookup what exactly the CRCerror was(believe command crc, will know for sure soon).

But i'd also advise you to blurr out your CID, as even though Ninty is not sure to have them on record one never knows.
 
Can anyone please answer this post I made the other day. No one has answered it yet:

Since you guys seem to know a lot about the technical specs of the 3DS, can any of you answer this question; Can the 3DS really update he FPGA of the Pro ASIC chip inside flashcarts, or not?

Ratman9977 said: ↑ Gateway can't update the FPGA at all -- it's impossible without a JTAG debugger, which the nintendo 3ds is not. The best they could do -- is if they used a softcore with an external rom containing the code -- is to update that via SPI. In that case, the clones would be able to perform the same action.
Ratman9977 said: ↑ Gateway can only use those JTAG inputs with an external tool to program the FPGA. The 3DS itself is not a JTAG programmer, therefore the FPGA design cannot be updated on either the Gateway orbclones from the 3DS itself.
 
Can anyone please answer this post I made the other day. No one has answered it yet:

we did answer that question... from what we know its not posible to do it with the 3ds, but maybe they will update it in a different way (flash something from the sd card to a special part of the FPGA if that is posible).
 
Delete this photo!
Don't show your CID number.


oops! Done!

So, the SD cable works as I can read/write my NANDs to my 3DS.
Everything is well placed. The SD card lock (in both the kernel SD and the SD cable) is up, which means unlocked. When the Linux was booting I noticed only one fail related to IEEE (network).

Any other advises? What should I try?

PS: What would be a good output for a unlocked status?

Thanks!
 
mvmiranda . ok, that error shouldn't happen, especially as it did transfer the (seemingly) correct CSD (the content of the four response registers at the bottom of your picture).

CCRC_ERROR (command crc error) should (as in "thanks broadcom for telling me to look it up in a non public datasheet") mean that the pi didn't get a correct crc reply while running the command.

has it only happened once or does it happen constantly? also have you already been able to dump your nand successfully? edit: scratch that question, was typing while you posted your last reply

edit: a good output should look like http://www.virtualdrive.cc/putty3dsd.jpg (taken from http://www.moddingstudio.com/content.php?1697&ModPagespeed=noscript)
 
mvmiranda . ok, that error shouldn't happen, especially as it did transfer the (seemingly) correct CSD (the content of the four response registers at the bottom of your picture).

CCRC_ERROR (command crc error) should (as in "thanks broadcom for telling me to look it up in a non public datasheet") mean that the pi didn't get a correct crc reply while running the command.

has it only happened once or does it happen constantly? also have you already been able to dump your nand successfully?


Well, I think I screwed up here :P LOL
First, the kernel SD was LOCKED and then at the update process (when the RPU.zip was extracting the files) must have failed without giving me errors.
When I noticed the SD was locked I unlocked it and powered the Rasp again (but the RPU.zip was not there, thus it didn't extracted any files).

I think that was the problem since there's nothing related to the RPU.zip in the SD nor USB stick.

Am I right?
 
mvmiranda . ok, that error shouldn't happen, especially as it did transfer the (seemingly) correct CSD (the content of the four response registers at the bottom of your picture).

CCRC_ERROR (command crc error) should (as in "thanks broadcom for telling me to look it up in a non public datasheet") mean that the pi didn't get a correct crc reply while running the command.

has it only happened once or does it happen constantly? also have you already been able to dump your nand successfully? edit: scratch that question, was typing while you posted your last reply

edit: a good output should look like http://www.virtualdrive.cc/putty3dsd.jpg (taken from http://www.moddingstudio.com/content.php?1697&ModPagespeed=noscript)


It happens all the time!

I'll try again this time with the SD unlocked and I'll put the RPU.zip inside the USB again.
 
It happens all the time!

I'll try again this time with the SD unlocked and I'll put the RPU.zip inside the USB again.

Shouldn't be the reason as the raspberry pi ignores the write protect switch.

And on closer examination that "seemingly correct CSD" isn't that correct any more. somehow the communication got garbled up at that point: vibration, power fluctuation, solar flare, ghosts, etc.

edit: in case the problem persists: could you please send me the RPU_log.txt file from the usb stick?
 
Shouldn't be the reason as the raspberry pi ignores the write protect switch.

And on closer examination that "seemingly correct CSD" isn't that correct any more. somehow the communication got garbled up at that point: vibration, power fluctuation, solar flare, ghosts, etc.

edit: in case the problem persists: could you please send me the RPU_log.txt file from the usb stick?


My SD cable has around 27cm long.

Now I'm not receiving my CID again.
SND_send_init: error occured whilst waiting for command complete interrupt
Everything is 0, except CTO_ERR and ERR
RESP3, 2 and 1 are 0
RESP0 is 0x03FE040F

SD_init: no CMD1 (0) response

What the heck!
 
CTO is the command timeout...

could be your cable is to long for the preset clock frequency. give me a few timeunits (need to get everything set up again) to lower it


edit: re power: could, but shouldn't be the case, at least if your usual cardreader is usb powered.
 
how about turn on your 3ds after you plug the sdmod in raspi.
in rpu_guide txt:
"13) Plug in the SDmod card connected to your 3DS and turn the 3DS on."

here's mine:
testing the RasPi based 3DS unbricker in "Querry only" on my 3ds LL.
2014-01a.jpg
2014-0133.JPG

thanks, bkifft.
 
how about turn on your 3ds after you plug the sdmod in raspi.
in rpu_guide txt:
"13) Plug in the SDmod card connected to your 3DS and turn the 3DS on."

here's mine:
testing the RasPi based 3DS unbricker in "Querry only" on my 3ds LL.

thanks, bkifft.


Trying... thx m8!
 
how about turn on your 3ds after you plug the sdmod in raspi.
in rpu_guide txt:
"13) Plug in the SDmod card connected to your 3DS and turn the 3DS on."

here's mine:
testing the RasPi based 3DS unbricker in "Querry only" on my 3ds LL.

thanks, bkifft.


Didn't work!
I switched back to USB cable plugged to my notebook and did like this:

Switched off 3DS (pulled be battery), pluggled the SD cable, plugged the 3DS to Rasp then turned the 3DS on. The blue screen came and then I run the "s" option.

Now I see my CID again but still the first error...
 
we did answer that question... from what we know its not posible to do it with the 3ds, but maybe they will update it in a different way (flash something from the sd card to a special part of the FPGA if that is posible).

Okay, but will this "different way" require the JTAG pins to do the flash, or can they do it another way?
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum