Hacking 3DS unbricking progress

[tobelight]

Hello
I test the unbrick 3DS xl with the raspberry . I have a problem when i tape F , there is no action and the screen display (S)afe , (F)orce ....(loop)
If i tape S, I have the message MMC is locked

Thank for your help

Tobelight

 

[bkifft]

Hello
I test the unbrick 3DS xl with the raspberry . I have a problem when i tape F , there is no action and the screen display (S)afe , (F)orce ....(loop)
If i tape S, I have the message MMC is locked

Thank for your help

Tobelight

as your pi isn't connected to the internet do the offline update as described in step 3b.

 

[tobelight]

yes i am not connected to the internet and i have put the RU.ZIP on the sd card .

I am test my SD CARD (mod) because I think it 's locked

ps: sorry for my english

 

[bkifft]

yes i am not connected to the internet and i have put the RU.ZIP on the sd card .

I am test my SD CARD (mod) because I think it 's locked

ps: sorry for my english

please do it again as for some reason it didn't do the update. make sure to name the file "RPU.zip" (big letters for the RPU, small letters for the zip)

 

[mvmiranda]

i highly suspect it's your cable length (edit: or some interference) as the different responses mean that the transmission gets somehow garbled up.

anyway: i reduced the clock to the smallest possible value, please try it: https://drive.google.com/file/d/0B4Gv-RnAT-F_VnJQd3Izc2xVUVU/edit?usp=sharing (even though its way smaller than an usual update package just put it on the usb)

Should I just put the main.c inside the USB stick?

 

[bkifft]

Should I just put the main.c inside the USB stick?

nope, the RPU.zip (you can repack the main.c as RPU.zip if you want or redownload the whole zip from google drive)

 

[mvmiranda]

nope, the RPU.zip (you can repack the main.c as RPU.zip if you want or redownload the whole zip from google drive)

got it...

I'll take the RPU.zip I have and replace the the main.c inside the zip with this one.

k?

 

[bkifft]

got it...

I'll take the RPU.zip I have and replace the the main.c inside the zip with this one.

k?

aye, works fine too. but the update process is only "if there is an RPU.zip extract it to the tool folder". and as the other files are already updated the main.c would be enough

 

[mvmiranda]

nope, the RPU.zip (you can repack the main.c as RPU.zip if you want or redownload the whole zip from google drive)

Success!

You rock bkifft !

Thx m8!
Will send the picture soon

 

[bkifft]

Success!

You rock bkifft !

Thx m8!
Will send the picture soon

thank you for doing such a sloppy solder work to show me that i can lower the clockrate even further ;P (jk)

 

[mvmiranda]

thank you for doing such a sloppy solder work to show me that i can lower the clockrate even further ;P (jk)

You're welcome... I guess
It could be the length of the cable too? Cause the solders are ok for me. I've been doing this for quite so long and I've never seen such thing... Although I've never worked with eMMC and such delicate circuits pulses.

If you say it's really the solder, i'll review my skills AhHAHHAhAhAhA

 

[krisztian1997]

thank you for doing such a sloppy solder work to show me that i can lower the clockrate even further ;P (jk)

what frequency you used ? maybe the problem is that I initialize the card on too high frequency with my arudino code

 

[bkifft]

You're welcome... I guess
It could be the length of the cable too? Cause the solders are ok for me. I've been doing this for quite so long and I've never seen such thing... Although I've never worked with eMMC and such delicate circuits pulses.

If you say it's really the solder, i'll review my skills AhHAHHAhAhAhA

Nah, just pulling your leg in regards to the soldering. could be a bunch of things (cable length, cable quality (twisted, shielding, etc) high frequency sources around you (old CRT style tv, powerline in front of the house etc), etc).

I just cut quite a few corners with the tool and used a fixed clockrate of about 400kHz, regular SD readers check for such errors and simply reduce the clockrate until they can't reduce it any more or the errors are gone.

but as the unlocking doesn't need a huge amount of data to be transferred there's no need to use a high clockrate at all, so I'll just leave it at the minimum possible.

what frequency you used ? maybe the problem is that I initialize the card on too high frequency with my arudino code

250-ish kHz (edit: to be more precise: the ARM core on the Pi has a base clock of 250 MHz, biggest possible clockdivider is 0x3FF, so 244379 Hz.)

 

[mvmiranda]

Nah, just pulling your leg in regards to the soldering. could be a bunch of things (cable length, cable quality (twisted, shielding, etc) high frequency sources around you (old CRT style tv, powerline in front of the house etc), etc).

I just cut quite a few corners with the tool and used a fixed clockrate of about 400kHz, regular SD readers check for such errors and simply reduce the clockrate until they can't reduce it any more or the errors are gone.

but as the unlocking doesn't need a huge amount of data to be transferred there's no need to use a high clockrate at all, so I'll just leave it at the minimum possible.
...

Phew!
Thx God my solder skills don't suck then... Or at least lets think this way.

Again, good job!

 

[tobelight]

I still have the same error: no action when I F (the file RPU.zip Ok on my sd card)

 

[bkifft]

I still have the same error: no action when I F (the file RPU.zip Ok on my sd card)
it attached screenshot of problem and my connectivity

View attachment 6245View attachment 6246View attachment 6247

snarky reply: do step 3b) of the instructions.

friendly reply: the update file has to go on the USB stick, not the SD card

edit: oh, the "MMC is locked" means you got the launcher.dat brick, so the unlock will work (just remember: you need your own NAND backup)

 

[jochem77]

I still have the same error: no action when I F (the file RPU.zip Ok on my sd card)
it attached screenshot of problem and my connectivity

View attachment 6245View attachment 6246View attachment 6247

Maybe because the micro SD adapter hasn't got the lock switch, so it is read only?

 

[bkifft]

Maybe because the micro SD adapter hasn't got the lock switch, so it is read only?

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.

 

[krisztian1997]

Nah, just pulling your leg in regards to the soldering. could be a bunch of things (cable length, cable quality (twisted, shielding, etc) high frequency sources around you (old CRT style tv, powerline in front of the house etc), etc).

I just cut quite a few corners with the tool and used a fixed clockrate of about 400kHz, regular SD readers check for such errors and simply reduce the clockrate until they can't reduce it any more or the errors are gone.

but as the unlocking doesn't need a huge amount of data to be transferred there's no need to use a high clockrate at all, so I'll just leave it at the minimum possible.



250-ish kHz (edit: to be more precise: the ARM core on the Pi has a base clock of 250 MHz, biggest possible clockdivider is 0x3FF, so 244379 Hz.)

I just realized I hate no idea how to change the frequency on arduino... fuuu

Maybe because the micro SD adapter hasn't got the lock switch, so it is read only?

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

 

[Coto]

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)

there was a configurable IO with the clockrate and the divider iirc

edit: http://arduino.cc/en/Reference/SPISetClockDivider