Jump to content
RealModScene
snyghalt

FSD Won't update

Recommended Posts

Hi there, I'm new here.

I bought a RGH console and I'm a bit lost in it.

 

I'm a PC user and I ussualy don't have problems with techy stuff, but this new RGH Xbox is still a bit confussing for me.

 

The first problem I'd like to solve is that I can't uodate FSD 3 (think I have rev. 058 or somthing like that)

 

I checked the option to "enable update notifications on startup" and I never get the option to do so upon startup.

When I try to do it manually I allways receive the message "your FSD is up to date" (even dough I know it is not)

 

Can my console have any setting to keep this updates blocked ?  Where should I look for ?

 

I read a few tutorials to update manually ... but I also discovered that my console won't start usung the eject button to get my CPU key.

 

What could be wrong in this case ?

 

 

If I need to give more info please let me know and I will search for it.

Thanks to everyone for any help yo can give me.

Share this post


Link to post
Share on other sites

what dashboard are you on, (stock) and what happens when you press eject. does it power up but just not display on your TV via HDMI ?

 

What kind of motherboard is it. 

 

Do you know how to use FTP.?

 

Do you have a copy of your nand and cpu key from where you bought it. 

 

Do you know how to get to "dashlaunch" 

Share this post


Link to post
Share on other sites

Man, you are FAST !

I'm not at home now, but I will check my dash version as soon as  I get there.

How can I check what kind of motherboard do I have ? (without opening my console) by serial #  ?

I do FTP with no problem.

I don't have  NAND nor CPU KEY numbers, sorry.  Can I get them somehow ?

 

Thanx

Share this post


Link to post
Share on other sites

you can check what kind of board it is looking at the power options on the back of it. 

 

 

Posted Image

 

What happens when you press "eject" does it power on, I've never come across a machine that would not power on with "eject" (not a working one any way)

 

You could also try "simple nand flasher" made by Swizzy if all else fails ;)

Share this post


Link to post
Share on other sites

You most likely have an old version of XeLL in your nand, and the reason for not updating F3 is because the newer versions are all "Beta", so you have to enable that option in order to update that part...

 

Judging by you having rev 0.58 i'd say you've probably got and old dashboard aswell, so i would recommend updating the entire console, you can read a tutorial i've written here: http://xebuildtut.xeupd.com or the one jpizzle wrote for xebuild 1.08 (easier): http://www.realmodscene.com/index.php?/topic/2205-xebuild-108-update-tutorial/

 

I do however recommend that you before doing anything else dump your console using Simple 360 NAND Flasher, then store the dump made from that in a safe place... 

  • Like 1

Share this post


Link to post
Share on other sites

ah, forgot about that "beta" option, and defo "store you nand" and RAR it, then store it in about 3 different places, one on site one off site and one at your friends place..lol ;)

 

@ Swizzy, the really old one's not power on with eject, must have been way before my time...lol

Share this post


Link to post
Share on other sites

ah, forgot about that "beta" option, and defo "store you nand" and RAR it, then store it in about 3 different places, one on site one off site and one at your friends place..lol ;)

 

@ Swizzy, the really old one's not power on with eject, must have been way before my time...lol

Corona don't power on when you press eject after a power cycle, however... once you've started with power once it'll accept eject as a valid startup reason (dunno why) other then that any xell version older then XeLL-Reloaded v0.992 don't have Corona video support, there is however one that was unofficial that had HDMI support for coronas ;)

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the heads up on that, would seem I'm a little behind with the "coronas" and not the other way round, I think we talked about one the other day when the guy was trying to update it. 

 

You know using your simple nand flasher for Coronas and you said that you need the crc32 file, where do you get this from, I was just having another read of the thread and see that he took a chance when he created his new nand in GUI xe build, and then you wrote this "+ to flash you need to add a crc32 as well (matching the file you want to write)" I know he flashed it using the -f by JP rather than back via the USB flasher. just wondering about this that's all, it's good to keep up (well try...lol)

 

@ OP, sorry not a hijack of your thread, just good to learn about these. 

 

I also see that there's a XeLL-Reloaded v0.993 with Corona Video support released by your good self... ;)

Share this post


Link to post
Share on other sites

