Hacking Suggestion AMS iPatched units deja vu

[kumikochan]

Just wait a couple of months, i'll give it +- 6 months

 

[Zaybokk]

Deja vu is an entry point for homebrew.
Not a cfw.
You can only run some homebrew made for it...
And you can never use it to launch cfw.

just tried the Amiibo Emulation - (emuiibo) , but it keeps crashing on me
no idea why?, am i'm missing something here?... i have atmosphere 0.8.7 master - 6.2.0 firmware , i copied over
files that was included in the zip on this page :

note: worked fine with this one alone-(1st time loaded, then after keeps crashing? hmm)
#1: https://github.com/XorTroll/emuiibo

note: after putting the *.nro* file in *switch* folder now keeps crashing.
#2: https://github.com/FuryBaguette/AmiiSwap

note: not sure if there needed with one another to even use emuiibo properly?..

 

[annson24]

With regards to a release of implementation -- I no longer actually have the source code for my original Deja Vu demos due to a hard drive dying last summer. However, <= 4.1.0 should be able to use it pretty readily soon thanks to nspwn allowing mmio access. Give it a few days.

— Michael (@SciresM) April 16, 2019

<= 7.0.1 will probably be able to use Deja Vu at some point in the future, since we theoretically have the pieces necessary to do the privilege escalation it needs. Do not update past 7.0.1, if you want a software hack for the Nintendo Switch.

— Michael (@SciresM) April 16, 2019

 

[x124]

Deja vu is an entry point for homebrew.
Not a cfw.
You can only run some homebrew made for it...
And you can never use it to launch cfw.

According to https://switchbrew.org/wiki/Switch_System_Flaws
Deja vu gives access to BPMP code execution. same as Fusée Gelée. It should be possible to boot into an emunand system from there

 

[The Real Jdbye]

Now with ofw8 broke the dejavu exploit which gone public what are the option for us with the patched units. Have not see much info so decided a separate topic where to post any info would be useful. For begining where can be found the released exploit chain so to follows the future updates.
Up to ofw3 it can be used as it but patched units begins with ofw4. On 4.x is needed just a little tweak and for 5.x-7.x more than a little. Using the dejavu method will definitely requires an emunand setup which is in progress.
Does that summarize it well, any early guidelines for cfw preparations are wellcome

Simple. Don't update.
EmuNAND will be a godsend though.

 

[hippy dave]

Will emunand and sysnad be usable, combined both are around 50gb, read somewhere about shrinking emunand. And because dejavu is launched via website what will happens if the website is down, can it be somehow saved on the console, is it good if using most of the time sleep mode instead turn off. Another thing i'm unsure when launch cfw via dejavu does it completely restart the console or just boot into cfw, for rcm in comparison it boot in rcm then in cfw don't know if reboot. Maybe is good when released AMS for ipatched units to include option fo completely disabling the autormc to prevent accidentally turn it on as there is allways a risk.
edit: and using this before anything else to avoid update? https://gbatemp.net/threads/90dns-dns-server-for-blocking-all-nintendo-servers.516234/

Yes emunand and sysnand will both be useable (once emunand is released). Sysnand will still live on your built-in storage, so you don't need to worry about the size/space for that. Emunand will take up space on your SD card, but most of the space it takes up can be used to install games (equivalent to installing games to your internal storage). Shrinking emunand should be possible, but might not be considered high priority as the space can be used for games.
You might not be able to cache the deja vu webpage, hexkyz said caching wouldn't work on newer firmwares, don't know how new. You'll be able to host it on your local network, for when the internet or some public exploit site is down. Yes sleep mode is good. Yes 90dns is good for avoiding updates, but also tell anyone who uses your console not to click an update notification on pain of death.

When rcm exploit was discovered, all entire scene became depending on it and no one cared about finding new entry points.
This obsession about rcm was so huge, that ipatched units were born with the stigma of an obsolete and less featured product. just like the wii mini. I don't think it will ever be cfw running on them, seriously. imo new gen consoles will be available first..

Deja vu is an entry point for homebrew.
Not a cfw.
You can only run some homebrew made for it...
And you can never use it to launch cfw.

So yeah deja vu was always planned to be used on patched units. Deja vu will be used to reboot into cfw.

i have two units, one is a *Non-patched unit* and Other one is a *yellow-patched unit*.. my question is:
i have the patched unit on firmware 6.2.0 and haven't updated since can i run CFW on it?..
or is deja vu even Considered CFW?.. little confused sorry for the questions..

Yes you will be able to, once deja vu is released and updated for 6.2, which will take a while but not forever.
Deja vu is an exploit chain that will be used to run cfw, so yes you'll have cfw.

 

[x124]

