DBIPatcher for traslate v810 russian version

[wurstpistole]

Edited: Transcription of conversation betwen Morce3232 and duckbill:
Morce3232: Will you mind if the translation is added as an nro patch?

duckbill: If you want to add it as a patch – go ahead, but warn users that there may be surprises.
486 – the last one without checks
Nothing destructive will happen. It will just start forgetting to do what was asked, and the further it goes, the more often it will happen.

baffling how one guy can be so bitter about his app being translated into a western language that he would go through all the effort to render it useless or deliberately cause errors in case someone translates it

 

[Morce3232]

baffling how one guy can be so bitter about his app being translated into a western language that he would go through all the effort to render it useless in case someone translates it

I wouldn't delve into that discussion. He surely has his reasons to not want the english version released.

As for potential counter measures, while I can not rule them out, it seems rather convoluted to implement such protection scheme he describes, when proper string encryption would suffice and be likely definitive solution.

Also I would like to note, that apps and games get translated all the time, without any approval, into russian even.

 

[Deleted member 702243]

Yes.

so then how come you can make it forget about the newest version of games by just formatting? if it's embedded in the firmware that each firmware version knows the latest game update versions up to that point then surely it would always nag about it without first needing to connect to the internet to be told about updates?

 

[masagrator]

so then how come you can make it forget about the newest version of games by just formatting?

Can't say about how this works exactly, but there are 2 lists - version list and required version list. They are stored in separate system saves. What causes nag is the required version list which stores only info about games you inserted/downloaded at least once.

it's possible that formatting wipes system saves related to them - either the one storing required version list or both of them. You can find out by trying to use VersionDumper homebrew after formatting offline. If it will return error or no entries at all, it means that it wiped system save for both.

 

[Deleted member 702243]

Can't say about how this works exactly, but there are 2 lists - version list and required version list. They are stored in separate system saves. What causes nag is the required version list which stores only info about games you inserted/downloaded at least once.

it's possible that formatting wipes system saves related to them - either the one storing required version list or both of them. You can find out by trying to use VersionDumper homebrew after formatting offline. If it will return error or no entries at all, it means that it wiped system save for both.

from my personal testing on older firmware versions at the time, the version list stores the available game updates versions and will nag when starting a game with an available update, but it will give you the option to ignore the update and just play the game anyway. required version list updates after you've installed a game update to store information about the latest installed updates, and will nag if you uninstall an update or downgrade to an older update version (when using physical copies on ofw, but it works with digital copies too if you uninstall updates with cfw.) this removes the option to start the game without updating from the nag, basically the same popup just one button is removed

version list updates when online with nintendo, I dont know if it instantly does it as soon as you connect online or if you need to access the eshop first, or if it's a periodic check, etc. required version list updates when an update is installed. it's possible that newer firmware versions actually have a default version list that can never be changed, but I've never seen a popup saying there is a game update available on an offline console, and I have one game I specifically keep on an older update from 2021 so I should have seen this by now. it's possible the data is embedded in the firmware but the update nag is only activated when going online, to prevent freshly formatted consoles in the future from being asked to update when internet connection might never actually be available anymore, but that wouldnt make sense because it needs to download the info about available game updates from the server anyway, for anything released after the firmware version was released

dbi and other apps years ago that claimed to reset this and remove the nag only ever actually reset the required version list to allow running games after downgrading updates, but it never got rid of the nag because available version list wasnt touched. these days duckbill fixed it and both version list and required version list get reset when you reset required version in the app, so the nag is removed correctly. I don't know what the other homebrew do and if they fixed it. I know it never actually worked in goldleaf back then

what I used to do back in the days is that I wiped once, then I backed up the system saves for both version lists. when I needed to reset update versions I would just mount system partition and replace the version lists with the saves I had backed up from before

 

[mspy]

DLCs don't have separate updates, they are just one file with with different version numbers. That function I am using only tracks separate update files which are available only for base games.

Actually there are very few exceptions to this, generally once installed your DLCs get updated along with normal game updates but in rare cases nintendo actually releases a updated version of the DLC itself which I think is cumulative so you won't need to have the original version installed and can go straight to the last one, maybe technically you can say it's not a update because it's a standalone file that works out of the box.

so then how come you can make it forget about the newest version of games by just formatting? if it's embedded in the firmware that each firmware version knows the latest game update versions up to that point then surely it would always nag about it without first needing to connect to the internet to be told about updates?

Can't say about how this works exactly, but there are 2 lists - version list and required version list. They are stored in separate system saves. What causes nag is the required version list which stores only info about games you inserted/downloaded at least once.

it's possible that formatting wipes system saves related to them - either the one storing required version list or both of them. You can find out by trying to use VersionDumper homebrew after formatting offline. If it will return error or no entries at all, it means that it wiped system save for both.

