Hacking Question - downgrade to update

[kiel379]

Hey guys
Been reading alot about these "franken firmwares" caused by downgrading.
Would downgrading to a firmware bellow 9.2 then using sysupdater to update to 9.2 fix the problem?

 

[kiel379]

Bump

 

[Games&Stuff]

What?

 

[Rattor]

Hey guys
Been reading alot about these "franken firmwares" caused by downgrading.
Would downgrading to a firmware bellow 9.2 then using sysupdater to update to 9.2 fix the problem?

Why would using sysupdater to downgrade then sysupdater to update be more stable than using sysupdater once to downgrade to the firmware you want? The issues with the frankenfirmware are a possible consequence of using sysupdater, so all you're doing is doubling the chances sysupdater screws up and messes up one of your system components.

 

[kiel379]

From what I heard downgrading can skip over some files and keep the newer firmwares files in its place.
Aparently this is what has caused people to have some issues after downgrading.
If I downgraded to say 9.0 then upgraded to 9.2 would it give a clean install of 9.2
Basically get rid of the leftover files from the higher firmware.

--------------------- MERGED ---------------------------

The franken firmware issues have only been happening since downgrading was possible so I would assume that the update function of sysupdater is fine

 

[Tony_93]

Why would using sysupdater to downgrade then sysupdater to update be more stable than using sysupdater once to downgrade to the firmware you want? The issues with the frankenfirmware are a possible consequence of using sysupdater, so all you're doing is doubling the chances sysupdater screws up and messes up one of your system components.

Wrong, this frankenfrimwares are caused by using this modified sysupdaters that use Memchunkhax2 to downgrade, either the one from Julian20 or the one by Hux... (Can't remember his name now).

But there is the official sysupdater 0.4.1 by profi2000 that works flawlessly updating firmwares, users here and myself have been using it to update systems to 9.2 without issues for months now.

So, using a modified-memchunkhax2 sysupdater to downgrade to a lower frankenfirmware and use the official sysupdater to get to a clean 9.2 sounds like a great idea actually.

 

[kiel379]

It's not often I have a good idea.
Printing this page out and framing it asap.

 

[Aroth]

Hey guys
Been reading alot about these "franken firmwares" caused by downgrading.
Would downgrading to a firmware bellow 9.2 then using sysupdater to update to 9.2 fix the problem?

No it won't

The franken firmwares are the result of the fact that newer FWs have more system titles than older ones. For example 10.3 on the N3DS has 110 titles. 9.5 only has 105, and 9.2 only has 102 titles. Unless and until sysupdater has a way to check for and delete the extra titles that were added on firmwares between 9.3 and 10.3, downgrading will result in a franken-firmware. Trying to "update" from 9.2 to 9.2 with the official sysupdater will not fix this either, because it won't remove the extra titles.

The upside is that this will not prevent you from installing CFW in most cases now (excepting a few rare strange cases). On the other hand you are more prone to weird little glitches and bugs that are very hard to narrow down because of the franken firmware.

 

[lynismybae]

The franken firmwares are the result of the fact that newer FWs have more system titles than older ones. For example 10.3 on the N3DS has 110 titles. 9.5 only has 105, and 9.2 only has 102 titles. Unless and until sysupdater has a way to check for and delete the extra titles that were added on firmwares between 9.3 and 10.3, downgrading will result in a franken-firmware. Trying to "update" from 9.2 to 9.2 with the official sysupdater will not fix this either, because it won't remove the extra titles.

Can somebody provide more insight into this? I was under the impression that sysupdater removed the pre-downgrade firmware during the process.

 

[Aroth]

Can somebody provide more insight into this? I was under the impression that sysupdater removed the pre-downgrade firmware during the process.

Unfortunately the code repos for the mch2 versions were removed so i can't exactly link it to you anymore. But from what I saw it grabs titleID and version info from each cia, compares it to the one installed, and if its not a match it deletes the existing cia and then installs the new one. Considering the only file lists it has access to are your installed titles and the list of files in the updates folder, it has no way of knowing which extra titles to delete.

 

[lynismybae]

Unfortunately the code repos for the mch2 versions were removed so i can't exactly link it to you anymore. But from what I saw it grabs titleID and version info from each cia, compares it to the one installed, and if its not a match it deletes the existing cia and then installs the new one. Considering the only file lists it has access to are your installed titles and the list of files in the updates folder, it has no way of knowing which extra titles to delete.

I see. So does upgrading with sysupdater work in a similar fashion?

 

[Aroth]

I see. So does upgrading with sysupdater work in a similar fashion?

As far as I know, upgrading works by installing the new title over the old title. It doesn't bother uninstalling because its assumed all the new titles are of a new version.

Also, to my knowledge, no update has removed a title from use. If a service is removed, the title associated with it is replaced with a stub title.