So I've heard a thing about updated cart readers and downgrading/keeping sysnand on low firmware
What is it about and how does it affect patched units? I've seen mentions of disabling the cart reader in emunand as a workaround
Does this mean we won't be able to use carts on emunand with high firmware versions in order to keep exploit avenue open?
Or does it just mean we won't be able to use carts on the ofw with low firmware version after we update it?
I don't particularly care about where I'm playing my games, but I very much like to keep my carts

 

[hippy dave]

So I've heard a thing about updated cart readers and downgrading/keeping sysnand on low firmware
What is it about and how does it affect patched units? I've seen mentions of disabling the cart reader in emunand as a workaround
Does this mean we won't be able to use carts on emunand with high firmware versions in order to keep exploit avenue open?
Or does it just mean we won't be able to use carts on the ofw with low firmware version after we update it?
I don't particularly care about where I'm playing my games, but I very much like to keep my carts

The card reader firmware has one version for system firmware versions below 4.0, and another version for 4.0 and above. If your system firmware is already 4.0 or above, then just don't worry, you're not affected.*

If your system firmware is less than 4.0, and you're planning to keep it there and use updated emunand, then you have a choice. You can keep cart games working in sysnand, by using nogc patches to disable the cart slot in emunand, or you can not use nogc patches so your cart slot is updated by emunand, which means you can play carts in emunand, but not in sysnand.

Using nogc patches would be the safest option by default, to keep things how they are as it's currently not possible to go back. Once you've got the exploit all set up and running sysnand and emunand how you want it tho, you might find you want to play newer cart games that don't work on your old sysnand, so maybe you'll want to update the card reader firmware. See how it plays out and make your own decision at the time.


*e: I've just re-read your post and noticed you said "patched units". You'll definitely have firmware 4.1.0 or above, so you can forget about this entirely. Leaving the rest for anyone else it might help.

 

[x124]

The card reader firmware has one version for system firmware versions below 4.0, and another version for 4.0 and above. If your system firmware is already 4.0 or above, then just don't worry, you're not affected.*

If your system firmware is less than 4.0, and you're planning to keep it there and use updated emunand, then you have a choice. You can keep cart games working in sysnand, by using nogc patches to disable the cart slot in emunand, or you can not use nogc patches so your cart slot is updated by emunand, which means you can play carts in emunand, but not in sysnand.

Using nogc patches would be the safest option by default, to keep things how they are as it's currently not possible to go back. Once you've got the exploit all set up and running sysnand and emunand how you want it tho, you might find you want to play newer cart games that don't work on your old sysnand, so maybe you'll want to update the card reader firmware. See how it plays out and make your own decision at the time.


*e: I've just re-read your post and noticed you said "patched units". You'll definitely have firmware 4.1.0 or above, so you can forget about this entirely. Leaving the rest for anyone else it might help.

Thanks for the explanation. Since there is no reason to stay in ofw except to launch cfw, I guess cartridge is not needed there anyway as everyone with patched switch will be playing everything in emunand

I'm hoping this thread can serve as a central for those of us with hacked switches to discuss cfw. The whole homebrew community is too used reliant on rcm bug that patched switches feel cast aside.
Any guesstimates about release time? I'm guessing development priority is 8.0.0 support (already seems done) -> emunand -> deja vu.
Let's hope it's not too long now

 

[hippy dave]

Any guesstimates about release time? I'm guessing development priority is 8.0.0 support (already seems done) -> emunand -> deja vu.
Let's hope it's not too long now

8.0 support later today (source: SciresM). Couple of people have said emunand is coming in the next couple of days, I personally haven't seen it said by the devs working on it but I guess someone must have. My rough estimate for deja vu is a sliding scale of within a week for the lowest firmware versions, to months away for 7.x

 

[BakaBehindKeyboard]

The whole homebrew community is too used reliant on rcm bug that patched switches feel cast aside.

But is that really any surprise? Even with deja vu, unpatched units will still be the superior and safer option. Once ipatched units were discovered in the wild, there was still a rediculous amount of time to get unpatched systems. If you missed out on that it's a bummer for sure but doesn't susprise me one bit that patched systems are lowest on the totem pole. There's still so much to be done with unpatched systems first and that takes time.

 

[Hiipswerf]

Wait I'm confused about the whole EmuNAND and Deja Vu thing
So sys nand will be on the latest firmware to play online and EmuNAND will be there to play hacked games
If that's correct then how would you be able to use DJV if sys nand is on the latest fw which it is patched on?
Am I missing something here?

 

[hippy dave]

Wait I'm confused about the whole EmuNAND and Deja Vu thing
So sys nand will be on the latest firmware to play online and EmuNAND will be there to play hacked games
If that's correct then how would you be able to use DJV if sys nand is on the latest fw which it is patched on?
Am I missing something here?