Thanks for the heads up on that, would seem I'm a little behind with the "coronas" and not the other way round, I think we talked about one the other day when the guy was trying to update it. 

 

You know using your simple nand flasher for Coronas and you said that you need the crc32 file, where do you get this from, I was just having another read of the thread and see that he took a chance when he created his new nand in GUI xe build, and then you wrote this "+ to flash you need to add a crc32 as well (matching the file you want to write)" I know he flashed it using the -f by JP rather than back via the USB flasher. just wondering about this that's all, it's good to keep up (well try...lol)

 

@ OP, sorry not a hijack of your thread, just good to learn about these. 

 

I also see that there's a XeLL-Reloaded v0.993 with Corona Video support released by your good self... ;)

 

If you use the automatic mode (the cmd file) you need to generate a CRC32 hash of the updflash.bin and put this in a text file named "updflash.crc32" however, if you use the manual mode ( press A or B ) you don't need this file (it's purely for safety, if you transfer your nand over network it may end up beeing mangled... having a CRC32 requirement in order for the automode to work adds a small layer of protection against potential bricks)

 

And yes, i do make alot of tools/fixes, i didn't make XeLL-Reloaded v0.993 myself, but i had a big part in it ;)

  • Like 1

Share this post


Link to post
Share on other sites

ah a bit like an MD5 then....... what tool do you use to generate that CRC32 of the updflash.bin... good to learn so thanks for explaining, oh and thanks for all your hard work ;)

Share this post


Link to post
Share on other sites

ah a bit like an MD5 then....... what tool do you use to generate that CRC32 of the updflash.bin... good to learn so thanks for explaining, oh and thanks for all your hard work ;)

http://lmgtfy.com/?q=crc32+windows or if you're using macintosh: http://lmgtfy.com/?q=crc32+osx or if you're using linux: http://lmgtfy.com/?q=crc32+linux

 

one of the above 3 links should help, CRC32 is VERY common, infact, you can even use any SFV tool... it also generate CRC32... any of 'em should be a-ok

 

** edit: **

