Hacking Suggestion AMS iPatched units deja vu

[NBlack]

standard hbl, but deja vu shouldn't take long to be implemented

incorrect. nvhax was only very recently implemented in a usable form, and is only currently usable on 4.x (and maybe 3.0.x(?))

As cat said, not yet but shouldn't take long.

 

[fingolin]

What is the next step for full dejavu and cfw, i'm on 4.0.1 but think to wait till the whole chain, not on close term with programing and will need to educate myself, as i understand python 2.7 install is necessary to setup pegaswitch.

 

[NBlack]

What is the next step for full dejavu and cfw, i'm on 4.0.1 but think to wait till the whole chain, not on close term with programing and will need to educate myself, as i understand python 2.7 install is necessary to setup pegaswitch.

Completely necessary.

Next step will be implement nvhax+dejavu+pegaswitch as i understood.
pegaswitch (launcher) => nvhax+dejavu payload => homebrew+others adaptation

Please, if im wrong correct me

 

[x124]

I'd wait a week or two even after full deja vu release. ipatched systems are very fragile and one mistake can brick the system for good with no way of recovering.
Also perhaps if one has the patience, waiting for next hekate and atmosphere release with more emunand bugfixes and stability wouldn't be a bad idea either.

Anyway, I'm very excited that deja vu is finally dropping. been waiting for months!

 

[pcwizard7]

as far i can tell atm PegaSwitch can only load the homebreew loader not cfw, correct?

 

[Galactiiix]

as far i can tell atm PegaSwitch can only load the homebreew loader not cfw, correct?

Yes, just the homebrew

 

[NBlack]

I'd wait a week or two even after full deja vu release. ipatched systems are very fragile and one mistake can brick the system for good with no way of recovering.
Also perhaps if one has the patience, waiting for next hekate and atmosphere release with more emunand bugfixes and stability wouldn't be a bad idea either.

Anyway, I'm very excited that deja vu is finally dropping. been waiting for months!

Its a good idea, we dont have Recovery tools as non-patched switch so please be patient, if we was waiting for a 'long' time, a few weeks more is not time.

 

[ZachyCatGames]

I'd wait a week or two even after full deja vu release. ipatched systems are very fragile and one mistake can brick the system for good with no way of recovering.
Also perhaps if one has the patience, waiting for next hekate and atmosphere release with more emunand bugfixes and stability wouldn't be a bad idea either.

Anyway, I'm very excited that deja vu is finally dropping. been waiting for months!

Atmosphere and hekate already both have protections to prevent bricks on FG patched systems

 

[Eukelade]

Caffeine for Switch Units with 4.0.1 and 4.1.0 is out.

Thanks to the AtlasNX Team .

Source:
https://github.com/AtlasNX/caffeine

 

[NBlack]

Great! Warmboot ready, next step CFW

 

[Galactiiix]

I am impatient ! Thank you

 

[NBlack]

I am impatient ! Thank you

Who will be the first? make your bets!

 

[bajul]

how to fix?

 

[NBlack]

how to fix?

Use sudo.

If you installed with sudo npm install, user owner its nobody. Remove all and try npm install without sudo again to run without sudo node start.js
better option:
IN YOUR FOLDER WITH node_modules!!!! (not root please!)
sudo chwon yourser:yourgroup *

Edit:
Ok, i see you are using root user. Maybe better option (windows) run your console with administrator privileges.

 

[Eukelade]

You can find some additional Information here: https://pegascape.sdsetup.com/

Please wait patiently for some tutorials, if you don't know what you are actually doing.

 

[proffk]

According to github this allows cfw to launch with pegaswitch on 4.1.0 fw. All this is good progress to maybe getting all ipatched units open.

Seems you have to launch this with a Fork of pegaswitch if your on 4.1.0.
The instructions on running that fork seem complex.

 

[Eukelade]

According to github this allows cfw to launch with pegaswitch on 4.1.0 fw. All this is good progress to maybe getting all ipatched units open.

Seems you have to launch this with a Fork of pegaswitch if your on 4.1.0.
The instructions on running that fork seem complex.

Yeah, keep in mind that the pegaswitch fork of the Reswitched Team is not up-to-date.
Use this fork instead: https://github.com/noahc3/pegaswitch

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

AtlasNX posted some information on Twitter:

https://twitter.com/AtlasNX/status/1143489005687902209

 

[proffk]

Removed (double post)

 

[proffk]

Heres a youtube vid I found showing it in action on 4.1.0

 

[AceX]

https://pegascape.sdsetup.com/]
For your safety, you should avoid using the following homebrews on IPATCHED systems:

• memloader
• ChoiDujour
• ChoiDujourNX (safe on emuMMC, do not use on sysnand)
• Anything involving AutoRCM (briccmii, SX OS payload, etc)
  • Many homebrews have been updated to block enabling AutoRCM on IPATCHED units including Hekate and ChoiDujourNX. Still exercise very high caution.
• Anything which writes to sysNAND without proper security or verification in place

Does that mean TX can't use it?

 

[x124]

https://pegascape.sdsetup.com/]
For your safety, you should avoid using the following homebrews on IPATCHED systems:

• memloader
• ChoiDujour
• ChoiDujourNX (safe on emuMMC, do not use on sysnand)
• Anything involving AutoRCM (briccmii, SX OS payload, etc)
  • Many homebrews have been updated to block enabling AutoRCM on IPATCHED units including Hekate and ChoiDujourNX. Still exercise very high caution.
• Anything which writes to sysNAND without proper security or verification in place

Does that mean TX can't use it?

They can. they just need to update their software to not automatically enable autorcm for ipatched users, thus breaking their switch.

Now here is my real question:

Upon using PegaScape to reboot into a payload on an IPATCHED Switch, you should immediately create a NAND backup with Hekate and dump all of your keys (especially BIS keys) with Lockpick_RCM. Understand that by not dumping these, there is no recovery method for your Switch should anything cause it to fail to boot.

Does this mean with nand backup and keys, we stand a chance at unbricking our switch? By opening the device and putting the nand into a programmer to reprogram it with backup perhaps? I don't think there is another way

Also bonus question: Can those bricker codes floating around, brick the console on emummc? or will they just corrupt the emummc in the worst scenario?