Maybe when you install a game for the first time it only checks the required version list which I assume would be the minimum version the game needs to run on the current system firmware and when you update the game it uses the version list and ticks the version that the update has even if it is not the latest that is listed there.
Then the only way to run the game on a lower update would be to use a app like DBI to reset the tick?
Point is the nag would only match the most recent update that the user has ever installed for a game and not the latest present on the offline version list.
Perhaps only when you go online it validates the version list forcing the nag to a newer update.

 

[The Real Jdbye]

Why wouldn't it be safe?

The rumor is that there might be brick code in dbi, because of something the dev said.
Seems that it was a joke but people are still wary.

 

[duckbill007]

Don't you need to direct DBI to use a known database such as titleDB first?
Or does it also grab the info on its own from official sources and refreshes it automatically when online?

For update check it needs version.txt on some url or locally. Also, it can dump to version.txt info from fw update or received by hos from tagaya server.

 

[Deleted member 702243]

Actually there are very few exceptions to this, generally once installed your DLCs get updated along with normal game updates but in rare cases nintendo actually releases a updated version of the DLC itself which I think is cumulative so you won't need to have the original version installed and can go straight to the last one, maybe technically you can say it's not a update because it's a standalone file that works out of the box.

yes that's what masagrator meant. for games the Base is (almost?) never updated, instead there is a separate Update. but dlcs dont have separate files for the update, instead the dlc file is updated directly

even physical copies that have updates bundled work that way, the cartridge includes the Base (usually v0 but not always), the eshop ncas for the update, plus a ticket and a certificate for the update. the ticket is installed to nand when the cartridge is run, but the console runs the digital update files off the game card instead of installing them to the console. the distinction matters because physical and digital ncas are different, ncas for cartridges have distribution bit set to 1 for game card contents, but the updates bundled inside updated game cards are the same as the eshop downloads, and distribution bit is set to 0 to tell the console this is digital contents

this is at least interesting because the system doesn't let you run gamecard ncas installed as digital contents without either patching the distribution bit check, or modifying the ncas to change the distribution bit from 1 to 0. but this shows that digital ncas will run from gamecard just fine, or at least it specifically allows updates to run from gamecard. in practice it doesnt matter for us because it's not like we would have a way to put eshop files on game cards to run them anyway, but it's interesting to know how the os works

things have changed a lot over time though with firmware updates, so the details might not be 100% accurate to fw 20. but anyway. what matters is that even game cards dont update the Base, and instead a separate Update is bundled, while dlcs dont have separate updates because they get directly replaced with higher versions

Maybe when you install a game for the first time it only checks the required version list which I assume would be the minimum version the game needs to run on the current system firmware and when you update the game it uses the version list and ticks the version that the update has even if it is not the latest that is listed there.
Then the only way to run the game on a lower update would be to use a app like DBI to reset the tick?
Point is the nag would only match the most recent update that the user has ever installed for a game and not the latest present on the offline version list.
Perhaps only when you go online it validates the version list forcing the nag to a newer update.

no, the console doesnt check any kind of required firmware version when installing. it only checks when trying to run the game, and this checks the minimum required firmware version in the cnmt. more specifically, when installing, the required firmware version is taken from the cnmt and saved to a cache on nand (in system save data 8000000000000121), and the system checks against this when running a game, instead of checking the actual installed cnmt. you can install a game that has a required system version higher than what you have installed and it will install fine, but it will check that required version in the cache on nand and see that your firmware version is too low, and demand that you update before you are able to run the game

this behavior is useful for us because this cnmt cache isn't really validated in any way. it's not signed and there are no other checks to prevent arbitrary values from working (it never re-checks the real cnmt after installing). so installers for nsp and xci can just spoof it and make it write 0 to the cache, instead of the actual required system version, and then it checks and sees your firmware version is higher than 0 and it will never complain that you need to update the firmware to run a game. and because it goes by cache, this works without modifying the game files, meaning you don't need (additional) signature patches for this bypass to work and it doesnt taint your unmodified files if you ever wanted to back them up later

for what it's worth this probably could (can?) be done on an unmodified console without cfw, because the eshop doesn't always require the latest firmware version to access it and buy/download games. I know before being banned I could just access the eshop without updating after restoring my nand backup, and I could buy and redownload games. I don't remember specifically installing games and trying to run them though, so maybe all the games I had just happened to not require a higher firmware version than what I had. it's possible that the eshop does check for the current firmware version before installing a game to ensure games don't get installed on a lower firmare version. I know that homebrew nsp installers don't check it though, and that you can install a nsp on a lower firmware version and then get asked to update the firmware only when you try to run the game. and these days they periodically update the eshop servers to require updating to the latest firmware version before you can access it, so it wouldn't be easy to check. but tbh since they already had the systems in place to just prompt for a system update on game launch, it doesn't make sense to also enforce it on the eshop side

 

