Hacking Easy steps to remove "update nag [only]" on EmuNAND

[noctis90210]

ok im going to make little tutorial removing update nag on emunand.
take note that im focusing on update nag only.

requirements:
- of course 3ds sysnand 9.2 below
- rxtools
- sysnand without update nag
- no need to use complicated PC decrypting tools, just 3ds sysnand 9.2 below with unlinked EmuNAND.

Step 1
launch rxMenu
go to "dumping"
go to "dump nand files"
choose "sysnand"
choose "import.db"
import.db will be located at SD:/rxtools/ folder
save this import.db to safe place so that if update nag comes again, we will not going to do this step 1 again, just place again the import.db to SD:/rxtools/ folder

Step 2
go to "injection"
go to "inject nand files"
choose "emunand"
choose "import.db"
run emunand.

i dont think we need to delete the actual updates already downloaded, cuz we will install it anyway in future once hack for current FW will come, at the same time, no other benefit we can gain if we delete the actual updates, for now update nag is our focus to remove, without the update nag, we are safe not to accidentally update our emunand.

if you also want to avoid update nag to come again, just always launch freemultipatcher every time you boot to emunand. dont be lazy, it will just take 10 sec :-)

 

[dpad_5678]

 

[noctis90210]

waaah!!! not funny, the face is so scary :-P

 

[duffmmann]

I'm confused because 2 of your requirements seem to contradict each other:

-3ds sysnand 9.2 below
-sysnand without update nag


If my sysnand is 9.2 or below, then how could it possibly no longer have the update nag to begin with? And if it didn't have the update nag anymore, couldn't we have just followed the same set up we did to remove it from the sysnand for the emunand? Or am I misunderstanding/missing some info here?

 

[noctis90210]

I'm confused because 2 of your requirements seem to contradict each other:

-3ds sysnand 9.2 below
-sysnand without update nag


If my sysnand is 9.2 or below, then how could it possibly no longer have the update nag to begin with? And if it didn't have the update nag anymore, couldn't we have just followed the same set up we did to remove it from the sysnand for the emunand? Or am I misunderstanding/missing some info here?

what i mean about 3ds with sysnand 9.2 below are 3ds that can run rxtools or simply xploitable firmware.
this sysnand should HAVE NOT update nag (clean import.db)

were going to xtract import.db of sysnand and transfer it to emunand so that the emunand will not ask you all the time for an update...
hope, everything is clear :-)

 

[duffmmann]

what i mean about 3ds with sysnand 9.2 below are 3ds that can run rxtools or simply xploitable firmware.
this sysnand should HAVE NOT update nag (clean import.db)

were going to xtract import.db of sysnand and transfer it to emunand so that the emunand will not ask you all the time for an update...
hope, everything is clear :-)

I am on a sysnand of 9.0, so running rxtools isn't an issue. Its the other part that confuses me, it sounds like your saying that my sysnand should not have the update nag. But it does have the update nag because it wants me to get to the latest firmware, just as my unlinked emunand does.

 

[noctis90210]

I am on a sysnand of 9.0, so running rxtools isn't an issue. Its the other part that confuses me, it sounds like your saying that my sysnand should not have the update nag. But it does have the update nag because it wants me to get to the latest firmware, just as my unlinked emunand does.

so you dont have this requirement:
sysnand should have not update nag.
what we really need is a sysnand that doesnt have update nag. get the files in it...
then inject that file to emunand so that emunand will remove its update nag...

 

[cvskid]

So if i wanted to get rid of a update nag for gateway 3ds, i would use these steps to get rid of the update nag, then switch back to gateway emunand and it would work since they both use the same emunand right?

 

[duffmmann]

so you dont have this requirement:
sysnand should have not update nag. what we need is a sysnand that doesnt have update nag.

Can you point me in a direction to remove the update nag from the sysnand? I didn't know this was possible to remove, but if it is, then I absolutely would love that.

 

[Criminal90]

Can you point me in a direction to remove the update nag from the sysnand? I didn't know this was possible to remove, but if it is, then I absolutely would love that.

turn on the Nintendo 3DS while holding A+R+L+Up(DPad) and than select cancel

 

[noctis90210]

So if i wanted to get rid of a update nag for gateway 3ds, i would use these steps to get rid of the update nag, then switch back to gateway emunand and it would work since they both use the same emunand right?

just run rxtools first to extract/inject the file. then you can boot gateway without update nag if you finish the 2 steps i mentioned.

Can you point me in a direction to remove the update nag from the sysnand? I didn't know this was possible to remove, but if it is, then I absolutely would love that.

i heard that you need to push some button if youre going to turn on your 3ds, i just dont know what exactly are those button, and the 3ds will ask you to delete the update... im not sure...

edit: oh there's the answer by @Criminal90 about your question...

 

[duffmmann]

I'm not seeing an import.db file, but I do see a ticket.db file is that what we should dump and inject, or is there a key to getting the ticket.db file to show up as an option?

 

[noctis90210]

I'm not seeing an import.db file, but I do see a ticket.db file is that what we should dump and inject, or is there a key to getting the ticket.db file to show up as an option?

no, not the ticket.db, its a different file... what we need is import.db...
use the latest nightly of rxtools, im using the build from nov 15, i think newer builds like nov 19 is also stable...