I think that to avoid getting frankenfw when attempting to do a downgrade, one thing that can be done is downgrade to 9.0 or 9.1. Then if you get a frankenfw you can upgrade to 9.2 with a cartridge.
This actually seems like a pretty good idea, I wonder if anyone else here could chime in,
I don't see how this really solves anything. If you tried to downgrade to 9.0, and it wasn't a complete downgrade, you'd be left with various 9.0+ titles (Same as downgrading to 9.2). You'd still need to downgrade these titles at some point. Updating to 9.2 afterwards wouldn't solve that (As a cartridge update wouldn't try to change titles that have a higher version than the 9.2 update. So, in the end, you have the same frankenfirmware, but you ran an update/downgrade process twice to get there).
Last edited by Townsperson,
I once franked an N3DS. I tried to update back to 9.9 with AC:HHD.
Game passed the update and never booted.
Game passed the update and never booted.
Not to hijack this thread, but I'll just leave the question out there:
Sysnand on 9.2, updated NVer to latest to access shop, then downgraded it back to 9.2
Only one title updated then downgraded back to original firmware..
Is that considered frankenfw?
Sysnand on 9.2, updated NVer to latest to access shop, then downgraded it back to 9.2
Only one title updated then downgraded back to original firmware..
Is that considered frankenfw?
Im really starting to believe that frankenfirmware isnt such a problem. Correct me if im wrong but if you downgrade with frankenfirmware (and lets say its good enough to install cfw/run HBL) then youre not actually in trouble as you have all you need from 9.2 while using higher FW from emunand. And if you use another route it gets better because in the case of
a) deciding to leave hacking completely and use vanilla FW
B) use a9lh and update sysnand to the latest FW
you will always be updating sysnand which will get rid of frankenfirmware. And since your 3ds didnt brick you could also just try running sysupdater again if mismatched titles are really annoying.
So unless theres a problem like frankenfirmware blocking exploits (which ive heard of rarely; mostly during the early days of memchunkhax2 sysupdater testing) I dont see why its a problem.
a) deciding to leave hacking completely and use vanilla FW
B) use a9lh and update sysnand to the latest FW
you will always be updating sysnand which will get rid of frankenfirmware. And since your 3ds didnt brick you could also just try running sysupdater again if mismatched titles are really annoying.
So unless theres a problem like frankenfirmware blocking exploits (which ive heard of rarely; mostly during the early days of memchunkhax2 sysupdater testing) I dont see why its a problem.
The thing about frankenfirmware is that it's unpredictable. Sure you may be able to use homebrew after a "downgrade", but that doesn't mean in the future everything will be compatable. Unless it's on purpose (and even then it's still a worry), you should never have frankenfirmware on your system. Also some people like me have a9lh but don't want to update or tamper with their vanilla sysNAND for obvious reasons. You're thinking of frankenfirmware in the best of light, under optimal conditions and for many people, it doesn't work out that way.
But so far all the methods ive seen to repair it requires either updating via game cart and restart the process or tampering even more with the system by either individually installing/uninstalling system cias which honestly sounds terrible considering the risk. Are their any stats regarding how many people get frankenfirmware? Because if a lot of people are getting it and are stranded on frankenfirmware then maybe the downgrade process needs to be reevaluated
I doubt anyone's keeping track, but there's always a good 10+ people a week that seem to have some form of frankenfirmware. And it may be a terrible process, but most of the time the reason for it is because homebrew won't work or they can't get into emuNAND.
Similar threads