[mspy]

For update check it needs version.txt on some url or locally. Also, it can dump to version.txt info from fw update or received by hos from tagaya server.

Does DBI dumps and uses version.txt from the firmware or from the official servers by default if the specified url can't be reached or no local file is found or if found is outdated? I mean, does it checks all the sources for the latest updates (including firmware and official servers) or it only takes into account the first working source it finds?

Also without titledb the version.txt dump from firmware and the oficial servers will not work for DLCs as mentioned before?

this is at least interesting because the system doesn't let you run gamecard ncas installed as digital contents without either patching the distribution bit check, or modifying the ncas to change the distribution bit from 1 to 0. but this shows that digital ncas will run from gamecard just fine, or at least it specifically allows updates to run from gamecard. in practice it doesnt matter for us because it's not like we would have a way to put eshop files on game cards to run them anyway, but it's interesting to know how the os works

You could run games without installing like gamecards with SX OS.
No other solution that I know of has since been able to do it.
Not even DBI.

 

[Deleted member 702243]

You could run games without installing like gamecards with SX OS.
No other solution that I know of has since been able to do it.
Not even DBI.

SX just mounts xci to a virtual game card slot, os sees game card content running from game card slot = no problem. It doesn't and couldn't mount nsp (digital contents) to game card slot

The os accepting eshop contents from the game card slot would only be useful on ofw, where everything is required to be signed. but this is blocked by many factors, like the fact that game cards require additional cartridge-specific data that is required for the cartridge to load, that eshop games don't come with of course, and the fact that properly signed eshop nsp implies a personalized ticket for games and dlc, which would only work with one specific user account. And you would need to build a game card image from scratch to contain those files, which you could never properly sign, either

It's possible updates are just a special exception anyway. But I would be interested in knowing exactly why we can't just merge update data with an existing gamecard dump, and run that on mig switch. I think it's because adding or changing a built-in update would require modifying the FileEntryTable in PartitionFsHeader, which would require changing the PartitionFsHeader hash in the cartridge header, which would break the cartridge header signature, and then it would get rejected for invalid signatures. On SX this works because signatures are ignored, but on ofw we can't do anything that makes signatures invalid of course

Anyway like I said it's not useful information at all, we can't do anything cool with it. But it's fun to learn of weird quirks like this of how the os works anyway. As long as you're actually interested in the way things work and not just playing games I guess

 

[mspy]

SX just mounts xci to a virtual game card slot, os sees game card content running from game card slot = no problem. It doesn't and couldn't mount nsp (digital contents) to game card slot

Wouldn't converting the NSP to XCI with something like Switch Army Knife or NSC_BUILDER to add the content you wish do what you are looking for?

 

[Deleted member 702243]

Wouldn't converting the NSP to XCI with something like Switch Army Knife or NSC_BUILDER to add the content you wish do what you are looking for?

I just explained why that can't work lol

 

[BETA215]

I still can't understand why people are using this. This man had proved to be untrustworthy, shady, definitely suspicious. Just use Goldleaf and don't put your devices on risk for silly reasons...

 

[Muxi]

Just use Goldleaf

However, Goldleaf only supports the installation of NSP files and does not have the same range of features as DBI.

 

[Deleted member 702243]

However, Goldleaf only supports the installation of NSP files and does not have the same range of features as DBI.

and, reportedly, doesn't even do that correctly

https://github.com/XorTroll/Goldleaf/issues/733

 

[yankii]

and, reportedly, doesn't even do that correctly

https://github.com/XorTroll/Goldleaf/issues/733

Just the price of not having an asswipe for a dev...

 

[Morce3232]

I still can't understand why people are using this. This man had proved to be untrustworthy, shady, definitely suspicious. Just use Goldleaf and don't put your devices on risk for silly reasons...

Maybe we could give duckbill finally a break? Like, I don't see him threatening or shittalking anyone in this thread.

Things have been said in the past, sure. But I don't see any bricked switches yet.

Also, the dbi pretty much IS the best software of its kind, when we get over all the drama surrounding it.

 

[johw]

Maybe we could give duckbill finally a break? Like, I don't see him threatening or shittalking anyone in this thread.

Things have been said in the past, sure. But I don't see any bricked switches yet.

Also, the dbi pretty much IS the best software of its kind, when we get over all the drama surrounding it.

best comment

 

[Deleted member 702243]

Just the price of not having an asswipe for a dev...

TotalJustice is a good egg and sphaira probably does everything goldleaf does, but better, tbh