Just confirming bgtoolset operates only in RAM if I only intend to DUMP the NOR/NAND of a machine?
Seems a strange one, but I have been keeping backups of all my consoles' per console data such as EID root keys (if possible) and EEPROM data, and also the NOR flash which contains per console keys (if the NOR chip fails or a fluke damages the data on them, I could go to this backup and restore it via a flasher). I keep them for all my consoles. This has been trivial with my jailbroken systems, but not for OFW ones. My setup is two jailbroken and two legit consoles for online play that I will keep legit until the store goes then jailbreak. One of the group has his own legit console. We often LAN at home, but sometimes do opportunistic online play.
To save me messing around with a flasher, I had wanted to load bgtoolset and just dump the NOR of my non jailbroken super slim and slim. Have no intention of jailbreaking these just yet as I connect to PSN (and all my bought content for PS3/PS4 over the years is on the same account). The jailbroken ones are simply for DRM-Free preservation of content I bought legitimately that my group play a lot (I created custom pkg install disks of all my games and DLCs I have bought over the years. It is a pop in the disc, install the game/DLCs and license fixes and its ready to go). When the store/online goes, the legit consoles will eventually get qCFW.
I was wondering if bgtoolset operates 100% in RAM assuming you clear the browser history until you patch the NAND/NOR? That would mean I can safely dump and check syscon data of my legit machines.
Keeping a NOR and EEPROM backup is a great idea is if the NOR ever corrupts for any reason or due to time, the system is not a brick if the per-console keys are lost. We play them a lot in our group hence the desire for preservation.