Terms of Service.

PS5 NOR Editor is written and operated by one person, trading as NoRunDev, no company, no team. That is worth knowing before you buy: support is one inbox, answered by the person who wrote the program, and there is no one else to escalate to. Contact is support@norundev.com or, on WhatsApp, +39 334 870 4214.

Using the program, or buying a license for it, means you accept these terms. If you do not accept them, do not buy a license and do not use the program.

A Windows program that reads and edits a 2 MB PS5 NOR dump: identity fields, validation, repair, recovery and the partition-rebuild feature called Regenerate. Four of those, Contribute, Validation, Repair and Regenerate, run on a server this project operates, not on your machine. Without that server the program still opens a dump and runs ten structural checks locally; it does not validate in depth, repair, or regenerate.

It is independent software, not affiliated with or endorsed by Sony Interactive Entertainment. “PlayStation” and “PS5” are trademarks of Sony Interactive Entertainment Inc., used here only to identify the hardware the program works on.

A license key runs for the term you bought, see Pricing, and is checked at every launch, against the licensing service, before the tabs exist. Offline, the last good check keeps the program working for 24 hours; past that the key reads stale and needs to reach that service again. A key that comes back suspended or cancelled closes the program with a message naming that state, and that refusal is written to disk, so it holds even with the network unplugged. A network that is merely unreachable does not close anything, until the 24 hours run out.

The key is bound to one computer. Moving it to another machine is a step this project handles by hand, on request: write to support and it gets moved, no justification needed.

When a license can be suspended or cancelled, and what happens to your money when it is, is set out under Suspension and bans below.

Plans are fixed terms, 3, 6 or 12 months, sold through Ko-fi's shop, in EUR. The license key is sent by email within 48 hours of the purchase, usually within 24; if it has not arrived by then, write to support. A plan does not renew itself: nothing is ever charged without a new order from you, and running past the term means buying another one. Prices and plan lengths can change for future purchases; they do not change the price or the length of a term already bought.

Within 14 days of buying, you can ask for your money back and get all of it, no reason needed, as long as the license has not been activated. Activated means the key has been entered and accepted on a computer at least once. Downloading the program, or receiving the key by email, does not count.

Once a key has been activated, the refund window closes: at that point you have had the thing you bought. Before downloading the program you are asked to confirm, explicitly, three things: that you have read these terms; that you ask for the license to be usable straight away, before the 14-day withdrawal period ends; and that you understand you lose your right of withdrawal once the license is activated. If you are not asked, or do not confirm, the 14 days stay open whether or not the license was activated.

This is separate from a suspension or a ban, which is covered below, and from the legal rights described under No warranty.

Opening a dump sends it. The whole 2 MB image goes to this project's server, the file as it is on disk at that moment, and the server keeps that copy so that Validation, Repair and Regenerate can work on it without the file being sent again. This is how the program works, not an option: they run there, against that copy, not on your machine.

After opening, only your changes travel, including any identity fields you have typed by hand. When they grow too large to send that way, the whole edited file is sent again and becomes the copy the server works on.

Uploads are capped at 20 a day per license and 100 a day across everyone, and the server refuses any upload when it has less than 2 GiB free. Those limits exist to keep one machine from pulling the service apart; if you hit them in ordinary repair work, write to support.

Regenerate answers with a whole rebuilt partition rather than an edit list. nvs is synthesised from patterns derived across many dumps; every other partition is taken from a sanitised reference dump, another console's partition, not yours. Before any response is written into your dump, every field that identifies your console and every volatile log the EMC keeps is put back from your own file first: neither a reference dump nor a synthesised partition gets the last word on those.

Two cautions: unk holds calibration specific to each console, and a reference EMC or USB-PD partition can carry a different firmware build from yours. Choosing which partitions to regenerate is your decision.

Contribute adds a dump to the reference pool. Donating is deliberate: nothing is donated by opening a file, only by using that feature.

A note you attach to a contribution (“did the console work”, a southbridge revision, a comment) is recorded as your claim, not verified against the chip; a southbridge revision the server does not recognise is stored as unknown.

By contributing you allow this project to use the dump to derive the maps and templates the service relies on, some ship with the program, others stay on the server, and, once sanitised, to use it as a reference dump for Regenerate, so that partitions of that console other than its identity can be written into another customer's dump.

The program ships with two EMC firmware images, taken from a publicly available repository, and the Patches & flags tab writes them into both emc_ipl slots of a dump. They are there because southbridge revision swaps need them.

