XeBuild under Linux?

A

anjelika

Full Member
Dec 7, 2011
28
0
Hey,
Anyone managed to run xebuild under linux command line to generate new images?
I am willing to create a web app for my clients to let them automatically generate new glitch images by entering their console's serial number.
So far I can do this on Windows but want to use a linux box for this.
Thanks.
 
Nintendo

Nintendo

VIP Member
Sep 5, 2014
605
33
Spain
anjelika said:
Hey,
Anyone managed to run xebuild under linux command line to generate new images?
I am willing to create a web app for my clients to let them automatically generate new glitch images by entering their console's serial number.
So far I can do this on Windows but want to use a linux box for this.
Thanks.
Click to expand...
You need the CPU Key to create the glitch image, not the Serial number.

As far as i know, you can't use XeBuild running Linux, maybe using Wine?
 
A

anjelika

Full Member
Dec 7, 2011
28
0
I know that I need the CPU Key, but knowing the Serial number is all I need. Usually is easier for clients to obtain that (it is written on the back of the console) than the CPU Key. J-runner is creating a folder with the console's serial number and inside this the CPU Key file is found. Wine is not an option as I only run linux in command line more mode. Wine won't allow me to automate the whole process.
 
Nintendo

Nintendo

VIP Member
Sep 5, 2014
605
33
Spain
anjelika said:
I know that I need the CPU Key, but knowing the Serial number is all I need. Usually is easier for clients to obtain that (it is written on the back of the console) than the CPU Key. J-runner is creating a folder with the console's serial number and inside this the CPU Key file is found. Wine is not an option as I only run linux in command line more mode. Wine won't allow me to automate the whole process.
Click to expand...
I see, in my opinion using windows will be fine as XeBuild doesn't work with Linux, maybe you can figure out an easier method.

Good Luck.
 
Last edited:
G

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
If I remember correctly, Xebuild is written in python, which will work in linux. You just have to find the command line version for windows, and go from there. You may have to make some changes to the code to get to work properly in Linux though.
 
A

anjelika

Full Member
Dec 7, 2011
28
0
That's what I was thinking. I also remember that this was using python at least in the early stages. The problem is that I can only find .exe files for the latest versions.
I know that I can use Windows, I am using it at this time but wanted to host a website where the client could enter its console's serial number and a updflash.bin will be downloaded without my interaction. That's the whole idea, could sound lazy but I call it automation :)
 
Nintendo

Nintendo

VIP Member
Sep 5, 2014
605
33
Spain
anjelika said:
That's what I was thinking. I also remember that this was using python at least in the early stages. The problem is that I can only find .exe files for the latest versions.
I know that I can use Windows, I am using it at this time but wanted to host a website where the client could enter its console's serial number and a updflash.bin will be downloaded without my interaction. That's the whole idea, could sound lazy but I call it automation :)
Click to expand...

It's a good idea, you can host the website using Windows, it's going to be easier than modifying some old py code.
 
A

anjelika

Full Member
Dec 7, 2011
28
0
Yeah but I don't want to run a windows machine just for that. I have a raspberry pi which is great for the project but only runs linux. Beside, website hosting in Windows is crap, Apache rullz;)
 
S

SqWaw

Noob Account
Nov 8, 2004
1
0
NY
Seems you can just use wine on linux. Haven't tested actually generating anything, but looks like it'll work.

[email protected]:~/Documents/xbox360/xeBuild_1.12$ wine xeBuild.exe
---------------------------------------------------------------
xeBuild v1.12.659
---------------------------------------------------------------
ERROR: invalid command line, you need to specify parameters!
---------------------------------------------------------------
Usage :
xeBuild [mode] -t <type> [<switch> [<switch>...]] <out.bin>


Example :
xeBuild -t retail -c trinity -d files -b 0102...0f -p 0102...0f out.bin


Switches:
-t <type>: retail, jtag, glitch, glitch2, glitch2m, devkit (defaults to retail)
-p <key> : 32 character CPU hex key (override, can be elsewhere)
-b <key> : 32 character 1BL hex key (override, can be elsewhere)
-c <con> : console type
-d <dir> : per build files directory
-f <dir> : use different data dir and file lists
-s <file>: outputs SHA-1 of final image to <file>, if <file> is not provided an auto generated name is used
-o <opt> : set xeBuild options
-a <name>: append patches
-i <ext> : adds _<ext> into firmware ini and patches file names
-r <ext> : adds _<ext> into ini bl section name and patches file names
-v : shows more info during build process
-noenter : suppresses prompt for enter key when finished
-? : shows this info


legend:
[mode] : build, client, update - defaults to build if not present
<con> = xenon, zephyr, falcon, jasper, jaspersb, jasper256,
jasper512, jasperbb, jasperbigffs, trinity, corona, corona4g
<dir> = path, absolute or relative, to a directory - do not terminate with \
<key> = 128 bit key in hexadecimal representation
<name> = name.bin contents will be appended to hv/kernel patches


