4gb Internal Mem Unit On Limited Edition And 250gb Consoles Options

[Antman1]

After trading my 4GB Slim for a MW3 Console I soldered a connector for the 4GB Internal mem unit and noticed it does not work on the Retail Dash. I have my MW3 Console setup with a Dual Nand Cygnos360v2 board and have the Cygnos360 nand setup with a banned KV from a 4GB Slim Console. When I have the RGH Image selected and load the hacked Dash the 4GB Internal Mem unit works great. If I select the retail stock dash it does not load the 4gb Internal Memory unit.

In conclusion I have found that the Keyvault for the 250GB and Limited edition Console disables the ability for the console to see the internal memory unit. If you Glitch the Slim and use a KV from a Slim that had a 4GB Internal Memory unit it works fine.

Now I have Freestyle Dash loaded on the Internal memory unit and it is separated from my HDD.

Here is a guide on how to add the 4GB Internal Memory Unit if anyone else wants to do it.

http://unmrkd.net/heavenlymodz/uncategoriz...l-edition-slim/

This post has been edited by Antman1: Dec 13 2011, 09:09 AM

[Jumpy_Beans]

Nice! That's a clever way to keep your homebrew material off of your stock hard drive.

[Morning Call]

the 4gb module is indeed tied to the KV. this has been known. i still wouldn't trust it though. idealy you don't want ANYTHING common between retail dash and glitch, especially a 'protected' filesystem from ms itself. who knows what they plan on doing later to allow that module to work allowing them to read the contents.
if they did read it, im sure it would be an instaban. theres only one way to get data onto that module and that shows right there that in some shape or form you were mucking with the console.

[Antman1]

the 4gb module is indeed tied to the KV. this has been known. i still wouldn't trust it though. idealy you don't want ANYTHING common between retail dash and glitch, especially a 'protected' filesystem from ms itself. who knows what they plan on doing later to allow that module to work allowing them to read the contents.
if they did read it, im sure it would be an instaban. theres only one way to get data onto that module and that shows right there that in some shape or form you were mucking with the console.

I'll keep everyone posted. I have had my JTAG content and files on my stock HDD for a long time before the RGH even came out and no console of mine ever got banned or profile suspended. I dont think it is an issue at all. I just like having my Homebrew FSD dash and Apps on the internal Mem Unit so that I can switch hard drives and USB devices without worrying about my FSD Data.

I also never found anything stating the 4GB Mem unit was tied to the KV though. There was speculation and no confirmation.

This post has been edited by Antman1: Dec 15 2011, 11:47 PM

[mimk97]

I'll keep everyone posted. I have had my JTAG content and files on my stock HDD for a long time before the RGH even came out and no console of mine ever got banned or profile suspended. I dont think it is an issue at all. I just like having my Homebrew FSD dash and Apps on the internal Mem Unit so that I can switch hard drives and USB devices without worrying about my FSD Data.

I also never found anything stating the 4GB Mem unit was tied to the KV though. There was speculation and no confirmation.

do you have a 4Gb Keyvault for me :-)

[k0mpresd]

I'll keep everyone posted. I have had my JTAG content and files on my stock HDD for a long time before the RGH even came out and no console of mine ever got banned or profile suspended. I dont think it is an issue at all. I just like having my Homebrew FSD dash and Apps on the internal Mem Unit so that I can switch hard drives and USB devices without worrying about my FSD Data.

I also never found anything stating the 4GB Mem unit was tied to the KV though. There was speculation and no confirmation.

ive had jtag content (xexmenu) on my retail hdd ever since the first release of the software and never a ban of any type.

also, i have a halo reach console with the connector for the 4gb module. all i did was plug the module on and it worked no problem.

[Morning Call]

im not saying ms will ban you guys just that there is a chance. best way to stay safe is to keep everything separate. that is all.

you have to assume that anything in common between the two types of dashboards can be used against you in a court of microsoft

[Morning Call]

just thought of something you could do.

you've already got dual nand working, so why not disable the 4gig module when booted to retail dash utilizing the CE

[marcus.miranda]

Hello guys,

Good day to you all!

I'm bringing this topic up again with a question: I have a Slim Gears 3 Limited Edition dual boot console without the 4Gb connector, so I'm assuming I have a KV that has the INTMU disabled (assuming because I have not tested it yet). If I have the INTMU disabled and use this MOD to add a 4Gb module, will it be safe to use this HW MOD online on my retail NAND or should I somehow cut the 4Gb power when switching to the retail NANDs?

If disabling is the choice, what should I use to disable it (switch, MOSFET, any other component)?

Thanks guys!