Hacking Help Please Black Squares In emuNAND

[jaksy]

This is why its a good idea to keep detailed text files on the .cia you install to your console, to include title IDs and unique IDs.

It'd be nice if FBI had some kind of logging feature with the name and ID of cia's you've previously installed so you can crossreference.
To my knowledge though there's no such convenience, and I'm not going to start logging everything by hand.

 

[kehkou]

It'd be nice if FBI had some kind of logging feature with the name and ID of cia's you've previously installed so you can crossreference.
To my knowledge though there's no such convenience, and I'm not going to start logging everything by hand.

That would be nice, at least to show the names of installed software in FBI. In the digital manual of most games, however, the title ID is on the bottom of the first page. It's also printed on the cartridge and the sticker.

 

[wormdood]

This is why its a good idea to keep detailed text files on the .cia you install to your console, to include title IDs and unique IDs.

this would only be relevant if it included failures as well as successes . . . a total history

 

[kehkou]

this would only be relevant if it included failures as well as successes . . . a total history

True, but FBI doesn't 'fail' to install SD only titles to the nand. If you have the title ID of every game you install, you could search for it and delete it without fear of a brick.

 

[wormdood]

True, but FBI doesn't 'fail' to install SD only titles to the nand. If you have the title ID of every game you install, you could search for it and delete it without fear of a brick.

my case was 4 instances of fbi from failed injections . . . so while fbi itself does not fail you can still fail to inject

 

[kehkou]

my case was 4 instances of fbi from failed injections . . . so while fbi itself does not fail you can still fail to inject

I had the issue of FBI not injecting. I injected it into a nand backup instead, but the black square was there prior to that.

Before seeing this thread, I thought the black squares were just CFW files to make rxtools work, in the same vein as early 1.5 PSP homebrew with the corrupt data icons. after using sysupdater, I kinda wondered what happened to the squares

 

[wormdood]

I had the issue of FBI not injecting. I injected it into a nand backup instead, but the black square was there prior to that.

Before seeing this thread, I thought the black squares were just CFW files to make rxtools work, in the same vein as early 1.5 PSP homebrew with the corrupt data icons. after using sysupdater, I kinda wondered what happened to the squares

i was told that it was a bug but when i learned more about how cfw works i became fixated with this problem and getting ds mode to work from emunand ( . . . still pitching ideas around with another group of tempers)
i don't like having a sub-par system

if you updated with sysupdater the there is a good chance the update probably overwrote the improperly installed files if they are on sysnand destination = nand but i am glad we figured out an easy manual way to remove them

 

[kehkou]

if you updated with sysupdater the there is a good chance the update probably overwrote the improperly installed files if they are on sysnand destination = nand but i am glad we figured out an easy manual way to remove them

I wonder why they show up on virgin consoles, like mine were, in the first place. Is the big N's installer code really that buggy?

 

[wormdood]

I wonder why they show up on virgin consoles, like mine were, in the first place. Is the big N's installer code really that buggy?

no offence but i don't believe they ever do instead i think people are the sole cause and they either
1.) truly don't realize they have made a mistake along the way
2.) they don't remember making a mistake along the way
3.) the guide they followed made a mistake (the guy who wrote it is only human after all)
4.) bought the console used the previous owner made a mistake along the way or even the previous owner got it used in witch case you know even less about the 3ds
5.) there simply too prideful to admit there mistake
. . . i can go on and on with perfectly valid reasons to not recall the exact time the files were actually installed and when you take into consideration that only specific revisions of rxtools apply the set of patches that allow the improper files to display in the first place my point should become clear

but assuming the bug(files) were in fact left there by nintendo then it still would not matter as nintendo 3ds software on its own will never display them and with a simple update they can(?) erase them

 

[kehkou]

no offence but i don't believe they ever do instead i think people are the sole cause and they either
1.) truly don't realize they have made a mistake along the way
2.) they don't remember making a mistake along the way
3.) the guide they followed made a mistake (the guy who wrote it is only human after all)
4.) bought the console used the previous owner made a mistake along the way or even the previous owner got it used in witch case you know even less about the 3ds
5.) there simply too prideful to admit there mistake
. . . i can go on and on with perfectly valid reasons to not recall the exact time the files were actually installed and when you take into consideration that only specific revisions of rxtools apply the set of patches that allow the improper files to display in the first place my point should become clear

