Print

[Dicko316]

I can't get any of the programs, yours v0.5, v0.6, v0.7 or xebuild to work on my falcon, I keep getting E71 which i presume is because the patches are not right which it applies whilst building the hacked image.

It was actually one of my customers who discovered this when he tried to update today, I thought he must of been creating the image wrong so built it myself and emailed him it. He still had the same problem with the image I created. So I built an image for a falcon I have here and I get exactly the same thing.

v0.4 worked fine building an image for dash 13604. Which I have just reinstalled and works fine.

Anyone else having similar problems?

[Dicko316]

There are bad blocks in both nands of our falcons but they seem to be handled correctly.
I did however get an error 0x00000204 at 0xfe using rawflash3, I had a search on all the forums and google but found nothing.
I also got this same error re-flashing the 13604 dash back but it still works ok.

[steplay29]

hi just updated a jasper 512mb with the new version 0.7 and it worked a treat even for me lol.am going to to the kids two falcons v3 but when i run the progam beside option 5:it says a falcon with cb 5771,but my two falcons are 5770.just wondering is it ok to go ahead and flash this or to wait?

[Dicko316]

Couldnt re-edit my post sorry:

So finally got it sorted, used v0.7, dumped my nand on dash 13604 with flash360v1.0 it gave same error unable to read 0xfe error 204. I then used this image to build my dash 14699, flashed back with flash360v1.0 got no errors writing and it worked.
[chose to build without dashlaunch patches]

Having problems auto booting into FSD now from official hdd.
My ini looks like this
[QuickLaunchButtons]
Default = Hdd:\FSD22\Default.xex
 
[Settings]
nxemini = true  
pingpatch = true  
contpatch = true  
fatalfreeze = false
fatalreboot = true
dvdexitdash = false  
xblaexitdash = true  
nosysexit = false  
exchandler = true  
noupdater = true  
liveblock = true  
 
[Plugins]
plugin1 = Hdd:\swap.xex

It just boots to NXE and yes the path to FSD is right lol. Funny thing is if I use a USB stick and use USBMU:\FSD22\default.xex it works fine.

Edit:
Solved my problem, just removed the blank lines from the ini, lol weird!

This post has been edited by Dicko316: Dec 12 2011, 03:19 PM

[steveo1978]

QUOTE(Dicko316 @ Dec 12 2011, 05:58 AM)

There are bad blocks in both nands of our falcons but they seem to be handled correctly.
I did however get an error 0x00000204 at 0xfe using rawflash3, I had a search on all the forums and google but found nothing.
I also got this same error re-flashing the 13604 dash back but it still works ok.

Does it say something like "block 0xfe seems bad error 0x00000204" if so then consider your self lucky I get about 20 or more of those in rawflash but every thing is fine. I have not found a solid reason for those errors, but I will not worry about it until I find out if its actually a bad thing.

[Dicko316]

QUOTE(steveo1978 @ Dec 12 2011, 04:53 PM)

Does it say something like "block 0xfe seems bad error 0x00000204" if so then consider your self lucky I get about 20 or more of those in rawflash but every thing is fine. I have not found a solid reason for those errors, but I will not worry about it until I find out if its actually a bad thing.

After using flash360v1.0 to update to dash 14699 and then going back to 13604. Then using rawflashv3 to update again to dash 14699 that error has now gone!

[digipimp75]

worked great on my Jasper BB jtag, thanks!  

The only problem I had was adding avatar support after flashing the 14699 image.   I chose the option to block system updates, and tried a few diff usb drives, renamed the folder $$systemupdate, but nothing worked.    Finally I had to repatch and allow system updates, then apply the update, then patch it again.   Kind of annoying, but it worked.

[steveo1978]

QUOTE(digipimp75 @ Dec 12 2011, 12:53 PM)

worked great on my Jasper BB jtag, thanks!  

The only problem I had was adding avatar support after flashing the 14699 image.   I chose the option to block system updates, and tried a few diff usb drives, renamed the folder $$systemupdate, but nothing worked.    Finally I had to repatch and allow system updates, then apply the update, then patch it again.   Kind of annoying, but it worked.