The setup for deja vu would be lower firmware sysnand, to run the hack, and updated emunand, to play games. Whether it's safe enough to take emunand online is going to be a matter of opinion and probably change over time.

Updated clean sysnand for online and dirty emunand for hax is a different setup that would be useable with fg/rcm boot, but not on patched switches.

 

[x124]

But is that really any surprise? Even with deja vu, unpatched units will still be the superior and safer option. Once ipatched units were discovered in the wild, there was still a rediculous amount of time to get unpatched systems. If you missed out on that it's a bummer for sure but doesn't susprise me one bit that patched systems are lowest on the totem pole. There's still so much to be done with unpatched systems first and that takes time.

It's not a surprise and I'm not complaining. but it doesn't hurt anyone if we had a place to exclusively talk about patched switches. Homebrew development for switch can continue in parallel with ipatched and unpatched switches. the only difference is payload delivery (which in my opinion deja vu is superior if you don't care about online, but everyone has their own needs). I bought my switch knowing full well what I was getting into and don't regret it now.
While patched switches are the minority now, things will be different in a year or two especially when new hardware revisions come out. Also consider the count of unpatched switches are shrinking as they get broken/banned. Wouldn't you rather have the option to buy a brand new switch any time you wanted and be able to hack it instead of hunting ebay and yard sale for a second hand hackable model or keeping a second console in a box just in case?

 

[BakaBehindKeyboard]

It's not a surprise and I'm not complaining. but it doesn't hurt anyone if we had a place to exclusively talk about patched switches. Homebrew development for switch can continue in parallel with ipatched and unpatched switches. the only difference is payload delivery (which in my opinion deja vu is superior if you don't care about online, but everyone has their own needs). I bought my switch knowing full well what I was getting into and don't regret it now.
While patched switches are the minority now, things will be different in a year or two especially when new hardware revisions come out. Also consider the count of unpatched switches are shrinking as they get broken/banned. Wouldn't you rather have the option to buy a brand new switch any time you wanted and be able to hack it instead of hunting ebay and yard sale for a second hand hackable model or keeping a second console in a box just in case?

Yeah, I didn't mean any offense. I'm glad ipatched units are getting a way to use CFW. The option being out there for more people is great. I was just saying that it isn't surprising that the community isn't making those systems the main priority. Though I really don't see any way that deja vu is a superior option to load payloads versus the current method. From what I've seen/heard it's slower and involves more steps. Plus it's way more dangerous since you have no emergency way to load payloads if something goes wrong with your sysnand. Unfortunately I foresee many people bricking their systems with autoRCM or whatever else and having no option other than hardmods to save them. Honestly the only people I see using deja vu are those who're forced to because they have a patched system. If I'm mistaken with that feel free to let me know. Not here to really argue though. Looking forward to see what happens in the future for sure.

 

[x124]

Yeah, I didn't mean any offense. I'm glad ipatched units are getting a way to use CFW. The option being out there for more people is great. I was just saying that it isn't surprising that the community isn't making those systems the main priority. Though I really don't see any way that deja vu is a superior option to load payloads versus the current method. From what I've seen/heard it's slower and involves more steps. Plus it's way more dangerous since you have no emergency way to load payloads if something goes wrong with your sysnand. Unfortunately I foresee many people bricking their systems with autoRCM or whatever else and having no option other than hardmods to save them. Honestly the only people I see using deja vu are those who're forced to because they have a patched system. If I'm mistaken with that feel free to let me know. Not here to really argue though. Looking forward to see what happens in the future for sure.

No offense taken at all. Sorry if it seemed like that.
I too am happy that the wait is almost over. thankfully most tools like atmosphere are getting patches to resist autorcm in patched switches to avoid such mistakes. but you are 100% correct that unlike the rcm method, a small mistake can completely brick the system without a way to load a payload in order to fix it.
regarding the payload launch, as far as I can tell it's as simple as setting up a special dns similar to 90dns that tricks switch into opening the browser (captive portal) and sending the payload. No need for a jig/autorcm and no need for an external dongle. it is indeed more difficult to implement for developers though

 

[Dysproh]

Deja vu is an entry point for homebrew.
Not a cfw.
You can only run some homebrew made for it...
And you can never use it to launch cfw.

This is just not true. Deja Vu is a trustzone exploit that will enable running CFW, though it requires an entrypoint.

 

[P3T3]

This is just not true. Deja Vu is a trustzone exploit that will enable running CFW, though it requires an entrypoint.

Correct will be the entry point for cfw, like reboot to payload, cfw, emunand... How ever they implement it, looking forward to dusting off my ipatched unit!

 

[fingolin]

Besides the website push have no idea about the setup, is it automatic or does requires some other actions and how long approximately takes to boot it.

 

[fingolin]

Any news on dejavu solution?