What is the ultimate point of keeping the cardreader from updating to work on higher firmwares?
I understand it's to allow it to work in older firmwares, but what for exactly?
The point of going back to older firmware is to make use of a potential coldboot exploit to jump right into cfw without all the hassle of payload injection.
But at the end of the coldboot, we'd still wanna be in a latest firmware setting (i.e. through emunand?) for compability and future additions to horizon anyways, right? at which point we'd need the updated cardreader anyways, right?
Or is there something I'm not seeing here.
Just in case there is something I'm missing, I did use the new sd files website to get reinx with the nogc patch (it seems to be in the ReiNX folder). If I only use reinx.bin to jump into cfw (and not hecate), is there anything else I need to look out for?
Finally, when the time comes to downgrade back again, do I just use the corresponging 'update' files for 3.0.2 or would I need my nand backup for that to work?
I understand it's to allow it to work in older firmwares, but what for exactly?
The point of going back to older firmware is to make use of a potential coldboot exploit to jump right into cfw without all the hassle of payload injection.
But at the end of the coldboot, we'd still wanna be in a latest firmware setting (i.e. through emunand?) for compability and future additions to horizon anyways, right? at which point we'd need the updated cardreader anyways, right?
Or is there something I'm not seeing here.
Just in case there is something I'm missing, I did use the new sd files website to get reinx with the nogc patch (it seems to be in the ReiNX folder). If I only use reinx.bin to jump into cfw (and not hecate), is there anything else I need to look out for?
Finally, when the time comes to downgrade back again, do I just use the corresponging 'update' files for 3.0.2 or would I need my nand backup for that to work?