Print

[moeom]

QUOTE(Inuyasha152 @ Nov 13 2010, 03:12 AM)

Jasper 512mb. I'm getting "cannot read" errors..

CODE

***** could not read .\data\launch.xex, skipping *****
***** could not read .\data\lhelper.xex, skipping *****
***** could not read .\data\\dae.bin, skipping *****
***** could not read .\data\\fcrt.bin, skipping *****

Using a freeboot 0.032 dump.

So is this normal? I'm guessing yes, this is normal because my Flash 360 dump does not contain these files either. Someone confrim.


I've also got:

CODE

reading .\data\ce_1888.bin (0x5606a bytes) padding to (0x56070 bytes)
reading .\bin\patches_jasper.bin (0x90c bytes)
**** ldv line 3 set to 00 f0 type: c

[Haygar]

QUOTE(ElecTriX @ Nov 14 2010, 08:49 AM)

Hi everybody! Just registered here 'cause I have a couple of question about updating my Freeboot.
I'm currently running Freeboot 0.032 (9199) on my X360 Jasper 512.

As I bought my xbox already JTAG:ed I'm currently below newbie-level when it comes to NAND-flashing and all that. Unfortunately the company closed so they are not available to answer the questions that I have. My question is following;

1. The company that did the JTAG said they "removed the possibility that future updates burn the uFuses".. Sounds good to me, but may this be a problem when updating to 12611?
2. Don't know if they removed "R3T6" ? Is this standard when doing JTAG and what if they did not remove it? What can happen?
3. I received a dvd-disc containing many files; Folder "66mb" containing "nand1.bin" -> "nand3.bin", all of the same size 69 696 KB. Folder "512" containing "nand1.bin" -> "nand3.bin", all of the same size 540 672 KB and also a text-file named "badBlocks".  What's the difference between the files as they are different sizes? Also, why is there 3 files?
4. What's best, using the original NAND or the 0.032-NAND? If using the original NAND might bad blocks be a problem?
5. When flashing on xbox, keep KV and config or not? What's best and why?

Sorry for all the questions and hope none of you judge me for being a newb, want to learn! If you have links that might answer the questions above please send me!

