updflash help

[wans]

Ok so i want to update to the latest dash but i tried this twice before and it didnt quite work out, i just want to know how well does Flash360 relocate bad blocks, the last time i done it it killed my xbox and i had to get the soldering iron back out to fix it, i really don't want to have to do that again, the freeboot image i made in freeboot toolbox is perfect and does not consist of any badblocks, my working XBR works fine because i used the badblock tool to relocate.

Also i heard something about updating your flash not working so good on falcon motherboards can anyone clear that up for me?.

From the info iv given does anyone know 100% if this is going to work or not going to work.

[Gazcoigne]

flash360 doesnt manage bad blocks at all, it will simply flash the image into the nand you give it.

do it yourself its piss easy

open you original dump in degraded and note the bad blocks and their relocations

manually read out the sectors using nandpro and inject them into the respectve remapped locations in your freeboot image

the fact you need a point and click app to do your work for you points to the fact you either need to read up a bit more or get a pro to do it for you.

[wans]

Any pros willing to help me out?

[Gazcoigne]

come on dude we are not here to wipe your ass for you, rise to the plate man.

ill help you certainly but im not doing it for you, you should learn yourself.

open your orig dump in degraded 1.1 and post a screenshot so i can show you and others reading

it will say

bad block found at (for example) 0x01A
block relocated to 0x3FF

may be lots or just a few

then you need to read out the corresponding sectors from your freeboot image using nandpro name them sequentially

then inject them back into the freeboot image where degraded tells you they should go starting at 0x3FF working backwards (assuming 16mb nand 256,512 have diff adress i cant remember off the top of my head but can be found on the forum boards)

then when done put the freeboot image on root of USB drive named as updflash.bin

load flash360 and choose to flash without keeping current kv and config

job done

if you post a screenshot of degraded i will give you the commands for nanpro

its quite simple to work out really each bad block will be listed sequentially and are remapped in order backwards from the last block.

[wans]

Sorry im really new to all this stuff.

Dregraded won't open my orig dump, it just says Error: Cannot read file and i tried the change year trick.

My bad block is located at 0xD i have a 16mb flash.

[wes11ph]

just convert your xbr image to freeboot.32

[wans]

just convert your xbr image to freeboot.32

Any pointers on how to convert xbr to freeboot? i can't find anything on that.

Also will this work: replacing all the 8995 files in the flash via xexmenu FTP with files from 9199.

      - aac.xexp[1,2]
      - aac.xexp[1,2].meta
      - bootanim.xex
      - bootanim.xex.meta
      - bootanim.xexp[1,2]
      - bootanim.xexp[1,2].meta
      - cb_[1940, 4579, 5771, 6750].bin
      - cd_8453.bin
      - ce_1888.bin
      - cf_8498.bin
      - cg_8498.bin
      - createprofile.xex
      - createprofile.xex.meta
      - createprofile.xexp[1,2]
      - createprofile.xexp[1,2].meta
      - dash.xex
      - dash.xex.meta
      - deviceselector.xex
      - deviceselector.xex.meta
      - deviceselector.xexp[1,2]
      - deviceselector.xexp[1,2].meta
      - gamerprofile.xex
      - gamerprofile.xex.meta
      - gamerprofile.xexp[1,2]
      - gamerprofile.xexp[1,2].meta
      - hud.xex
      - hud.xex.meta
      - hud.xexp[1,2]
      - hud.xexp[1,2].meta
      - huduiskin.xex
      - huduiskin.xex.meta
      - mfgbootlauncher.xex
      - mfgbootlauncher.xex.meta
      - mfgbootlauncher.xexp[1,2]
      - mfgbootlauncher.xexp[1,2].meta
      - minimediaplayer.xex
      - minimediaplayer.xex.meta
      - minimediaplayer.xexp[1,2]
      - minimediaplayer.xexp[1,2].meta
      - nomni.xexp1
      - nomni.xexp1.meta
      - nomnifwm.xexp1
      - nomnifwm.xexp1.meta
      - signin.xex
      - signin.xex.meta
      - signin.xexp[1,2]
      - signin.xexp[1,2].meta
      - updater.xex
      - updater.xex.meta
      - updater.xexp[1,2]
      - updater.xexp[1,2].meta
      - vk.xex
      - vk.xex.meta
      - vk.xexp[1,2]
      - vk.xexp[1,2].meta
      - xam.xex
      - xam.xex.meta
      - xam.xexp[1,2]
      - xam.xexp[1,2].meta
      - xenonclatin.xtt
      - xenonclatin.xtt.meta
      - xenonclatin.xttp[1,2]
      - xenonclatin.xttp[1,2].meta
      - xenonjklatin.xtt
      - xenonjklatin.xtt.meta
      - xenonjklatin.xttp[1,2]
      - xenonjklatin.xttp[1,2].meta
      - ximecore.xex
      - ximecore.xex.meta
      - ximedic.xex
      - ximedic.xex.meta
      - ximedic.xexp[1,2]
      - ximedic.xexp[1,2].meta

Im thinking that seems to be what dash version your loading.

[bidomo]

Don't use FTP to modify the flash when you hardly can turn on the console...

[wans]

Don't use FTP to modify the flash when you hardly can turn on the console...

The console powers up fine.

Forgive me if im missing something but if the flash holds the dash version why can't i just do that via FTP?

[bidomo]

Go ahead an do it!

Yes you can!

You don't wanna read but if you insist do it.

I was saying YOU can hardly turn on the console, not that the console fails. In other words, take it to someone else

[AD]

And I thought the instructions inside of freeboot were enough... I guess I was wrong.

[wans]

Sorry about being an idiot.

How does this look?



Uploaded with ImageShack.us

Because degraded wouldnt open my orig image i used the bad block tool only to open it, it tells me that my bad block is at 0xD.
Also nandpro while dumping my orig image gives me an error reading block D

So i assumed "nandpro up.bin: -r16 0x00D.bin 0x00D 1" was the command i needed to go for.

[Arakon]

Then you didn't read the instructions. block addresses are written without the 0x in the commandline. 00d/3ff.

[ReverseAffect]

not to mention degraded didn't open the nand ...
do you know why?

[wans]

Then you didn't read the instructions. block addresses are written without the 0x in the commandline. 00d/3ff.

Arakon i know you are a very knowledgeable guy and im not trying to insult you, i did read the instructions.

The commandline for block adresses can be 0x00D or 00D or even just D. just tried all 3 and all extractions are identicle in hex, not that it matters, just if you find anyone else who may have done it different like so, it dosn't make any difference and won't be the cause of any problems.

[wans]

not to mention degraded didn't open the nand ...
do you know why?

I have no idea why degraded won't open my orig.bin, i dont understand it at all.