<out.bin> = optional, overrides auto built output image name
<ext> = using this option would cause the builder to look for _glitch_<ext>.ini instead of _glitch.ini
and patches_jasper_<ext>.bin instead of patches_jasper.bin
<opt> various options can be specified on the command line, see perbox sample ini for descriptions
listed below, ALL are available to all image types
the others can be specified but are only used for that specific image type
ALL = nomobile noremap noecdremap nosecurity nosusecurity nandmu smcnocheck cputemp=
ALL = gputemp= edramtemp= overcputemp= overgputemp= overedramtemp= cpufan= gpufan=
ALL = avregion= gameregion= dvdregion= macid= cfldv=
JTAG/GLITCH = smcnoeject smcnoblink cygnos demon xellbutton= xellbutton2= dvdkey=
JTAG only = nodvd olddvd dualboot=
GLITCH only = patchsmc
options noted above with an = are expected to be followed with a value
specifying one of the options without an = is the same as setting TRUE in the ini
any value assigned to it will be ignored.
note that command line options take precedence over any values set in perbox ini
and that only values preceded with 0x will be interpreted as hex, MAC is the only exception
example: -o macid=00:22:48:F1:01:02;gameregion=0x00FF;nomobile
example: -o macid=00:22:48:F1:01:02 -o gameregion=0x00FF -o nomobile
example: -o macid=002248F10102 -o gameregion=255 -o nomobile
---------------------------------------------------------------


press <enter> to quit...
 
  • Like
Reactions: anjelika
G

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
anjelika said:
Yeah but I don't want to run a windows machine just for that. I have a raspberry pi which is great for the project but only runs linux. Beside, website hosting in Windows is crap, Apache rullz
Click to expand...
Apache has a windows version also. so web hosting is about the same in windows, if you use apache. Now the built in windows web server is crap, I would agree there.

SqWaw said:
Seems you can just use wine on linux. Haven't tested actually generating anything, but looks like it'll work.

[email protected]:~/Documents/xbox360/xeBuild_1.12$ wine xeBuild.exe
---------------------------------------------------------------
xeBuild v1.12.659
---------------------------------------------------------------
ERROR: invalid command line, you need to specify parameters!
---------------------------------------------------------------
Usage :
xeBuild [mode] -t <type> [<switch> [<switch>...]] <out.bin>


Example :
xeBuild -t retail -c trinity -d files -b 0102...0f -p 0102...0f out.bin


Switches:
-t <type>: retail, jtag, glitch, glitch2, glitch2m, devkit (defaults to retail)
-p <key> : 32 character CPU hex key (override, can be elsewhere)
-b <key> : 32 character 1BL hex key (override, can be elsewhere)
-c <con> : console type
-d <dir> : per build files directory
-f <dir> : use different data dir and file lists
-s <file>: outputs SHA-1 of final image to <file>, if <file> is not provided an auto generated name is used
-o <opt> : set xeBuild options
-a <name>: append patches
-i <ext> : adds _<ext> into firmware ini and patches file names
-r <ext> : adds _<ext> into ini bl section name and patches file names
-v : shows more info during build process
-noenter : suppresses prompt for enter key when finished
-? : shows this info


legend:
[mode] : build, client, update - defaults to build if not present
<con> = xenon, zephyr, falcon, jasper, jaspersb, jasper256,
jasper512, jasperbb, jasperbigffs, trinity, corona, corona4g
<dir> = path, absolute or relative, to a directory - do not terminate with \
<key> = 128 bit key in hexadecimal representation
<name> = name.bin contents will be appended to hv/kernel patches


<out.bin> = optional, overrides auto built output image name
<ext> = using this option would cause the builder to look for _glitch_<ext>.ini instead of _glitch.ini
and patches_jasper_<ext>.bin instead of patches_jasper.bin
<opt> various options can be specified on the command line, see perbox sample ini for descriptions
listed below, ALL are available to all image types
the others can be specified but are only used for that specific image type
ALL = nomobile noremap noecdremap nosecurity nosusecurity nandmu smcnocheck cputemp=
ALL = gputemp= edramtemp= overcputemp= overgputemp= overedramtemp= cpufan= gpufan=
ALL = avregion= gameregion= dvdregion= macid= cfldv=
JTAG/GLITCH = smcnoeject smcnoblink cygnos demon xellbutton= xellbutton2= dvdkey=
JTAG only = nodvd olddvd dualboot=
GLITCH only = patchsmc
options noted above with an = are expected to be followed with a value
specifying one of the options without an = is the same as setting TRUE in the ini
any value assigned to it will be ignored.
note that command line options take precedence over any values set in perbox ini
and that only values preceded with 0x will be interpreted as hex, MAC is the only exception
example: -o macid=00:22:48:F1:01:02;gameregion=0x00FF;nomobile
example: -o macid=00:22:48:F1:01:02 -o gameregion=0x00FF -o nomobile
example: -o macid=002248F10102 -o gameregion=255 -o nomobile
---------------------------------------------------------------


press <enter> to quit...
Click to expand...
I dont know if I would trust wine with this. It is iffy at best.
 
Last edited:
  • Like
Reactions: anjelika
You must log in or register to reply here.