Hacking 3DS unbricking progress

  • Thread starter Thread starter krisztian1997
  • Start date Start date
  • Views Views 376,685
  • Replies Replies 1,233
  • Likes Likes 32
Status
Not open for further replies.
At least the Pi doesn't care about the write protect switch, the SD reader for the flash back might very well though. Good catch in advance.

good to know, because it can be a bit tricky with some sd to minisd adapters (and once i had no luck with the duc tape on the side )
and for the restore, i asume then you could do it like that
dd if=/mnt/data/nand.000 of=/dev/mmcblk0 bs=4096
 
this can be usefull if soldering to microSD adapter is too hard
$(KGrHqR,!hoE6mEkw0UoBOu(Zf2Rqg~~60_12.JPG
http://www.ebay.co.uk/itm/Micro-SD-Card-extension-cable-/111269245903
 
I just realized I hate no idea how to change the frequency on arduino... fuuu


Duct tape is your friend, put some over that side and it should work (that trick works since the VHS times)

Check out http://playground.arduino.cc/Code/Prescaler (and pay special attention to the fact that changing the clock via the prescaler also changes all time based stuff (like sleep() or wait()). also dont forget to change the spi clock divider then (http://arduino.cc/en/Tutorial/SPIEEPROM).

p.s. according to the last link 0x11 on SPCR already means 250kHz


good to know, because it can be a bit tricky with some sd to minisd adapters (and once i had no luck with the duc tape on the side )
and for the restore, i asume then you could do it like that
dd if=/mnt/data/nand.000 of=/dev/mmcblk0 bs=4096


aye. you just need to switch to a kernel with the SD drivers (for that reason one is included on the SD card ready to be copied over/renamed) and need to get the image on the pi (options include but are not limited to mounting an extra fat usb drive, growing the ext4 on the usb and send the dump per smb/scp, creating a new fat on the usb which needs some trickery on windows as it doesn't like partitions on removable drives (and when you want to be really manly and like living on the edge you could even do some crazy netcat tricks, but that's not for those faint at heart)).
 
it works better with the file RPU.zip on the stick usb . Thanks Biffkt


my 3DS XL found life :) .... Will send the picture
 
gratz :) 13 done, still X to go.

aww, mine only unbricked one :lol:. untill the guys from r4i are gonna find a way to unbrick, your code is gonna unbrick every bricked console.
I found this interesting document explaining how clock works on arduino https://sites.google.com/site/qeewiki/books/avr-guide/spi
About that single unbrick with my code, his shield using an IC for the voltage divider, thats why it worked
 
oh my, I cant believe that I forgot to look over that bug when not terminating the execution after every step... and that error is interesting, the 3DS should turn on when its not connected to any card reader without an error
My 3ds shows the error because is bricked.
What is new is that the error message doesn't change when plugged with the 5 wires solded, but does change when using only 4
 
My 3ds shows the error because is bricked.
What is new is that the error message doesn't change when plugged with the 5 wires solded, but does change when using only 4

Something is wrong with CS then... arduino is much harder to use than a raspi, if you can get a raspi instead and use bkifft's code. I will look into a problem but not sure if I can fix it because I dont know why that happens with your 3ds
 
I could not make it work with my 3ds XL =/.

When I put a normal SD card the program works correctly.

I am using Arduino UNO + SD Shield.

3ds eMMC Toshiba.

5 wire the SD card reader does not recognize the 3ds. = DAT3 ON
4 Wire the reader recognizes the 3ds with over 943 MB can not format. = DAT3 OFF.

Erro with 3ds.

Enabled outputs/inputs
Initialized SPI with 250khz frequency
Waiting the minimum 80 cycles for warm up
Keeping CS line on low for communication0

Reset command sent on MOSI, but no answer from the slave. Please check your card connection/soldering
Initialization failed
Retrying...
Enabled outputs/inputs
Initialized SPI with 250khz frequency
Waiting the minimum 80 cycles for warm up
Keeping CS line on low for communication0

Reset command sent on MOSI, but no answer from the slave. Please check your card connection/soldering
Initialization failed
Retrying...
Initialization failed after several retries
 
Same error here.
Since i saw the message "Reset command sent on MOSI, but no answer from the slave. Please check your card connection/soldering" i though that maybe something was wrong with my solderings between the 3DS and the SD card adapter, so today I went ahead and recheck everything from the start.
The board solderings seem fine:

vpuha8.jpg


Then I cut the SD Adapter and made a new one:

zvyntd.jpg


I even shortened the cables a bit just in case:

fu143q.jpg


After all the rechecks I tried again the code without success.

I also decided to retry with the SDcard that didn´t work yesterday (Kingston 128mb). I thought that I missed the step of terminating the program execution and that was why it failed, but i was wrong!
For some reason, even doing every step the card remains unlocked and cannot be erased.
I wonder whats different between the two cards I tested.
 
The code works partially, at least I tested it ok with and SD card.
The thing is, apparently there is a detail missing to make it work 100% of the times.
In fact I was wondering if I could identify the diference between the 2 Sd cards I tested. Maybe that would give some clue of what works and what not.
 
Tested once again with my 3DS.
This wierd error happens:

Enabled outputs/inputs
Initialized SPI with 250khz frequency
Initialization failed
Retrying...
Enabled outputs/inputs
Initialized SPI with 250khz frequency
Waiting the minimum 80 cycles for warm up
Keeping CS line on low for communication255
255
255
255
255
255
255
.
.
.

Reset command sent on MOSI, but no answer from the slave. Please check your card connection/soldering
Initialization failed
Retrying...

Initialization failed after several retries
 
Something is wrong with CS then... arduino is much harder to use than a raspi, if you can get a raspi instead and use bkifft's code. I will look into a problem but not sure if I can fix it because I dont know why that happens with your 3ds
We need to see the response of each CMD sent when using 3ds
 
We need to see the response of each CMD sent when using 3ds

Look at the post above, all that 255 255 255 is the response from the card after I send the reset... something is very wrong with it.

The code works partially, at least I tested it ok with and SD card.
The thing is, apparently there is a detail missing to make it work 100% of the times.
In fact I was wondering if I could identify the diference between the 2 Sd cards I tested. Maybe that would give some clue of what works and what not.

I got a kingstone too which fails to lock because mine had the lock feature disabled, but the code works perfectly with SD and MMC cards, I tried over 6-7 different cards, one of them is 11 years old and it works, except that it cant report if its locked or unlocked
 
In case my kingstone card have the lock feature disabled, shouldn't at least the erase option work?
I tried that with data in the card and was still intact when plugged back to the pc
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum