Status Code: d000007b when trying to format HDD

[mushy408]

I've been running XBR on my jtag console for a while now without problems. I could format the hdd, create/remove profiles etc...

I've updated to the new freeboot (12611 dash) using bestpig's toolbox. Everything has gone fine. Only problem is when I try to create a profile, create a directory or format the HDD I get this message...

Xbox Live error
(something like) The requested operation is unavailable at this time, please try again later
Status Code: d000007b

If I boot into freestyle and try creating a directory with the file manager, I get the same error.

Tried the HDD in another console - works 100% fine (formatting, profiles etc)
Restored the XBR nand backup onto my console - HDD works as it should (formatting etc)
Flash the freeboot nand image - Keep getting the status code error d000007b
I can still use the console & play games etc, but anything involving creating dirs/formatting/profiles, it won't have it.

Console is a Xenon. Never had RROD or any problems. Found 2 bad blocks which were remapped to the new image (flash360 does it)

Any help on this? Thanks

[Gazcoigne]

try building a NAND image with fbbuild instead of the one click apps, following the readme also remembering to extract and include all of the security files etc

[mushy408]

Ok, thanks for that. I'll give it a go. The latest version of Fbuild is v0.11? I'll post back with results.

[mushy408]

Just rebuilt the image with FBbuild - tried twice now and no luck.

1) Extracted ALL files needed (KV, SMC, config, secdata etc) & built the image - still have the same problem

2) Used ALL the dummy files to create my image (including secdata & KV) - still have the same problem.

Also popped the HDD out & tried in another JTAG console - works fine.

Could I have found a bug in the new freeboot? If I flash freeboot 9199 - everything works fine (profiles, formatting etc)

Every profile I create is corrupted - does this mean BANNED? I've already tried with findsecdata & patched the image with the zeroed file(s) using nandpro - STILL THE SAME!!!

Any help?

[mushy408]

Yet another update - I decrypted the X-value using 360 flash tool - it says that everything's clean, so i'm guessing the console isn't banned after all.

Looks like a bug in freeboot 0.4 with Xenons. I've tried many combinations and still can't get it working right.

I should have some more consoles & HDDs coming today so I can test further.

Any more ideas?

[l_oliveira]

Feels, smells, looks like CORRUPTED KEYVAULT. 

[mushy408]

Ok, I'll try swapping KV with another xenon I have.

I have 3 Nand dumps (done with infectus) and all 3 are identical... Infectus is pretty crap for any oustanding features. Looks like I'll have to resort to Xavbox.

Thanks for the suggestion. I'll keep you posted on progress.

[l_oliveira]

Infectus is a big pile of dog poop. Avoid it by any costs unless you're out of options on the console (blown SPI port).


Honestly it's wiring is a big source of bit errors on the flash. It's flashing algorithm/CPLD firmware and flashing app work like if they were written by an underpaid overworking programmer locked up in a basement. Xavbox tools and drivers make it work slightly better but it's still plagged by the poor CPLD firmware.

You're likely to be very frustrated because of things not working as they should if you keep using that Infectus...

[mushy408]

But what I don't understand is that I can flash 9199 freeboot and it works no problems. The console & infectus do not move inbetween flashing, they are stationary.

I tried another KV from a xenon - I still get the same error.

From further studying, it looks like the error comes when the onscreen keyboard tries to pop up - it does this on a number of things (create profile, rename etc)

Which file(s) should I be looking at for the keyboard function? I'm guessing it is dashboard related, but even with freestyle dash it happens.

[l_oliveira]

Last possibility is that your nand has bad blocks, then and you're not remapping them because INFECTUS SUCKS.

Yank that crap out and use SPI to flash. It will allow you to actually see which blocks of the nand chip are bad and will then allow you to take an attitude and solve the problem.

Without knowing which blocks are bad you won't be able to remap them.



Did I mention already that Infectus suck ? No ? Then let me say again, it sucks.

[mushy408]

I can confirm that both the bad blocks were remapped in all images. I'm now using an SPI flasher I built today.

Flashed a clean 12611 image with donor KV SMC & the rest. Still getting a Xbox live error screen - wierd. I've already applied the 12611 update for the avatars.

I know it isn't bad blocks because if I DONT remap them, the xbox refuses to turn on.

Still thinking its a bug in freeboot...

[l_oliveira]

The only way to know is flash the same rebooter image into another console and observe if it fails.

Fault on certain files are not fatal (E71, E72, E79) so the console will boot and play without them. But then odd stuff like what you mentioned would happen.

