Couldnt locate xell binary in nand. Aborting!

Xplorer4x4 · Post by **Xplorer4x4** » Wed Mar 14, 2012 7:20 am

I tried to update xell reloaded. I built xell using the git repository and everything built fine as far as I could tell. I grabbed the xell-gggggg.elf(since I have a Slim Trinity using the RGH) and renamed it to updxell.bin. I placed updxell.bin on my flash drive and booted in to Xell Reloaded but it kept giving me this error message over and over when it tried to find and elf to load:

!couldnt locate xell binary in nand. Aborting!
Trying dvd:/vmlinux...* update-xell binary found @ uda:updxell.bin ! Looking for xell binary in nand now.

tuxuser · Post by **tuxuser** » Wed Mar 14, 2012 9:22 am

Reading README helps sometimes...

Xplorer4x4 · Post by **Xplorer4x4** » Wed Mar 14, 2012 10:06 am

tuxuser wrote: Reading README helps sometimes...

I have read it many times, guess I should have referenced it again. Thanks.

I am confused though:

--Either your XeLL in NAND is too old or it's not a XeLL Reloaded binary

My build is from September 2011 and says XeLL Reloaded when I boot, is this really to old of a build?? When was the cut off? I don't suppose there is anyway to obtain a nand dump from my already RGHed console is there?

tuxuser · Post by **tuxuser** » Wed Mar 14, 2012 11:21 am

03-09-2011 build? yeah, thats too old.. it doesnt include the new xell offsets which are used by recent nandimages.

Xplorer4x4 · Post by **Xplorer4x4** » Wed Mar 14, 2012 11:43 am

So then the only option is to buy a Xecuter NAND-X & JTAG Connection Kit or is there a cheaper USB nand dump utility out there? I guess that even if there was a way to dump the nand as is with out a tool, a tool like that would be needed to reflash the nand? My chip is a Team-Xecuter Coolrunner.

Thanks for all the help tuxuser!

tuxuser · Post by **tuxuser** » Wed Mar 14, 2012 1:29 pm

Why make it so hard? Dump the Nand via Xell's Webinterface - build a new image - name the new image updflash.bin and flash it via XeLL.. or am I missing something?

Of course you dont have a recovery option then if something goes wrong..

Xplorer4x4 · Post by **Xplorer4x4** » Wed Mar 14, 2012 2:32 pm

tuxuser wrote: Why make it so hard?

That's exactly what I was asking! I googled to see if there was a way to dump the flash via xell but google didn't give any relevant results. I guess the only way to have a safe recovery option is buying a kit like the one mentioned? If the flash fails, am I still able to recover using a serial adapter?

I been trying to figure out how to build a the image. This was all I could find. It looks a bit out dated though. Is there a better tutorial to follow?

Also I was confused by this particular sentence:

If you are using XeLL-compile after 31. August 09 you could use the USB-Update feauture.

Does this not apply to XeLL Reloaded?

Thanks again Tux, I am truly grateful for your help, and I am anxious to learn!

tuxuser · Post by **tuxuser** » Wed Mar 14, 2012 7:36 pm

Xplorer4x4 wrote: I guess the only way to have a safe recovery option is buying a kit like the one mentioned?

Yep, a USB SPI Programmer is needed for that.

If the flash fails, am I still able to recover using a serial adapter?

NO

I been trying to figure out how to build a the image. This was all I could find. It looks a bit out dated though. Is there a better tutorial to follow?

It's still up-to-date for JTAG-consoles. http://free60.org/SMC_Hack#From_scratch or http://free60.org/SMC_Hack#Updating_a_hacked_image

If you are using XeLL-compile after 31. August 09 you could use the USB-Update feauture.
Does this not apply to XeLL Reloaded?

The date 31. August 2009 is only for original XeLL in XeLL-only images (not the *not to be discussed*-images)

Xplorer4x4 · Post by **Xplorer4x4** » Wed Mar 14, 2012 8:47 pm

tuxuser wrote:
If the flash fails, am I still able to recover using a serial adapter?
NO

Really? So basically there is no fail safe at all? What part specifically has to screw up to cause a brick?

It's still up-to-date for JTAG-consoles. http://free60.org/SMC_Hack#From_scratch or http://free60.org/SMC_Hack#Updating_a_hacked_image

The date 31. August 2009 is only for original XeLL in XeLL-only images (not the *not to be discussed*-images)

Not to be the grammar police but the double negative kind of confused me lol. Exactly what is it that is not to be discussed just so I know how to stay with in the rules.

Original XeLL?

Thanks for helping a n00b learn tux, with out people like you willing to tech people like me would never learn.

barnhilltrckn · Post by **barnhilltrckn** » Wed Mar 14, 2012 10:04 pm

Well rawflash v4 works pretty good so I doubt you will have issues unless you screw up building your image.

When it comes to recover incase of disaster flashing by lpt would be the cheapest method. If you have an old printer cable laying around cut it and take a multimeter to it to find out which wires are what on the side that hooks up to the pc. You can then use nandpro to read/write the nand from the pc. Dont let anyone tell you that you cant flash a slim by lpt because I have done it numerous times. Just do a quick google search and you can find plenty of diagrams.

Also just becuse the slim has 4gb internal memory does not mean its like the old phats with internal memory. Its a 16mb nand so treat it as such and you shouldnt have any problems.

Xplorer4x4 · Post by **Xplorer4x4** » Fri Mar 23, 2012 5:13 pm

Thanks guys, now in the wiki it says to use xell-1f.bin. Since I have a rgh shouldn't I use xell-gggggg not xell-1f.

LibXenon.org