fbBuild 0.11 - New freeboot and new Dashlaunch 2.06

[cory1492]

so basically you are saying to install dashlaunch patch? I don't really get how to do what you describe... ie make the machine boot with the 12611 image but load another dashlaunch.xex

if you think it can help you, I can gratefully send you my working 9199.image and keys etc for my console, along with the image I have built so you can check it yourself....

I don't know if many have noticed, but fbBuild can build images with dash launch in them already so you don't have to run the installer to use it - all that is required is taking a compatible launch.xex and lhelper.xex and putting them with the rest of the firmware files (like dash.xex). Since your problem is E71, dash can't load, try loading something else instead of dash.xex like freestyle or xexmenu via dash launch ini file's default option.

If you want to PM me a link, I do have tools for analyzing dumps' LBA closely - what would be most useful is working, and one you've written got E71 and then dumped (I presume xellous works even on E71 images to get a dump of 'after'?) The other stuff like key I can get from the images themselves.

[thesonandheir]

Jasper 16mb, CB 6723, SB 2.3

Created a few images from orig/XBR/FB 0.32 and all fail at splash screen. It just hangs there displaying the XBOX 360 logo.

Used fbBuild, EasyFB and BestPigs FBToolbox.

Can boot Xellous though so I can recover always.

Bad block in NAND @ 154, Xellous seems to remap to 3E0. Tried manually remapping to 3FF with Nandpro, still the same hang at boot.


Hope somebody can help.

[axe971]

 I got it working. it took a while, since i had the e71 error a lot. However, to fix it i extracted the smc from xell. i tried a freeboot smc, and a xbr smc, those didnt work for me. so use an xell smc.

on the other hand, when i try to apply the 12611 update to get avatars, it says that my console is already up to date. any thoughts? i am not exactly sure how to tell if my avatars are up to date, but i can create them. im loading the update from a burned cd with the default.xex on it

[tataniko]

I just did 2 jaspers 16a (23010) image using fbbuild and both of them are working like a charm, I did not get your point!!

Exatly, you made a jasper16 image(1198010) with fbbuild, 
and flashed to 2 jaspers16a(23010), and working like a charm, that's the point!   

The correct flashconfig of image file is the point.
Why has freeboot0.32/XBR3a image file proper (23010) flashconfig. 

[cory1492]

Wait, where are you getting this flash config from? If it's coming from a PC tool, it's based on the file and not the actual system flash config value and really doesn't reflect a real flash config value - to change what that sees, at 0x70 (of block 0 in the full flash image) change it from 0x00 00 00 00 to 0x00 01 00 00 and fix the ecc.

[tataniko]

Thanks, I will try, but imposibble mission without MODFREAKz ecc repair tools  

Update: changed at 0x70 to 0x00 01 without fix the ecc, flashconfig(1198010) not changed.

[Harbinger076]

ZerOneX, any of your jaspers with bad blocks?

my personal jasper has 1 bad block at block 65  xellous remaped it and all is nice..

[artik]

ZerOneX, any of your jaspers with bad blocks?

my personal jasper has 1 bad block at block 65  xellous remaped it and all is nice..

16Mo nand ? If yes, which procedure did you do ?

[Harbinger076]

ZerOneX, any of your jaspers with bad blocks?

my personal jasper has 1 bad block at block 65  xellous remaped it and all is nice..

16Mo nand ? If yes, which procedure did you do ?

sorry no.. 256 mb nand..

[andrez]

I just wanted to point out that this problem (E71 after the logo animation) only seems to affect those with a jaspers16-23010 and a bad block on dash.xex (range h72 - h1EB / fbbuild image). If you don't have a bb in that position it doesn't matter what revision you are flashing.

[terzi]

Jasper 16mb, CB 6723, SB 2.3

Created a few images from orig/XBR/FB 0.32 and all fail at splash screen. It just hangs there displaying the XBOX 360 logo.

Exactly same.
Jasper 16a and CB is 6723.
Southbrigde version is 2.3
Bad block at 27D.

[keropi]

so basically you are saying to install dashlaunch patch? I don't really get how to do what you describe... ie make the machine boot with the 12611 image but load another dashlaunch.xex

if you think it can help you, I can gratefully send you my working 9199.image and keys etc for my console, along with the image I have built so you can check it yourself....

