Some xLoader clarifications by the Noobz crew

It seems that many people were having problems with xLoader, the newly-released eLoader‘s sidekick. Not to worry though, the Noobz crew has given instructions to address most problems which plagued those who didn’t check the readme (bad!). Here’s all the clarifications directly from the official page.

Step-by-step instructions:

• Install xLoader, using either the auto-installer, or by following the instructions in the readme.txt file in the ZIP package.
• Install some homebrew – perhaps by using the Installotron, which you can run from Fanjita‘s baybeh”>eLoader (it doesn’t work well in xLoader).
• Use the PatchSFO tool to ensure that your homebrew is ready for xLoader (see below for instructions).
• Now browse to your PSP’s photo menu, and open the folder ‘xLoader 280’. If everything has worked, you will see 2 file icons, one a round blue circle, the other a ‘corrupt data’ icon. So long as your PSP hasn’t crashed at this point, then xLoader is now running.
• Alternatively, highlight the ‘xLoader 280’ folder and press START, to attempt a slideshow of the images in the folder. The PSP will complain that there are no pictures to show – this is OK, so long as the PSP hasn’t crashed, then xLoader is now running.
• Browse to the homebrew you want to load, in the PSP’s ‘GAME – Memory Stick‘ folder, and press X or O (depending on your PSP region) to start it.
• The screen should go white, and then some text about eLoader appears briefly, followed by the homebrew starting. If your PSP crashes, then the homebrew you’re trying to run is either not installed correctly, or it’s not compatible with xLoader.

Some general info:

• There’s plenty of useful and important information in the README file – click here to read it again (because of course you read it when you installed Kriek, right?).
• If you haven’t downloaded it already, you should grab the PatchSFO utility (see below). You can also install it via Installotron. If you run PatchSFO, then you’ll be able to at least attempt to run all your homebrew via xLoader. Without PatchSFO, the XMB won’t even try to start most homebrew.
• Sometimes you’ll find that the eLoader and xLoader TIFFs stop working. If that happens:
• Try running a disk checking tool on your memory stick. For Windows, you can use ‘chkdsk’, or the ‘Properties – Tools – Error Checking’ option that comes up if you right-click the memory-stick drive icon. On a Mac, you can try the ‘First Aid’ option of the Mac Disc Utility. This seems to fix about 95% of problems.
• Try reinstalling eLoader.
• Try starting with a different method – if you normally start with slideshow (using the START button, then try just opening the folder (with the X or O button) – and vice versa.
• eLoader will usually crash if you try to run it when xLoader is active. Just hold the power switch on your PSP for 5 seconds to reset it, then turn it back on again. This removes xLoader from memory.

Another thing to take notice in case you don’t know, Installatron is only able to use the first access point configuration. So if you’re not able to use Installatron properly, it would be wise to delete the rest of the access point configurations. We’re hoping that Fanjita can fix that so that there’s an access point selector, like in AFKIM or Links2. Until then though, you’ll have to make do with the workaround.

It seems that many people were having problems with xLoader, the newly-released eLoader‘s sidekick. Not to worry though, the Noobz crew has given instructions to address most problems which plagued those who didn’t check the readme (bad!). Here’s all the clarifications directly from the official page.

Step-by-step instructions:

• Install xLoader, using either the auto-installer, or by following the instructions in the readme.txt file in the ZIP package.
• Install some homebrew – perhaps by using the Installotron, which you can run from Fanjita‘s baybeh”>eLoader (it doesn’t work well in xLoader).
• Use the PatchSFO tool to ensure that your homebrew is ready for xLoader (see below for instructions).
• Now browse to your PSP’s photo menu, and open the folder ‘xLoader 280’. If everything has worked, you will see 2 file icons, one a round blue circle, the other a ‘corrupt data’ icon. So long as your PSP hasn’t crashed at this point, then xLoader is now running.
• Alternatively, highlight the ‘xLoader 280’ folder and press START, to attempt a slideshow of the images in the folder. The PSP will complain that there are no pictures to show – this is OK, so long as the PSP hasn’t crashed, then xLoader is now running.
• Browse to the homebrew you want to load, in the PSP’s ‘GAME – Memory Stick‘ folder, and press X or O (depending on your PSP region) to start it.
• The screen should go white, and then some text about eLoader appears briefly, followed by the homebrew starting. If your PSP crashes, then the homebrew you’re trying to run is either not installed correctly, or it’s not compatible with xLoader.

Some general info:

• There’s plenty of useful and important information in the README file – click here to read it again (because of course you read it when you installed Kriek, right?).
• If you haven’t downloaded it already, you should grab the PatchSFO utility (see below). You can also install it via Installotron. If you run PatchSFO, then you’ll be able to at least attempt to run all your homebrew via xLoader. Without PatchSFO, the XMB won’t even try to start most homebrew.
• Sometimes you’ll find that the eLoader and xLoader TIFFs stop working. If that happens:
• Try running a disk checking tool on your memory stick. For Windows, you can use ‘chkdsk’, or the ‘Properties – Tools – Error Checking’ option that comes up if you right-click the memory-stick drive icon. On a Mac, you can try the ‘First Aid’ option of the Mac Disc Utility. This seems to fix about 95% of problems.
• Try reinstalling eLoader.
• Try starting with a different method – if you normally start with slideshow (using the START button, then try just opening the folder (with the X or O button) – and vice versa.
• eLoader will usually crash if you try to run it when xLoader is active. Just hold the power switch on your PSP for 5 seconds to reset it, then turn it back on again. This removes xLoader from memory.

Another thing to take notice in case you don’t know, Installatron is only able to use the first access point configuration. So if you’re not able to use Installatron properly, it would be wise to delete the rest of the access point configurations. We’re hoping that Fanjita can fix that so that there’s an access point selector, like in AFKIM or Links2. Until then though, you’ll have to make do with the workaround.