貌似是4g破解的教程 求达人翻译

youyefu

如附件

youyefu

RUNNING FREEBOT / RGH2 ON CORONA 4G BOARDS
CONNECTION BETWEEN
NAND (U1D1 port) AND SD CARD ADAPTER
Notes / Warnings:
a) You can connect only DAT0, (not connect DAT1, DAT2 nor DAT3). This is proven to
work, if you have problems try connecting the 4 data lines.
b) A resistor of 68 ohm (or near that value) is required between the Pin 4 on the Sd card
adapter and the Pin 1 of the U1D1
c) Some SD Card readers JUST DONT WORK, make sure your wires have good solder
and if dont work try another card reader.
d) Once you succeed on connect your Nand to the PC, windows will detect it as
UNFORMATTED drive, this is normal DO NOT SELECT TO FORMAT THE NAND !!
e) After any write to the nand do a SAFE REMOVAL of the drive letter assigned.
f) A wire must be placed on one of the legs of the crystal near the Southbridge and the
ground side of the C1E16, check next picture
g) The console must be connected to its AC adapter but on stand by, connect
first the console then plug the usb sd adapter on the PC
Software Requisites:
a) Maximus SDTOOLS 1.5 or later, grab them from www.360nandflasher.com
b) In order to run the tools you need to have installed (if not already) the Visual
C++ redistributables.
http://www.microsoft.com/en-us/download/details.aspx?id=5555
b) Jrunner latest versions
c) corona16 donor files, included on the zip file with this guide.
Note on this tutorial. We will show you how to boot RGH2 on your corona 4G
board, please note since we will use the nofcrt option your drive will not be able
to boot games from the dvd (will do fine from hard drive). This can be fixed if
you provide your fcrt or wait for the current tools (jrunner, xebuild etc get
updated for corona 4G). Save your original backup for fix this situation later
GETTING THE CPUKEY – (RUNNING XELL)
Note: The following commands must be issued on a CMD window.
1.- Do a safety full dump of the corona dashboard area, save this file just in case the
things go wrong. The parameter “letter” is the letter that windows assigned to your SD
adapter.
C:\sdtools\sdreader letter fulldump1.bin C00
C:\sdtools\sdreader letter fulldump2.bin C00
The sdreader tool will give you MD5 check for the dumps, make sure the MD5 is same
on both dumps before continue
If you for any reason want to restore your nand at the original state you can do with this
command: sdwriter letter fulldump1.bin c00
2.- Do a dump of 16MB, this dump will serve only for generate XELL, due to current
tools require to have spare data you need to add a parameter “ecc”
C:\sdtools\sdreader letter dump1.bin 400 ecc
C:\sdtools\sdreader letter dump2.bin 400 ecc
Again, make sure both MD5 match before continue.
3- Open Jrunner or AutoGG or your favorite and use the dump1.bin to generate your
xell image:
a) Ex.: Jrunner: Open program, on the field source file choose
c:\sdtools\dump1.bin.
b) Click on Create ECC.
c) On the log box check where the image_00000.ecc is located
4.- Copy the file to the sdtools folder and execute the following command:
C:\sdtools\sdwriter letter image_0000000.ecc 50 ecc
If you see errors make sure your SD card adapter does not have the Write
Protection tab set to lock
5- Do a SAFE REMOVAL of the drive inside windows (or eject if your sd reader is
internal) .
6- Now you need disconnect the U1D1 port from the Nand and the Ground wire to the
crystal in order to boot xell.
7- Install the Glitch device as if it was a CORONA 16MB board, using your favorite
glitcher, dont forget to plug the network cable as WILL NOT GIVE VIDEO OUTPUT,
after the glitch boot you need to wait around 20 seconds more to be able to establish
network session.
8- On Jrunner use the feature of scan ip range to get your CPU KEY or if you know the
IP address (looking at the router) you can type it direct
CREATING AND SAVING THE RGH2 IMAGE:
1.- On this stage we will create a nand based only on the CPU KEY, the kv.bin from our
console (and the fcrt if you have it) and any donor smc.bin and smc_config.bin.
(included on the zip with this guide). Take note the only file specific of your console is
the kv.bin. Here is how to extract that file.
a) Open Jrunner, type your CPU KEY on the box and open the file
c:\sdtools\dump1.bin as Source File.
b) Click on menu Tools >> Extract Files.
c) Enter on the folder that jrunner extracted your files and copy the kv_enc.bin on
the folder Jrunner(install directory)\xeBuild\data. After that re-name the file
to only kv.bin. (if you have the fcrt file put it too)
d) Insert the donor Smc.bin, smc_config.bin on the same folder as previous
step.
e) Take note of the largest LDV shown (main screen of Jrunner, NAND_INFO
guide).
f) Restart J-runner and type your CPU again, then If you dont have the fcrt file
Enable nofcrt patch (XeBuild Patches menu). Then on the right options
choose the version of dashboard to create (ex.:15574) and set the hack type to
RGH2.
g) Now go to Advanced >> Create an image without nanddump.bin. If all goes
fine it will ask you to type your LDV, use the one you take note earlier. After that
it will ask to choose the board type, choose Corona.
2- Verify the J-runner log screen for any strange error. It is normal if you choose the
nofcrt to see the following error. If you only see the following error you can continue:
“xeBuild v1.04.515
---------------------------------------------------------------
building glitch2 image
***** ERROR: fcrt.bin not found, keyvault has this file flagged as required but it's
being skipped *****
---------------------------------------------------------------“
3- Now check where the updflash.bin image was saved and copy it to the sdtools
folder. For this step you will need reconnect the sd adapter to your U1D1 port on the
xbox and also put the ground wire on the crystal. Once connected to the PC run the
following command:
C:\sdtools\sdwriter letter updflash.bin 3dc ecc
A warning will appear due to filesize, just type “Y” (for yes) to continue.
4.- It is recommended to do a verify dump here and check the md5 shown on the write
command above match, the verify dump can be made with this: (note NO ecc
parameter is used on the following command)
C:\sdtools\sdreader letter verify.bin 3dc
The md5 should match with the one shown at write.
5.- Now we need to patch the fat entries (anchor block). For this you will need to open
the detailed xebuild log (usually stored on the same place as the updflash.bin) it is
called something like updflash(xxxxxxxxx).bin.log. Open it and look for the following
entry:
“adding as secdata.bin at raw offset 0xec0000 len 0x00000400 (end
0x00ec0400)”
Please note the address shown on the above example (0xec0000) could be different
on your log, you need to take note of that address as you will need it for next step
6- Now we need edit the fat entry, we need to Run the following command. The
secdataaddress is the one you take note on previoius step
C:\sdtools\sdfatedit letter secdataaddress
7- If no errors shown then you can now do a SAFE REMOVAL of the drive letter that
windows assigned. Then remove the wiring on U1D1 and the ground wire on the
crystal and go try boot the console.
8.- If you see it booting. Congratulations you have now your Corona 4G hacked !!
If you see any problem like christmas tree lights or red light then possibly you did
wrong on one of the steps (most likely the RGH2 creation step). Remember you can
always revert to original state (read the top of the guide) and start again.
Many Many Many thanks to c0z for the guidance on this. Many thanks to maximus
team for the sdreader, sdwriter and sdfatedit tools. And Many Many Many and Many
thanks to Edson Dario for his time dedicated to this tutorial and to the tests. And lastly
but not the least, Many thanks to the guys on dayton360mods forum for all the
exchange of ideas. We all did this for pure love to the scene.
Juggahax0r at Dayton360MoDs, Team Squirt, Zhangjiqi007, Zhaojun297,
Glitch360Team, Edson Dario, carranzafp, collions, Sileandro, nice69,c0z(joebloma)

weige9475

我只会认字母。。。。。。

soniceasy

rgh 2.0的 不是3.0