Questions 1 & 2 are essentially the same and although I have no update protection on my consoles, freeboot doesn't burn efuses so a valid freeboot image shouldn't be concerned whether R6T3 or jumper protection is in place when updating(someone correct me if I'm wrong)
The 3 nand dumps of 66mb and the other 3 of 512 should hopefully all be the same. They are done when reading the nand to verify the info is correctly read. The 512mb is the whole nand which includes everything like game saves and all but it's only the first 66mb you need. You can compare them to each other in a hex editor like HXD to verify that they match. eg if 1 & 3 match but 1&2 or 2&3 don't then 2 must have errors, so use 1 or 3, get it?
You should be ok to use either nand but I would go for the 100% original to be sure.
Also, I always rewrite the whole image (66mb) without keeping kv or config incase anything staying gets overwritten.
The rest of the nand doesn't need to be written to, just back it up before tho if you use it to save your games to the internal MU.

Hope this all makes sense, I gabble on a bit lol

Edit: Oh, and about the bad blocks, if they are outside the 66mb nands then don't fuss. If they aren't then they will most likely need to be remapped for your rebuilt image to work. Check them in 360 Flash Dump Tool 0.97. You will have a tab appear at the top right saying "Bad Blocks".Haven't done much on this but my jasperBB had one in the critical area but since when XBR started I've just written to my nand without remapping that bad block and it's been fine. Checking the dumps back confirms it's all good. I'm not saying everyone would be so lucky.

[Haygar]

QUOTE(DragonNZ @ Nov 14 2010, 09:05 AM)

It is a Jasper 16Mb CB 6723 (Verified in 360 Flash tool, and Easy GUI Frebooter). I have tried flashing both keeping the keyvault (Option A in Flash360) and overwriting the values (Option B in Flash360). Both times when I reboot, the splash screen is displayed and hangs at that point.

Hows your file system look in 360 fliash tool? Do you have 29 files. I stated earlier that the one fbBuild created for me had missing files although other than that it looked ok and was the correct size.

[ElecTriX]

QUOTE(Haygar @ Nov 13 2010, 11:20 PM)

Loads of good info

OMG, thanks for the answers! I've opened both the original 512mb NAND and the 66 "updflash.bin" in Flash dump tool but have never gotten the "bad blocks"-tab you are mentioning..? But still the badBlocks.txt is in the folder. The txt contains the row

QUOTE

error 204 reading block 668A

Also in Flash dump tool there is one big difference between the 512mb ORG NAND vs. the "updflash.bin";

QUOTE

6BL (CF) Patch 1
7BL (CG) Patch 1

is blank in the updflash.bin.

Also a more general (and somewhat dumb) question. But when updating my Freeboot then installning the dash-update, this won't screw up my saves / installs / JTAG in any way?

[Haygar]

QUOTE(ElecTriX @ Nov 14 2010, 10:01 AM)

OMG, thanks for the answers! I've opened both the original 512mb NAND and the 66 "updflash.bin" in Flash dump tool but have never gotten the "bad blocks"-tab you are mentioning..? But still the badBlocks.txt is in the folder. The txt contains the row
Also in Flash dump tool there is one big difference between the 512mb ORG NAND vs. the "updflash.bin";

is blank in the updflash.bin.

Also a more general (and somewhat dumb) question. But when updating my Freeboot then installning the dash-update, this won't screw up my saves / installs / JTAG in any way?

Nah, my falcon which has only 16mb nand(duh) shows correct 6bl and 7bl but the jasperBB shows blank also, always has even with freeboot9199, think it's just a minor bug in 360 flash tool.

I think 668A is well outside the 66mb area? 1000 blocks(FFF) sound right anyone? I'd have to go and check, if it is then your good to go.

Edit: Use Flash360 v1.0 on usb to dump your whole nand(512) before you reflash, especially if you use the internal MU for games saves. It may appear as unformatted after you update, which you know what that means.

[ElecTriX]

QUOTE(Haygar @ Nov 14 2010, 12:07 AM)

Nah, my falcon which has only 16mb nand(duh) shows correct 6bl and 7bl but the jasperBB shows blank also, always has even with freeboot9199, think it's just a minor bug in 360 flash tool.

I think 668A is outside the 66mb area? I'd have to go and check, if it is then your good to go.

Edit: Use Flash360 v1.0 on usb to dump your whole nand(512) before you reflash, especially if you use the internal MU for games saves. It may appear as unformatted after you update, which you know what that means.

Could you check it 668A is outside? Would really appreciate it!  

Ok good idea, gonna do a complete NAND-dump. Just as I know, after I've saved a complete NAND, updated the NAND and worse-case-scenario; the internal MU appear as unformatted.. What's my options then?

Also what's the "aud_clamp fix" ? As I've understood it there is some kind of software-fix if you've soldered something inside the xbox or what? How do I know if I should check it in EFB?

[Haygar]

A basic way if you have access to a memory card or official Hdd, (if it's someone elses accessories make sure they dont have the new kinect update on it or it will want to update, turn back now,9199 avatar update is ok since you're on FB 9199)transfer all your saves, profiles etc. to them as well as a full dump. I don't use the internal MU so haven't had to try restoring that sort of stuff afterwards. You just reformat (if required) using NXE/Kinect dash in the system/memory area later.

Aud_clamp fix is a newer alternative to the original jtag wiring that was introduced to help over come some problems that some consoles were having with booting, weird ring of light functionality, I think Zephers were the worst.
You will need to know if your's is wired for this because the SMC code has to match for the jtag hack to work.
I haven't done this even tho I get the occasional ring of light glitch, but doesn't phase me enough to be bothered, don't want to pull the pcb out of the case really. I'd prefer weird ROL than RROD.
If you have a wire going to the front ring of light pcb and another to DB1F1/FT1U2 then you have the original setup, but do your research first or you might end up with a non-starter.

Edit: I'm almost certain 668A is WELL outside the area of your 64/66 mb dump. Since you're not getting bad blocks in 360 flash tool, I'm presuming that it's just in the MU area of the nand so there's no problem.

[selfser]

QUOTE(boflc @ Nov 13 2010, 02:42 PM)

i just accepted that and flashed.

cool.  Got it working. Thanks a bunch

[DragonNZ]

QUOTE(Haygar @ Nov 14 2010, 11:48 AM)

Hows your file system look in 360 fliash tool? Do you have 29 files. I stated earlier that the one fbBuild created for me had missing files although other than that it looked ok and was the correct size.

Yup, just verified it now in 360 Flash Tool, 29 files in total for the new 12611 flash.

[ars0n]

awesome guys, this worked perfectly!!! zepher cb 4558

[QuackMasterDan]

Thank you so much Sneaky Peanut, for making such a simple, easy-to-use, and effective tool. It worked perfectly for the first try on my Zephyr 4558, especially on the trouble I've had in the past with aud_clamp wiring. I am having trouble to express the thanks I have for this tool you made (and with great speed too). Many gold stars to you and those involved with fbbuild.

[Teke_]

QUOTE(DragonNZ @ Nov 14 2010, 12:05 AM)

It is a Jasper 16Mb CB 6723 (Verified in 360 Flash tool, and Easy GUI Frebooter). I have tried flashing both keeping the keyvault (Option A in Flash360) and overwriting the values (Option B in Flash360). Both times when I reboot, the splash screen is displayed and hangs at that point.

I have exactly same problem. It is Jasper 16Mb and CB is 6723. Southbrigde version is 2.3. I had been using different methods to update.

At the beginnig i had xbr. I have to use XBR_Jasper16a_8955 because of that version was for boards with the new southbridge. Worked without problems. Then i updated to 9199 with FreeBOOT ToolBox Maker 2.4 and Flash360. Everything was perfect.

Tried to update to freeboot 12611 with many different ways. When i boot in new 12611 splash screen is displayed and it hangs there everytime.

Now i had tested following ways:
- Easy Gui Freebooter 12611
- FreeBOOT Toolbox 0.04 Maker v2.5
- Followed qualar tutorial (http://forums.xbox-scene.com/index.php?showtopic=723596&st=150&p=4752448&#entry4752448)
- Jtag tool

After failed update I had used lpt to flash nand again. And I can flash back 9199 version and its always working.

Can anyone help? Thanks.

Edit: I had tryed to create 12611 nand from original, xbr and freeboot 9199 version. Same situation always. And in my original dumb I have bad block at block 27D.

[DragonNZ]

QUOTE(Teke_ @ Nov 14 2010, 11:15 PM)

I have exactly same problem. It is Jasper 16Mb and CB is 6723. Southbrigde version is 2.3. I had been using different methods to update.

I just tried using freeBOOT_ToolBox_Maker25r2 (Best Pig 2.5r2) and it is still the same, hangs on the splash screen.....

[thesonandheir]

QUOTE(Teke_ @ Nov 14 2010, 10:15 AM)

I have exactly same problem. It is Jasper 16Mb and CB is 6723. Southbrigde version is 2.3. I had been using different methods to update.

At the beginnig i had xbr. I have to use XBR_Jasper16a_8955 because of that version was for boards with the new southbridge. Worked without problems. Then i updated to 9199 with FreeBOOT ToolBox Maker 2.4 and Flash360. Everything was perfect.

Tried to update to freeboot 12611 with many different ways. When i boot in new 12611 splash screen is displayed and it hangs there everytime.

Now i had tested following ways:
- Easy Gui Freebooter 12611
- FreeBOOT Toolbox 0.04 Maker v2.5
- Followed qualar tutorial (http://forums.xbox-scene.com/index.php?showtopic=723596&st=150&p=4752448&#entry4752448)
- Jtag tool

After failed update I had used lpt to flash nand again. And I can flash back 9199 version and its always working.

Can anyone help? Thanks.

Edit: I had tryed to create 12611 nand from original, xbr and freeboot 9199 version. Same situation always. And in my original dumb I have bad block at block 27D.

QUOTE(DragonNZ @ Nov 14 2010, 10:59 AM)

I just tried using freeBOOT_ToolBox_Maker25r2 (Best Pig 2.5r2) and it is still the same, hangs on the splash screen.....

Me too, tried a few times now. Still recoverable through Xellous though so it's no biggie.

Jasper 16mb.

1 bad block at 154.

[Blade360]

QUOTE(Roden @ Nov 12 2010, 07:05 PM)

Hi, i have a cygnos installed and had great problems creating an image last time, the only program the worked was the bestpigs creator as it has an option for cygnos special wiring, will this program work anybody know? or wait for bestpigs again?

Easy fixed.

I was in the same boat, I made the freeboot12611.bin using this app but what you do is before you begin anything make sure you grab YOUR appropriate SMC (appropriate for your Cygnos V2 mobo) and rename it the exact same as the apps one in the folder.

So what you've done is deleted the apps Jasper SMC for example and replaced with the Cygnos V2 Jasper SMC you found in Cygnos V2 Toolbox (their official site has it under downloads).

Then just follow the steps and you'll be done.