After a partial downgrade from >=11.0, the browser nag remains (and the browser is unusable from a partial downgrade from 11.1/11.2 where the browser was not downgraded)

This happened when I downgraded a New3DSXL on 11.0 by downgrading its NFIRM to 10.4 with dgtool, making a NAND backup, tinyformatting, and then trying the downgrade from oot3dhax. The first time, the system crashed to the Nintendo Error screen when trying to install 0004003000008F02.cia (it partialed). After powering off, and powering back on, I tried to use browserhax but the browser nag (which I had before the downgrade) remained, so I had to use oot3dhax with the New3DS 9.2 payload to get back into HBL and downgrade again (the downgrade succeeded the second time). However, people without a primary or secondary cart exploit downgrading from 11.1 or 11.2 (with 10.4 NFIRM) would be stuck here, as the iptable/browser nag bypass doesn't work on the 11.1/11.2 browser. People on 11.0 who used the iptable method successfully would still be able to use it, unless they got the browser nag at some point.

Conclusion: If a 9.2 partial downgrade does not downgrade the 11.2/11.1 browser, people will need a primary or secondary cart exploit to get back into HBL and complete the partial downgrade. If they downgraded from 11.0 and do not have the browser nag, they can use the iptable method with the 9.2 payload on their SD card as already directed in the guide. However, if they already have the browser nag on 11.0, they will need a secondary or primary cart exploit to get back into HBL to complete the downgrade, as TinyFormat removes secondary exploits stored on the SD card (like steelhax).

hacks-guide / Guide_3DS

After a partial downgrade from >=11.0, the browser nag remains (and the browser is unusable from a partial downgrade from 11.1/11.2 where the browser was not downgraded) #784