Well, JRunner extracts the needed files OK, but crashes immediately on attempting to create the new image. Same thing on two different computers. Can someone more knowledgeable than me tell me how to accomplish the same thing with Xebuild or some other utility?
Good burns suddenly unreadable in XBL
- Thread starter PMac10000
- Start date
Nevermind, I found I way to do this. Backups are working. System info reports 16537.0 . But now the network connection test shows I can connect to the Internet, but not XBL. Followed by a suggestion to reset my router (port forwarding etc).
Nevermind once again... that XBL error appeared to be due to a Family Block setting that I removed. Now when I attempt to connect to XBL, I'm getting the same message requiring a system update. Do you suggest I take it from XBL? Or is there a better way.
Thanks for all your help.
Thanks for all your help.
I went ahead and attempted an offline USB update since the $systemupdate files are available from MS. Same symptoms... backups are unreadable after update. I see that my LDV has incremented again in Xell. In the NAND, the LDV on the right has increased to match, whereas the LDV on the left remains at the previous value. I assume that's OK.
Martin C
VIP Member
Yes, LDV changes are expected and are exactly as stated in my LDV sticky.
When was the last time you flashed your DVD drive?
When was the last time you flashed your DVD drive?
The Demon was installed and DVD flashed back in April (by a very reputable modder who happens to be a Super Mod here :smile: ) I have not flashed it since.
My noobness is showing, but I was under the impression that flashed Slim drives are locked. What is different about my console that is causing these system updates to flash them back to stock (which is what seems to be happening?)
My noobness is showing, but I was under the impression that flashed Slim drives are locked. What is different about my console that is causing these system updates to flash them back to stock (which is what seems to be happening?)
Martin C
VIP Member
It's not flashing anything.
Get the JF log from the person who flashed the slim drive for you. There's obviously a change somewhere and it's affecting your ability to read backups on the new dashboard.
Get the JF log from the person who flashed the slim drive for you. There's obviously a change somewhere and it's affecting your ability to read backups on the new dashboard.
Unfortunately, he doesn't have the JF.log. Short of waiting for a new release of Xebuild that support 16547, is there any other way to build a clean retail 16547 NAND? Should I even expect the new Xebuild to solve the problem?
Martin C
VIP Member
It's not a problem with the update via Xbox Live. Not from what I can see. FWIW I keep logs of all drives I flash and all consoles I RGH/JTAG.
If originals stopped working, it would be another matter. I'd look at reflashing the DVD drive.
If originals stopped working, it would be another matter. I'd look at reflashing the DVD drive.
So the new xebuild supporting 16547 is out. Can someone verify if this is the correct command line for what I'm trying to do:
xebuild -noenter -t retail -c trinity -d data -f 16547 -b {1BLKey} -p {CPU Key] -o cfldv=8 output.bin
xebuild -noenter -t retail -c trinity -d data -f 16547 -b {1BLKey} -p {CPU Key] -o cfldv=8 output.bin