but assuming the bug(files) were in fact left there by nintendo then it still would not matter as nintendo 3ds software on its own will never display them and with a simple update they can(?) erase them

I don't believe my squares were ever uninstalled, since they were on the console I preordered, then shelved since the wi-fi board became unplugged, then unshelved a week ago when I heard there was a CFW for it. My steps were

1) Install MSET (via wood card)
2) Put rxTools on SD card
3) Launch MSET, rxTools
4) Black squares

The modified update helped hide the squares.

I actually did install to nand by mistake once, and it produced a black square in the updated console, but I caught my mistake right away and uninstalled it (the only title in my nand that reported its product code instead of a unique ID). this was way after updating removed (or hid) the original black squares.

I think the black squares come in different 'flavors'.

 

[MelonGx]

If you have black squares only on rxMode SysNAND 4.X, I think it may be an rxTools bug.

http://gbatemp.net/threads/release-...olkit-fw-2-0-9-2.382782/page-727#post-5813269

 

[porko]

i haven't read the whole thread, but here's my experience with those pesky black boxes:

they showed up in my emunand when i set up rxtools a 2nd time (after having updated the emunand the first time), and they disappeared when i updated the emunand. so my guess is they're new stuff introduced in the new firmware, when i updated the first time they must have been embedded in there. anyways, that's my 2c.

 

[kehkou]

If you have black squares only on rxMode SysNAND 4.X, I think it may be an rxTools bug.

http://gbatemp.net/threads/release-...olkit-fw-2-0-9-2.382782/page-727#post-5813269

It's quite possible. Maybe in conjuction with a firmware threshold. Mine are a 4.5, and a 6.1, now both 9.0.
Anyone have the squares on 8.x?

 

[EddieEddie90]

N3DS running Homemenuhax, ctr manager, hbl and rxTools

My nand's are completely unlinked

I never had this problem before until today, this is what happened

I upgraded from an old version of rxTools (10/02) to the very latest posted by @Dean_

rxTools all upgraded fine and even Devmode / Pastamode now working

However when i entered emuNAND i was confronted with 2 gifts that needed unwrapping (neither had descriptions)

I unwrapped both gifts and now have 2 black squares, with no descriptions, if i try to load them i just get the Nintendo screen frozen

I have a lot of other installed content on the machine already and none of it is affected

It is just these 2 black boxes which i cannot remove

I have searched the forums and found others who have had them, some have never resolved the problem, others had to reformat the emuNAND

I am hoping somebody can please provide me with a solution to this

Thanks in advance for any suggestions

PROBLEM SOLVED!! Ok, after having much discussion here and lots of good advice from many members including @wormdood @Pingouin7 @MaNiAlJoWo @subcon959 @Queno138 @jaksy a solution to my problem of the unwrapped gift's producing black boxes has been resolved

I installed BBM (normally use only Devmenu) and found multiple instances of Devmenu and SysUpdater either installed or wrongly installed, so after removing them with BBM and rebooting the system they were gone!!

As simple as that, thanks for all those who helped

I have read half of this thread, and I got the solution, which is quite simple:

*NOTE: This is just in case you happen to have black boxes in emuNAND. I don't really know if this works with the sysNAND, but it should do without trouble.

- Open up FBI installer and check the unique ID for all of the CIAs you have installed on your system over the time (assuming you have them on your SD card). Better check the IDs of those you have installed lately and believe are the cause of the black boxes appearing on the emuNAND.

- Then, switch to delete mode on NAND, and check among all the NAND's titles the one that matches with the title unique ID you took note before. Then proceed to delete it and then reboot the system to see if the black boxes disapeared.

I got rid of TWO black boxes this way. I hope I made myself clear and I guarantee this method will work, you don't need to start fresh or anything.

Hope I helped!

PS. Sorry for my bad english. I'm from Mexico.