If my understanding of English helps me, it seems to me that SciresM wrote that this update doesn't look like a minor under the hood...
It does not look minor under the hood, per ninupdates.
— Michael (@SciresM) April 6, 2021
They have skipped minor updates before.
Yeah :/If my understanding of English helps me, it seems to me that SciresM wrote that this update doesn't look like a minor under the hood...
I hope the spoof is still possible...
https://twitter.com/SciresM/status/1379226450994208768
Thank you very much, but Emutool is insignificant work compared to what all of you are doing here and in other threads.Yeah :/
Also, I can't find fw 12.0.0 files, so I guess I'll need to update sysnand... anyone has them or knows where those could be ? darthsternie doesn't have them...
Btw, thank you for developing EmuTool @TheyKilledKenny
Yes, this is what I told you a few pages before, patches.ini in bootloader folder results in the same red alert.
...
{------ Atmosphere ------}
[Atmosphere EMUNAND]
payload=bootloader/payloads/fusee-primary.bin
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_atmosphere_hue.bmp
...
If you try that on 12.0.0, you'll brick %100.
The spoof has nothing to do with official firmware. It'll always work on SX OS 3.1, no matter wich firmware is installed.
same answer
I am messing a bit with FW12, sysnand, emunand, restore,... long story short, trying what I said I would do, trying this, but in an emunand
Let's see if I can finish it... not sure yet.
What are you trying to achieve ? To downgrade package2 ? Like in those binaries from shipengliang.com ?I am messing a bit with FW12, sysnand, emunand, restore,... long story short, trying what I said I would do, trying this, but in an emunand
Their "spoof" is flashing 11.0.0's package2 on 11.0.1, which would brick 12.0.0.
Hi @eliboa and thanks for NxNandManager.
Trying is not that much of an effort That's why I have taken extra care to do this in emunand and have backups of everything...
I'm perfectly agree with you. It is a spoof, a fake, a parody, I don't know how to call it. Nothing to do with official firmware support...
N made massive breaking changes in 12.0.0.Hi @eliboa and thanks for NxNandManager.
To be honest I don't know what changes those package2 files bring. I did the 11.0.0/.1 frankenbuild yesterday and I though trying this ( almost done, just have to migrate atmosphere style emuMMC to sxos style emunand/partitioning and test ). So, I don't know what will change and what wont. Also, I don't know about keys. I did create a new prod.keys from a fw12 emunand before doing the package2 patching, without it your new NxNandManager, 4.1.2, was saying Bad Crypto, but after creating the one from emunand with fw 12.0.0, it works fine. I am now dumping the whole thing and formationg+repartitioning with sxos+restoring from the frankenfw build. I will try.
My low hope was the changes in that package2 were not that big but the "hooks"/patches sxos does were in nonchanged places or that they are a bit flexible, not hardcoded... I don't know
--------------------- MERGED ---------------------------
That's why I have taken extra care to do this in emunand and have backups of everything...
Check here what SciresM wrote about 12.0Ok
