Hacking Imported a 8.1J N3DS (Need Setup Assistance)

[cultopi]

Nope, I'm still trying to get a copy of CN jp. But there are already people who have got it working with their own server, and there's no reason for it not to work

well, if that is so, I hope they release it soon with a public server.

 

[Tokiopop]

well, if that is so, I hope they release it soon with a public server.

The issue with that is the firmware files would also need to be hosted, which is a bit of a legal issue - and the only reason I'm not going to host it on my server

 

[Dean_]

Nope, I'm still trying to get a copy of CN jp. But there are already people who have got it working with their own server, and there's no reason for it not to work

Nintendo is not an idiot. 3DS only downloads update files from HTTPS authenticated server.
Update using a private server is simply not possible.

 

[Tokiopop]

Nintendo is not an idiot. 3DS only downloads update files from HTTPS authenticated server.
Update using a private server is simply not possible.

Considering Yifan Lu's method involves changing the server the 3DS looks for to a non https server...

 

[Dean_]

Considering Yifan Lu's method involves changing the server the 3DS looks for to a non https server...

That trick was possible only before the removal of some update files from their server.

 

[X_Frost]

You can boot NTR via Cubic Ninja and update.

Sadly, I can't use Cubic Ninja as I need the browser, OoT is the only option I see at the moment

 

[Dean_]

You can boot NTR via Cubic Ninja and update.

False

How does that help him update? It'll still be the exact same problem. The old 8.1 to 9.0-9.2 update method that uses NTR-CFW hasn't worked since Nintendo decided to remove old firmware versions from NUS.

True

The update files are still available, you can run your own server and use Yifan Lu's method.

It's as if you people don't look at one of the most active threads on this board

Partially unavailable (cannot be used to update)
False

Guys, currently there is *no* known method that updates 8.1J devices to 9.0-9.2.
That applies on N3DS with downgraded MSET.
Don't give people false hope.

 

[Tokiopop]

There's literally a thread where people have done it and both of you are saying otherwise. I'm done

 

[Dean_]

There's literally a thread where people have done it and both of you are saying otherwise. I'm done

When did you update yours? It WAS possible.
After since Nintendo removed some files(NATIVE_FIRM, BROWSER, etc.), that method is now broken. That is what I am saying.

 

[Tokiopop]

That trick was possible only before the removal of some update files from their server.

When did you update yours? It WAS possible.
After since Nintendo removed some files(NATIVE_FIRM, BROWSER, etc.), that method is now broken. That is what I am saying.

I am fully aware the files were removed, and it has not stopped people. It literally does not matter.

The original method never connected your 3DS directly to Nintendo's servers. It changed the 3DS to connect to a non-HTTPS server, so there is literally no issue with authentication problems. Your 3DS only ever communicated with the server on your computer, which made the responses for the 3DS. You can just host the firmware files that the original script grabbed from Nintendo yourself.

 

[Dean_]

I am fully aware the files were removed, and it has not stopped people. It literally does not matter.

The original method never connected your 3DS directly to Nintendo's servers. It changed the 3DS to connect to a non-HTTPS server, so there is literally no issue with authentication problems. Your 3DS only ever communicated with the server on your computer, which made the responses for the 3DS. You can just host the firmware files that the original script grabbed from Nintendo yourself.

OK. I get that part. Is it publicly available now? If that is not the case, debate is meaningless.

 

[Tokiopop]

OK. I get that part. Is it publicly available now? If that is not the case, debate is meaningless.

Is what publicly available, the firmware files? I uploaded them to 'that site' earlier this week

 

[Dean_]

Is what publicly available, the firmware files? I uploaded them to 'that site' earlier this week

Not the firm files.
Are methods for hosting servers, redirecting, etc. public?

 

[enarky]

If the method from that other thread works it should be pretty straight forward, like Tokiopop says everything is available and documented. Filesizes differ from the XML responses when converting the available update files back from CIA, but writing a script for that should be pretty easy. I assume the filesize difference was one of the last problems I had before trying it myself, that's why I shelved that idea for after my vacation.

 

[dpad_5678]

8.1J :
You cannot update it to 9.0~9.2
You cannot use any CFW
Your only choice is Cubic Ninja+Gateway

Gateway Mode = CFW

lol

 

[X_Frost]

If I had a copy of OoTJ with an exploitable save injected, could updating be done since it doesn't use MSET?

 

[Quantumcat]

Gateway Mode = CFW

lol

"CFW" refers to the free options. RxTools, ReiNand, Cakes, etc.

 

[Tokiopop]

If I had a copy of OoTJ with an exploitable save injected, could updating be done since it doesn't use MSET?

No, it needs to be something that doesn't use firmlaunch I believe, otherwise you'll brick. Basically the only option for 8.1j n3DS is NTR with Cubic Ninja. OoT is possible but no one has done anything to get it running. I asked @cell9 for help with where to start so I could start looking into it, and yellow8's oot3dhax save generator is essentially private since ctrclient-yls8 is private. #3dsdev IRC weren't much help either, and just talked about changing the documentation of oot3dhax so it doesn't mention ctrclient-yls8 anymore They also didn't even seem to be aware there was no public payload for 8.1 n3DS and tried linking me to smea's stuff. I would much rather spend a week learning something new and possibly help with getting a bit of movement with OoT (since I already own it) than fork out £40-60 for a Japanese copy of CN, but I'm honestly not sure where to begin.

@Ronhero and @laramie were originally working on some stuff (MSET to launch pasta I believe?) but I don't think it ever came to fruition, publicly at least.

 

[The Real Jdbye]

I am fully aware the files were removed, and it has not stopped people. It literally does not matter.

The original method never connected your 3DS directly to Nintendo's servers. It changed the 3DS to connect to a non-HTTPS server, so there is literally no issue with authentication problems. Your 3DS only ever communicated with the server on your computer, which made the responses for the 3DS. You can just host the firmware files that the original script grabbed from Nintendo yourself.

That's partially true. It made the 3DS fetch the update list from a different server, but the actual update files themselves were still fetched from Nintendo's servers. I don't think anyone has yet gone through the trouble to mirror the update data in the exact same format to make it possible to update a 8.1 without relying on Nintendo's servers at all.

 

[Quantumcat]

That's partially true. It made the 3DS fetch the update list from a different server, but the actual update files themselves were still fetched from Nintendo's servers. I don't think anyone has yet gone through the trouble to mirror the update data in the exact same format to make it possible to update a 8.1 without relying on Nintendo's servers at all.

Given he hasn't done it himself with the files removed from Nintendo's servers, I'd say Tokio is making an assumption from stuff he has read and doesn't fully know how it works.

Tokio if you want to make claims that everyone else doesn't agree with, you really need to make a proof of concept video.