with mine I had to name the update folder $$ystemupdate to get it to work. New dash is not that great on a hacked 360 since most of the stuff I would use requires Xbox Live.

[Rogero]

QUOTE(steplay29 @ Dec 12 2011, 02:39 PM)

hi just updated a jasper 512mb with the new version 0.7 and it worked a treat even for me lol.am going to to the kids two falcons v3 but when i run the progam beside option 5:it says a falcon with cb 5771,but my two falcons are 5770.just wondering is it ok to go ahead and flash this or to wait?

hello, just ignore the [CB5771] it was meant only for RGH since before "Multi Builder" this used to be "Easy ggBuilder" for RGH only  so go ahead and flash your Jtag falcons with CB_5770, it will work fine.
Anyway I just fixed the CB labels for next release

QUOTE(steveo1978 @ Dec 12 2011, 06:53 PM)

Does it say something like "block 0xfe seems bad error 0x00000204" if so then consider your self lucky I get about 20 or more of those in rawflash but every thing is fine. I have not found a solid reason for those errors, but I will not worry about it until I find out if its actually a bad thing.

"block 0xfe seems bad error 0x00000204" --> this error is issued from RawFlash when it finds an empty block while flashing, it's more then a warning then a real error and the meant block is actually fine and not bad, so don't worry at all about the "204" error

QUOTE(Dicko316 @ Dec 12 2011, 07:00 PM)

After using flash360v1.0 to update to dash 14699 and then going back to 13604.

using "Flash360" is much more recommended to dump/flash the nand, it seems to handle the bad or empty blocks better then "Rawflash"

QUOTE

Then using rawflashv3 to update again to dash 14699 that error has now gone!

yes, this is logical, because "Rawflash v3" seems also to use differential flash method, the blocks that caused the error "204" were marked as empty/zerod "FF" then the corresponding blocks from the image being flashed are also empty, so "Rawflash v3" will skip them on your second flash attempt and you won't see the error "204" (which should be only a warning)

[steveo1978]

well I guess I am gonna stop using rawflash.

Atleast I know now why it was throwing those errors up.

[guerriero di pace]

QUOTE(steveo1978 @ Dec 12 2011, 08:22 PM)

well I guess I am gonna stop using rawflash.

Atleast I know now why it was throwing those errors up.

is out Rawflash v4
changelog is interesting...correct bug with BB nand

[steveo1978]

Yeah I might give rawflash v4 a try right now and see how it goes. will also give me a chance to test out multibuilder v0.7

Rogero you want me to just change this threads title to "360 Multi Builder *support*" or something like that?

[Rogero]

QUOTE(steveo1978 @ Dec 12 2011, 11:17 PM)

Yeah I might give rawflash v4 a try right now and see how it goes. will also give me a chance to test out multibuilder v0.7

Rogero you want me to just change this threads title to "360 Multi Builder *support*" or something like that?

as you wish

[*Sem*]

Can someone please help me, I stuck with multybuilder on win xp 32, after I chouse the mb version the programm say it will make a ecc, and when nothing happens, "push any key to quit" again.
On win 7 64 the programm works fine!

[Rogero]

360_Multi_Builder_v0.8 on 22/02/2012
----------------------------------------------------------------
- Removed the CB Labels on Main Menu to eliminate any RGH/Jtag confusion.
- Updated xeBuild to v1.01 with support for Dashboard 14717.
- Updated Dashlaunch to latest version 2.30
- Updated Rawflash to v4 (xenon.elf in folder ..\Data) for better Flashing.
- Updated Xell-Reloaded to Xell Reloaded v0.991 with built in RawFlash v4.
- Updated Flashing Instruction for proper operations with RawFlash.
- FreeStyle Dash is set to boot as the Default Dash with default "launch.ini"

Credits to xeBuild / Dashlaunch devs, especially cOz.




source:  www.tortuga-cove.com