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.
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(?))
Completely necessary.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.
Yes, just the homebrewas far i can tell atm PegaSwitch can only load the homebreew loader not cfw, correct?
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 systemsI'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!
Who will be the first? make your bets!I am impatient ! Thank you
Use sudo.how to fix?
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.
They can. they just need to update their software to not automatically enable autorcm for ipatched users, thus breaking their switch.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?
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 wayUpon 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.