Two things follow that you should know before using that tab. The shipped images are fixed versions, written over whatever was on the board: on a board running newer EMC firmware the swap is a downgrade, and the confirmation dialog says which before anything is written. And the SLB2 truncation floor was lowered to accept them, which slightly weakens that check for every dump the program inspects, not only the ones it writes.

Only use this on hardware you own or are authorised to service. A NOR dump identifies a specific console, serial, board id, SoC id, MAC addresses among them, and sending one is on you to decide, console by console. If the console belongs to a customer, that decision is one you are making on their behalf, and you must tell them before you send it; what that involves is set out in the Privacy policy. Do not use Contribute on a console that is not yours without its owner's explicit agreement.

Recovery and Repair narrow down or reconstruct values from the bits that survive; they do not guarantee the result is correct, and a NOR write can only clear bits, never set one back. Keep the dump you started from. Saving proposes a new file rather than the one you opened, but you can still choose to write over the original, nothing stops you, nothing here backs it up for you, and the working buffer in memory is a different matter from the file on disk.

Abuse gets taken seriously, but not everything is abuse and not everything is treated the same way. Action is taken on verified facts, never on suspicion, and you are always told in writing what was found.

Closed immediately, first time, no warning: tampering with the program, cracks, unofficial patches, bypassing the license check, modified builds; payment fraud, cards that are not yours, a chargeback opened in bad faith after using the program; and illegitimate use, copying one console's identity onto another to evade a ban or make a stolen device look legitimate.

To be clear about the middle one: disputing a charge in good faith is not a violation. No one is banned for opening a dispute, nothing is done while one is open, and nothing is done if it is decided in your favour. If a payment went wrong, write in, it is faster that way.

license sharing, credentials used by more than one person, activation attempts beyond the limit, access passed on, goes through three stages instead. First a warning, saying what was detected and giving you time to fix it. Then, if nothing changes, a suspension of at most 30 days. Then, if it continues, the license is cancelled.

What happens to your money. A suspension pauses your term: days you cannot use the program are not days you paid for, and the expiry moves forward by the same number. A ban for tampering, fraud or illegitimate use forfeits the rest of the term. A ban for license sharing does not, the unused part is refunded. And a ban that turns out to be wrong is reversed with the lost time added back, or refunded in full if you would rather stop there.

If you think it is a mistake, write to support@norundev.com or on WhatsApp to +39 334 870 4214 and say so. You get an answer within 7 days, and if you are right it costs you nothing. It is worth writing in: the anti-abuse side of this sees computers and activations, not intentions, and it can be wrong. A replaced motherboard, a reinstalled PC, a bench machine swapped out, each of those can look like sharing without being it.

A configuration value can stop every installed copy of a given version from starting, before the license check, without notice, for a security hole, a defect that damages dumps, or any other reason this project judges sufficient. You are pointed at a build to move to.

If a copy you paid for is stopped and you cannot or do not want to move to the build you are pointed at, the rest of your term is refunded.

If this project shuts the service down, or stops trading, then within 30 days a final build is published with no license check and no version stop: free, no expiry, working offline, for good. You do not lose access to a program you paid for because the person selling it stopped.

That build is the whole program, not a cut-down one: the features that run on this project's server today, Validation, Repair and Regenerate included, come with it and run on your own machine.

Provided as is, without warranty of any kind, express or implied, including for a specific purpose or for a successful repair. Editing identity and firmware data on a games console carries a real risk of an unbootable board; this project is not liable for that outcome, for data loss, or for any damage arising from use of the program or its server-side features, to the extent the law where you are lets that liability be limited.

That limit is not unlimited. If you bought as a consumer, the law where you live gives you rights this page cannot take away, among them, having the program put right, or your money back, if it does not do what this page says it does. Write to support and it gets dealt with.

This page can be updated as the program changes, a new server-side feature, a new data flow, a changed limit, and the effective date at the top moves when it does. Earlier versions are kept and can be requested from support.

If a change materially affects what you bought, you will be told by email, at least 15 days in advance, at the address you bought with, and the change applies from the effective date to every license, including a term already paid for. If a change is one you cannot accept, write to support before it takes effect and the license is cancelled from your side, with the unused part of the term refunded.

Questions about these terms, a license, a refund or a ban go to the same place everything else on this site does: support@norundev.com, or on WhatsApp at +39 334 870 4214.