7 replies to this topic

[Marso]

Hi, I sent my Xbox 360 Jasper 512 Mb to a workshop where I got my Maximus 360 Nandflasher installed -I'm quite bad at soldering- and running under the latest Freeboot (supposedly with Xbox 1 and MU support, with no corruption issues).

There, the workers always do all files backup: config.bin, kv.bin, dump.bin (odd it is 528 Mb for a 512 Nand, isn't it?, nand70.bin, smc.bin and KEY.txt in a CD. Also files from DVD unit flashing.

I enjoyed one month of happy exploration and reading tutorials -most of them contradictory and making you get lost- but I kept doing small advances day after day, specially regarding homebrew and "easy" issues: setting up a new 500 HDD, managing FTP, using Quickboot...

The problem was when I was copying something FROM the internal MU: The console rebooted and I was not shocked since it rebooted apparently without a problem when in other occassion, XM360 ran for the first time.

But when I turned it on again, it didn't work: no video signal, no controller connection...

At first I was affraid of getting a "white brick", and starting re-reading many topics which I read long ago looking for an answer: I came across the FREEBOOT MAKER 2.4 rev 3 software (Piggy) and NandFlasher 360 1.0 for Windows (a good VGUI to simplify things).

I made a FreeBoot.bin image with the Piggy and then uploaded it to the console with NandFlasher, and it turned back my console to live, but with a problem, NO XBOX 1 GAMES SUPPORT.

I kept on investigating and, decided to ERASE MEMORY UNIT TO TRY TO DUMP BACK ORIGINAL NAND back to 6321 dashboard and start anew.

A BIG MISTAKE. From here, I'm completely stuck and don't know what to do. My brain is too blocked to go doing anything else. I tried to re-create a freeboot (64 mb)and upload to console and nothing, uploaded back the 512 MB nand (the file is 528 and that puzzled me) and no results; tried to inject KV and Config files when dumping in NandFlasher and nothing... I've written and Erased Memory Unit several times and no results. Xbox 360 doesn't boot.

WHAT CAN I DO? I'M TOTALLY DESPAIRED AND STUCK!

PLEASE, CAN ANYBODY TELL ME, STEP BY STEP, DUMMY-LIKE, WHAT TO DO?

Thank you very much.


PS: Can anybody tell me what is that black switch that is on Nandflasher under RST letters, next to the mini-USB connector? I haven't the chip manual. It's on the black board, not the version of the board which comes in a plastic case. I read it's precisely a switch, but which position is which when it's not indicated?

[vgcrepairs]

the button is Reset (RST) when the nandflasher is plugged into USB with no activity it will go to sleep if your PC supports that, and sometimes wont wake up so you can press reset to wake it up or unplug USB and plug USB back in same thing.

#1 it has been posted over and over and over to NOT use the built in MU, erase your nand, uplaod the 70mb freeboot file and leave the MU FORMATTED!!!!


If you flash your orig.bin back to the console it should bring it back to life

What software are you using to flash? Nandpro 2.0b ??

Freeboot is 9199 kernel based, MS REMOVED XBOX SUPPORT with 9199, this was is not a kernel issue this is what MS did

[Marso]

Thank you for your quick answer. About RESET button, I hadn't any manual; all came installed. I told them to use latest Freeboot (with DashLaunch patch) to support, Xbox 1 and Full Memory Access altogether, plus XKailink features.

I had read that latest release of FB solved MU corruption issues; in fact, it was during a MU to HDD copy of a folder that it became corrupt. The problems of many posts in many forums are that there's an excess of information, not always well contrasted and quite confusing.

To flash I used first Freeboot Maker 2.4 r3 (Piggy), and NandFlasher 360 1.0 for Windows (it has a nice and easy VGUI) to upload the .bin files. The problem is that when I use this latter, I uncheck the FULL NAND READ / WRITE FEATURE, and load a nand70.bin file and it says "Wrong filesize: 70x mb. Expected... 60x... mb or 66 mb with meta". Then I upload the Freeboot.bin file generated by "Piggy" and what I get is a nice Christmas Tree with 2 pairs of flashing red and green lights, switching upside down, and no video nor controller synch (which is an advance to what I had obtained up to now: nothing after reflashing).

I don't know if the problem is in the generated Freeboot.bin or that I can't inject Key (this is taken automatically by Piggy), KV and Config properly or if I have to restore the 512 MB Nand (it is actually 528 mb, which is odd, but in Alechip, one of your local Spanish dealers, did it all and gave me those files backup) prior to Freeboot.bin.

PS: I don't remember exactly, but I've also created a DUMMY_NAND_FILE for those 512 mb.

Edited by Marso, 03 September 2010 - 07:59 PM.

[vgcrepairs]

when using freeboot maker select your entire full orig.bin file not nand70.bin ( or did I misunderstand you?)

I have been telling people over and over DO NOT USE ANY GUI software!!!

Use the dos command window with nandpro !!!!!

[Marso]

I was using the original 528 MB (s this size possible? nand, and it produced a Freeboot.bin of 64 mb. The problem is that I think that I don't know how to inject KV and Config File of my console in the Freeboot.bin image. I remember having read that this should be 66 mb, and not the 64 it creates.

Besides, I have problems in using DOS commands, not by proper DOS Syntax but rather by the unexplained path:

1. Extract your original image

Extract your original 7371 [recommended] image with the following command:

ibuild.exe x -d temp\ -p [cpu key] -b [1bl key] 7371.bin

My console is actually under 6723 CB version; I assume that I can change that to 6723.bin, but the problem is with [1bl key]. I have only CPU KEY in a TXT file. But what is the 1bl key? DD88AD0C9ED669E7B56794FB68563EFA as I have seen in other forum?

Thank you.

[vgcrepairs]

freeeboot maker automatically sets it allup for you

If you use freeboot maker and you get red/green lights that means the keyvault is not correct or installer did not give you the proper backup file

email me sales@vgcrepairs.com, I will be gone for holiday weekend

[Marso]

Thanks for your help. I tried to rebuild freeboot image several times (with the kv the installer provided me) and in the end, it worked. I do not know if it's a PC problem (I formatted it not long ago), an antivirus issue, but in other occassions it was turned off too and no results, the USB wire problem, Freeboot Maker issues... Who knows?

The fact is that it is functional now, so kv must be right (the installer has a good range of experience in doing Jtags) though image is not patched to Xbox 1 compatibility or XKailink. I'll go on trying again, keeping my renamed FREEBOOT_CORRECT.bin in case I screw it up again.

Thanks for your help again.

EDIT: After using Freeboot Maker 2.4 rev.3 and creating a custom Freeboot image, inserting the Dashboard Launcher 1.0 with the compatibility Patch and Full Memory Access, it didn't work. Xbox 1 rebooted the console. However, I tried to experiment and copied KXam.patch file to HDD1:\ root to get ready for XKaiLink and... SURPRISE! IT SOLVED ALL THE PROBLEMS! Xbox 1 compatibility went back, I have access to one Xbox Original game I bought in the Bazaar but could only run in my untouched Xbox 360 and not possible, up to now, in the exploited one, besides having run Yariswap and XM360 1.8 on the file. Now it is ok.

[vgcrepairs]

greatm now stop using the MU