Would this work on my dev unit 3DS? (QUESTION)

[ghost]

I know i'm a familiar face from the Project_CTR issue, this is not really an issue but more a question, I compiled sysUpdater and signed it with devkeys, installed the .cia file to my dev unit 3DS, (I also took a screenshot with the Test Menu if you would like to use this image for future references ---> http://i.imgur.com/lJ8FKmd.png?1 ) I have the latest system update cia from the latest CTR-SDK 11.4.0 and extracted update cia files from the .csu files, my question is would sysUpdater even work? or would it just give me a hardbrick? I'm asking this mainly because FBI doesn't work on dev units so I just wanna make sure if this could possibly work on it.

[profi200]

I can't guarantee it will work but on the other hand i see no reason it should not work provided all used services are there and the title version check works correctly. It requires the standard services most apps should have access to + am:u or am:net.

How does FBI fail? That could useful to know.

Edit: Did you ever open your devunit? If not do you plan to do that? High res pictures of the hardware would be nice because no one made such pictures yet.

[Reisyukaku]

A lot of dev system apps have different title IDs, and i believe this is one reason why FBI doesnt work (but i could be wrong). Basically from my observations, the last digit of the TID low means this: 1 = dev 2 = retail 3 = retail (safemode) (i.e AM service on dev is 00001501) Aside from that, theres a lot of minor changes in code among apps ive looked into (spider, homemenu, etc) Edit: Btw, the hardware looked pretty identical to the retail units. Main differences between the systems is different bootroms and keys

[profi200]

What you are talking about is the TitleID Variation: http://3dbrew.org/wiki/Title_list (scroll down)

I was hoping for high res pics. Especially the second gamecard slot is interesting and how it is connected to the SoC.