I don't know if many have noticed, but fbBuild can build images with dash launch in them already so you don't have to run the installer to use it - all that is required is taking a compatible launch.xex and lhelper.xex and putting them with the rest of the firmware files (like dash.xex). Since your problem is E71, dash can't load, try loading something else instead of dash.xex like freestyle or xexmenu via dash launch ini file's default option.

If you want to PM me a link, I do have tools for analyzing dumps' LBA closely - what would be most useful is working, and one you've written got E71 and then dumped (I presume xellous works even on E71 images to get a dump of 'after'?) The other stuff like key I can get from the images themselves.

it would be interesting to use as an experiment but it has no real use for me, as I never used dashlaunch nor I am interested in booting fsd/xexmenu instead... this appears to be a freeboot0.04 bug or something...
I can send you files to look, you want my build image and the dump after it gets written? luckilly xellous works after 

[tataniko]

How can we index/convert/rebuild/rehash an 1198010 image to 0023010? 

I mean, if have a proper 0023010 binary, then we can remap bad blocks by hand correctly.

[andrez]

Jasper 16mb, CB 6723, SB 2.3

Created a few images from orig/XBR/FB 0.32 and all fail at splash screen. It just hangs there displaying the XBOX 360 logo.

Exactly same.
Jasper 16a and CB is 6723.
Southbrigde version is 2.3
Bad block at 27D.

27D is xam.xex. If I'm getting this right, xam.xex loads and then it try to run dash.xex, if that is not possible you get E71. In your case xam doesn't work and you have a freeze without error. Everything seems to poin out that remapped bad blocks on these jaspers aren't read correctly with an fbbuilded image.

[pkmz]

Wish I had a jasper to to help check stuff but I only have my xenon. Sorry guys

[fryc88]

I've tried one more time to fix my e71 12611 dash, but no success.
I used flash360 to dump my working 9199, extracted and decrypted KV, SMC and SMC_config as it is in tutorial, put it to fb 0.1, made  updflash.bin and used xellous to flash it. But like before, first start is fine, then shutdown, took power cable off for couple minutes, turn back in console and e71 like before. I did try also to remap my 0148 bad sector to 3ff, 3fe, and moving 8 sectors from 148 to 3f8, with no success still... Got no other ideas what i'm doing wrong here :/

I did not try to use flash360 to flash my nand, but i think xellous is enough. Last time i've even erased whole nand, flashed fresh xell+xellous+kv, flash 12611 dash, and same prob....
I wanna get 12611 working, it's fresh looking and working pretty faster than 9199 for me. Any clues now?

[keropi]

OK, I did some more testing...

I build my 12611 image (updflash.bin) and grabbed the nand with xellous after writting said image. Naturally for my case xellous reports: " ! SFCX: Bad block found at 00000090 "

so here is nandcompare:




and 360 Flash Tool , with the bad block and filesystem:





why 090 gets (automatically via xellous) relocated to 3E0 At least my 3FD/3FE/3FF blocks are just fine, I did some manual writing there with nandpro...

[utar]

why 090 gets (automatically via xellous) relocated to 3E0 At least my 3FD/3FE/3FF blocks are just fine, I did some manual writing there with nandpro...

I believe that the flash controller remaps bad blocks by starting with the last block (3FF) and working backwards.  Xellous and Flash360 work by starting with the first block in the reserved area and working forwards.  It however makes no difference as the controller searches the whole area.

I do have one perhaps wacky suggestion.  Assuming the fbbuild takes all the files from the data directory (rather than just certain ones it searches for) and takes these in alphabetical order why don't you make a dummy file before dash.xex in the alphabet.  E.g. daaa.xex that way the dummy file will be in the area where you have the bad block.

[nokaktsawa]

Me too have a jasper 16 mb with a bad block @ 1AC address, and I have the same problem as many of you: xbox boots, displays spash screen and then freezes there before getting to dashboard. No E71 whatsoever, though.
Luckily, Xell works and I'm able to flash any updflash through it without using LPT port.

One odd thing I noticed: every time I try to build a new 12611 freeboot, the updflash files generated are always DIFFERENT, no matter what app I use to build them (Easy Freeboot, Jtag tool, FreeBoot toolbox maker ecc...). Of course using the very same source files.
Does this happen to you too? Have you tried to compare thei content?

[andrez]

I think that is normal. There is some random generated stuff involved with the encryption. If you extract the files they will be identical.