I did have a tool made entirely in C specifically for this while i was adding the crc32 stuff... it was nothing special, just a random crc32 implementation, after a little tinkering i was told where the fault was (i had taken this code as-is and just put it in the 360 code... problem with that is that the crc32 implementation is different from "big-endian" which the 360 has, compared to the "little-endian" which most computers use (windows always use little endian i think)

 

The difference between big and little endian is nothing you'll need to worry about unless you are going to start developing stuff on your own or create patches or so for consoles... but, if you do want to read about it, here's a link: http://en.wikipedia.org/wiki/Endianness

  • Like 1

Share this post


Link to post
Share on other sites

I´d try to give you all the data ... but please take it easy on me: I´M THE NEW GUY IN THE BLOCK "nand, XeLL, CRC32, Simple 360 NANAD Flasher" and such stuff are not easy to understand for me.

 

The data I´ve collected so far :

 

I think I have a Corona ... but can´t tell for sure which one is it, since it says 9.6A on the back

I´m running stock dasboard 2.0.16202.0

FSD is version 3.0 Rev58

When I turn the console on by pressing eject : the DVD tray comes out and the green led on the power button turns on... then I receive a warning message on the TV : "MODE NOT SUPPORTED - This resolution is not supported on this TV. Please change the resolution" It´s a standard  Samsung LED 46" 1080p never had any issue with it.

There´s no way I can get my CPU Key or Nand copy.

 

thanx !

Share this post


Link to post
Share on other sites

I´d try to give you all the data ... but please take it easy on me: I´M THE NEW GUY IN THE BLOCK "nand, XeLL, CRC32, Simple 360 NANAD Flasher" and such stuff are not easy to understand for me.

 

The data I´ve collected so far :

 

I think I have a Corona ... but can´t tell for sure which one is it, since it says 9.6A on the back

I´m running stock dasboard 2.0.16202.0

FSD is version 3.0 Rev58

When I turn the console on by pressing eject : the DVD tray comes out and the green led on the power button turns on... then I receive a warning message on the TV : "MODE NOT SUPPORTED - This resolution is not supported on this TV. Please change the resolution" It´s a standard  Samsung LED 46" 1080p never had any issue with it.

There´s no way I can get my CPU Key or Nand copy.

 

thanx !

Put this on a USB Memory stick: http://www.homebrew-connection.org/files/xbox/nand_flasher/dl_Simple_360_NAND_Flasher_v1.3_BETA.rar and run it on your xbox (unrar it first) you'll probably need to go to the filemanager to launch it (just select "default.xex" and press A and it should start) once you've done that, follow the on-screen instructions, if all goes well you'll have both your nand dump and cpukey on your usb memory...

 

If that doesn't work, let me know and i'll make a package for you to run a newer version of XeLL that should work...

  • Like 1

Share this post


Link to post
Share on other sites

Done!

I´ve got my CPU Key and the file flashdmp.bin in a USB Memory Stick.

Did two copies and kept them in safe places

 

During the rawdump process I´ve got a warning message "block 0x2f5 seems bad, status 0x00000304"

But it ended without any other message and my NAND copy in the MemStick.

 

thanx everyone

 

Freshman awaiting orders  hehe   :baby:

Share this post


Link to post
Share on other sites

That's a quite common thing to get... bad blocks... however, that status code isn't one of the standard ones... this one means: 

ECC Error Detected & Interrupt (not sure exactly what that interrupt means... but... it's probably safe to treat it like a badblock, which you don't have to do on your own (xebuild auto remap bad blocks for you...)

 

Next you want to update your consoles dashboard, follow one of the links i gave you earlier, etheir to the network guide, which is quite easy to follow, or use my manual guide [should also be quite easy to follow, but have more steps in it)

Share this post


Link to post
Share on other sites

Back here reporting ...

 

I now have my NAND and my CPU KEY safely stored.

 

I´ve followed the step by step instructions found here http://www.realmodscene.com/index.php?/topic/2205-xebuild-108-update-tutorial/

 

No trouble at all. But I don´t see my FSD 3 updated to any newer version. I´m still running version 0.58  Should´nt  it be updated ?

What I do have now updated is my stock dashboard running 2.0.16537.0  This is the last one, isn´t it ?

 

as usual, thanx for your help !

Share this post


Link to post
Share on other sites

That's the part that guide is for, in order to update F3 you need to change settings so that it looks for beta updates, then you can update to the latest version...

 

Or you can download the latest version and manually replace the files on the console =)

Share this post


Link to post
Share on other sites

That's the part that guide is for, in order to update F3 you need to change settings so that it looks for beta updates, then you can update to the latest version...

 

Or you can download the latest version and manually replace the files on the console =)

Thanx Swizzy, that´s how we started all this. I can´t update my FSD even checking the beta updates option. Seems something is not quite right in my installation. Looks like somewhere in my configuration I have updates banned (some firewall option or something like)

Share this post


Link to post
Share on other sites

run FSD (or xex menu) and then FTP in and update dash launch and copy of FSD and then set the default xex in dash launch to point to your new FSD. 

 

HERE 

Share this post


Link to post
Share on other sites

1. Do you have an account on JQE360?  If not get one......

2. Link you account to your console.....

What for ?

Does this have anything to do to my FSD update problem  ?

 

Like I said in the beginning I´m trying to learn and understand here.

Share this post


Link to post
Share on other sites

follow my post.....dead easy...your nearly there ;)

Just to be sure ...

 

on the left are the uncompressed contents of the TeamFSD.Freestyle3.0.775 file

on the right you can see the contents of the freestyle folder in my Xbox accesed trough FTP.

 

Should I OVERWRITE the contents in my XBOX with the ones I´ve downloaded ?

Do I have to delete any file from my previous XBOX  FSD installation ?

For sure I will keep a Backup copy of my full Freestyle installation ... But how will I be able to restore it if anything goes wrong ? Cuz I figure my XBOX won´t boot If I mess up ...

 

Posted Image

 

 THANX !

Share this post


Link to post
Share on other sites

your worrying too much ;) everything is cool now, you done the hard work. 

 

On the right hand side, back out a folder, and then create one called FSD1, then copy the new fsd contents over to the folder you just created. (maybe open a bottle of wine at this point your nearly there......)

 

have you also got dashlaunch installed... ;)

 

Cuz I figure my XBOX won´t boot If I mess up ...

 

 

wrong...it will, you can't mess it up...well you can if you wanna, but it's hard work... ;)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...