Hacking [IDEA]Proxy / Own SOAP Server for Updates (for the Downgrade-Process)

[theross]

Hi Folks,
I keep on asking myself why nobody talked about the possibility of doing some DNS-stuff in order to redirect the 3ds-Update through an own Proxy or SOAP-Server in order to "send" always the 10.3 files instead of the new ones. Like that people could have several tries to downgrade their console.
Has anyone tried something similar?

 

[Apache Thunder]

I think that was already done for 8.1 Japanese consoles. I don't recall where the thread was on it. Sounds like a pain to do though. Better ways of downgrading may crop up in the future though. I'd say be patient and see.

 

[daxtsu]

I think that's a bit of a stretch in this case, because to recover from failed downgrades, you have to use recovery mode, which puts the system into a different mode altogether, so you'd be out of CFW/unable to run things like NTR, which you'd need in order to patch the URLs that the upgrade function uses.

 

[Melon__Bread]

I think that was already done for 8.1 Japanese consoles. I don't recall where the thread was on it. Sounds like a pain to do though. Better ways of downgrading may crop up in the future though. I'd say be patient and see.

Yeah I was one who went from 8.1J to 9.2J (sysnand) using that method and it was pain (but had no other choice if I wanted to use my gateway at the time).

IMO you are just better off trying something like sysupdated through HBL (if I recall the .3dsx version would work)

 

[Tjessx]

I've been looking into something similar, but i believe that the url's to the update server are https, so this would be very difficult, possibly not even possible

 

[theross]

I think that's a bit of a stretch in this case, because to recover from failed downgrades, you have to use recovery mode, which puts the system into a different mode altogether, so you'd be out of CFW/unable to run things like NTR, which you'd need in order to patch the URLs that the upgrade function uses.

If you read my first post again, you'll read the word DNS
I'm talking about redirecting the requests to your own SOAP-Server. You only need to make the proper DNS Redirection.

I've been looking into something similar, but i believe that the url's to the update server are https, so this would be very difficult, possibly not even possible

If you redirect the Request to your own server with an invalid certificate, what would the 3DS do? reject the connection and run into an error or simply go on with an untrusted certificate chain? (I BET Untrusted as in china for example they're modifying the CERT-Chain all the time in order to spy the citizens.

 

[Deleted-19228]

It uses TLS it should not work at all...

 

[Tjessx]

If you read my first post again, you'll read the word DNS
I'm talking about redirecting the requests to your own SOAP-Server. You only need to make the proper DNS Redirection.



If you redirect the Request to your own server with an invalid certificate, what would the 3DS do? reject the connection and run into an error or simply go on with an untrusted certificate chain? (I BET Untrusted as in china for example they're modifying the CERT-Chain all the time in order to spy the citizens.

It probably will reject the connection, but the question is: what will it do when it rejects the request.
I think that system update will reject the request.
Other things like browser allowance on lower firmware is possible

 

[Thunder Hawk]

Yeah I was one who went from 8.1J to 9.2J (sysnand) using that method and it was pain (but had no other choice if I wanted to use my gateway at the time).

IMO you are just better off trying something like sysupdated through HBL (if I recall the .3dsx version would work)

That sounds like fun.

 

[UraKn0x]

I think that was already done for 8.1 Japanese consoles. I don't recall where the thread was on it. Sounds like a pain to do though. Better ways of downgrading may crop up in the future though. I'd say be patient and see.

That was yifan_lu who's done that, and if you recall properly, the point where it differs (and that makes it impossible now) is that he directly edited the URLs in the console RAM to a HTTP server with NTR CFW, therefore the 3DS was no longer seeking for a HTTPS connection and made it possible. When you are softbricked there's unfortunately no way of editing the RAM...

--------------------- MERGED ---------------------------

Yeah I was one who went from 8.1J to 9.2J (sysnand) using that method and it was pain (but had no other choice if I wanted to use my gateway at the time).

IMO you are just better off trying something like sysupdated through HBL (if I recall the .3dsx version would work)

The problem that many people are facing is that if the downgrade process fails, the console is softbricked and the only way of getting out of this is by updating the 3DS with safe mode (which directly boots in the system update menu). So once you are softbricked now, you're doomed to the 10.4 hell.

 

[Melon__Bread]

The problem that many people are facing is that if the downgrade process fails, the console is softbricked and the only way of getting out of this is by updating the 3DS with safe mode (which directly boots in the system update menu). So once you are softbricked now, you're doomed to the 10.4 hell.

I was referring to updating, not downgrading. Also isn't there safesysupdater now that prevents people from using the wrong files

 

[UraKn0x]

I was referring to updating, not downgrading. Also isn't there safesysupdater now that prevents people from using the wrong files

Hi Folks,
I keep on asking myself why nobody talked about the possibility of doing some DNS-stuff in order to redirect the 3ds-Update through an own Proxy or SOAP-Server in order to "send" always the 10.3 files instead of the new ones. Like that people could have several tries to downgrade their console.
Has anyone tried something similar?

OP was clearly talking about the downgrade process. In any case it's now impossible to have a second try at downgrading, the only outcomes are first-try 9.2 or 10.4.

 

[Melon__Bread]

OP was clearly talking about the downgrade process. In any case it's now impossible to have a second try at downgrading, the only outcomes are first-try 9.2 or 10.4.

Great and I was responding to ApacheThunder about the old thread he was referring to

 

[UraKn0x]

Great and I was responding to ApacheThunder about the old thread he was referring to

And ApacheThunder was replying to OP, so anyways that was kinda off topic for you to say that. That being said, I'm not looking for an argument here so it'd be better to leave it there.

 

[Roboman]

OP was clearly talking about the downgrade process. In any case it's now impossible to have a second try at downgrading, the only outcomes are first-try 9.2 or 10.4.

You can still hard mod a 10.3 3ds get a nand backup and reflash in case of failure

 

[MelonGx]

For N3DS 9.0-9.2 and all exploitable O3DSes, upgrading to 10.3 then downgrading back to 9.2 is stupid - Wasting time & Self-making a brick chance to yourself.

For N3DS 8.1, upgrading to 9.1 is completely better than 8.1-10.3-9.2.

For 9.3-10.3, there are NO METHOD to boot anything like NTR Debugger to change your 3DS client to access private server.

For O3DS 7.0.0-0J to 8.1.0-1J, there are NO METHOD to boot anything like NTR Debugger either. But you still can use Carts to upgrade to 9.4-10.3 then downgrade.

So this project is currently meaningless.

 

[dubbz82]

You can still hard mod a 10.3 3ds get a nand backup and reflash in case of failure

This. Downgrading even with a supposedly "safe" process still has the possibility of hard bricking a console. Doing otherwise is putting your console at risk. It's abundantly clear to me that there's a bunch of people that have an extra 100+ dollars to burn on a new console if they're not doing this already.