[cory1492]

Still getting a Xbox live error screen - wierd. I've already applied the 12611 update for the avatars.

An error screen as in the console won't do anything else? .... or a simple message telling you something like "needs to write data to connect to live, do you agree" (tell it OK and it never asks again unless you reflash without retaining mobile*.dat), or a message related to a live profile you have not being able to sign into live (also a normal message if you use a live enabled profile, along with a massive delay in loading dash if you provide a net connection and have the machine blocked from WAN by router)?

For some reason I'm betting it's the "need to add data" - too many people don't read this message to actually see that it's asking something instead of giving an error.

xenonclatin.*/xenonjklatin.* hold strings and resources that are used throughout the dash, if either are corrupt you'll get oddities like onscreen keyboard not having any text or error messages with garbage (and more often than not a frozen console.) Problems with these files don't seem to be checked, I think the software assumes they are intact and always tries to use them.

[mushy408]

Ok, I'll explain from the top...

I have 3 good nand dumps of this xenon - contain 2 bad blocks (remapped when I flash using flash360)

I can write the original nand back - works perfect.

If I build & write XBR3 image (using kv, SMC, config etc) everything works as normal.

If I build & write a freeboot 9199 image (using original nand image) everything works as normal

If I build & write a freeboot 12611 image (using original nand OR donor files) I still get the error.

I flash a NEW freeboot image, then once complete I go through the setup screen on the xbox. Once I've done that. I power off, insert a HDD then power back on.
Next I insert my USB memory stick (with 12611 update) to update the avatars.
Then I try to create a profile - a blank box pops up on screen with just 'A' & 'B' (pad buttons) at the bottom -this should be when the onscreen keyboard comes up. I then have to press the xbox button to close it. If I press 'A', a profile is created but is corrupt as it doesn't have a name (which I cannot rename due to the keyboard)

At no point does the xbox ask to connect to live or do any other messages come onscreen.

When I go into settings/memory to format the HDD, I press 'A' to enter the console serial number, then a box pops up saying

Xbox Live error
This feature is currently unavailable
Please try again later
Status Code: d000007b

This is the EXACT message as appears on screen

The console is not connected to the net in anyway, nor has it been in the last few days of trying to sort this error out. This happens even after a fresh flash using flash360.

Most likely that something is being corrupted whilst flashing.

@cory1492 - where abouts would I find xenonclatin? I'm guessing this is a dashboard font or resource?

[l_oliveira]

I just found some console with odd behavior as well. While it's not exactly the same problem as yours it's something odd which prevents it from playing certain games, like for example halo3.

It gives "dirty disc error" even though the disc is fine or even when playing from a GoD container. I suspect it has either CPU issues or RAM issues.

[q36]

is that from fsd or from kinect dash?

[l_oliveira]

Wow, now that's odd. If I run the console without the harddrive, Halo3 plays fine.

I started to suspect of screwed up Southbridge chip (perhaps the HDD SATA PORT)

But definitely in my case it's a hardware fault.

[mushy408]

Ok, think I made some progress.

My infectus has gone in the bin (finally broke last night after 3 years of use) so I've been using an SPI flasher I made.

360 Nand flasher, Flash360 & XELL DO NOT handle bad blocks correctly - Even after remapping, dumping the nand afterwards shows the bad blocks were not allocated/moved properly.

I fixed the xenon by manually moving the blocks (hex editor)

Just been on with a Falcon that has 4 bad blocks (0x153, 154, 155, 1BB) which I remapped using 360 nand flasher. After dumping the nand I got 4 bad blocks, but FIVE blocks used in the spare area which did not match the original mapping.

Once again, hexedit the Nand header (to use in Bad Block Mover) remapped, change the header back & then flashed.

SORTED!!!

Lesson to be learned - there still isn't 1 decent program to handle bad blocks without the mucking about with either nandpro or hexedit.

If someone could edit/re-write the bad block mover program to remove the header check (zero paired image) to make it UNIVERSAL that would be a good treat!

[Gazcoigne]

its a bit unfair to say that those apps do not manage bad blocks at all, they didnt for you in that particular console.

I have flashed tons of NAND's using flash360 without one single problem with bad blocks.

moving blocks with nandpro is childs play also!! how hard is it to type a few commands??

[er_turu]

Is a very old post and i`m reply for future users for same error
I´m same error and fix flashing the jtag nand with Flash360

Sorry for my bad english