Alright I'm pretty sure I did everything right,
I made a map in Forge,
saved it,
using a Datel Transfer Kit I got off of the MU using XPort,
opened it up in Forge 2.3,
modded it,
saved it,
then i opened it up in HaloMods Container Tool and resigned with my profile ID and my device ID,
then I deleted the old map off of my MU and put the modded one on there.
I load up Halo with my profile on the MU and it doesnt show up.
I go look in the System Blade of the Dashboard and it shows a corrupt file which I'm pretty sure is my map, does anybody know what I did wrong? Thank You if you can help me.
transfer issue
- blade22222222
- Posts: 75
- Joined: Mon Feb 26, 2007 4:57 pm
- Location: halomods duh...
- Contact:
- mxrider108
- Posts: 456
- Joined: Thu Jun 29, 2006 6:39 pm
- Location: Cary, NC
- Contact:
![]() |
![]() |
Re: transfer issue
To be honest, I have had some issue with the HM container tool personally. I'm probably using an old version or something, but the error you get is exactly the same I get when using the HM tool. I have not figured out a fix for this issue besides simply using a different resigner...blade22222222 wrote:Alright I'm pretty sure I did everything right,
I made a map in Forge,
saved it,
using a Datel Transfer Kit I got off of the MU using XPort,
opened it up in Forge 2.3,
modded it,
saved it,
then i opened it up in HaloMods Container Tool and resigned with my profile ID and my device ID,
then I deleted the old map off of my MU and put the modded one on there.
I load up Halo with my profile on the MU and it doesnt show up.
I go look in the System Blade of the Dashboard and it shows a corrupt file which I'm pretty sure is my map, does anybody know what I did wrong? Thank You if you can help me.
- blade22222222
- Posts: 75
- Joined: Mon Feb 26, 2007 4:57 pm
- Location: halomods duh...
- Contact: