mko
-
Content Count
11 -
Joined
-
Last visited
Posts posted by mko
-
-
Thanks, I'll try.
I'm meeting the guy I got it from on Monday...he should still have the (original) original NAND image and the possibility to flash it directly. I'm sure he can get it fixed.
-
Thanks guys, you're all the best for trying to help me.
I'm not so sure about that. I tried using XeBuildGUI and jrunner. And NAND Flasher 360 definitely showed a few bad blocks when dumping the image, I don't know why they don't show up in the "before-image". But I'll try some things.whatever you used to create the image has created a bad one, use XeBuild
It's weird, there should be bad blocks in the bad read. I saw it in the NAND Flasher 360 output. Maybe it immediately remapped them somehow?Exactly as above
no bad blocks in read so none should appear in created image
Thanks. I have removed the hard drive, but it still doesn't work. Sadly I can't remove the internal 4GB memory to try that .I got this before, I removed hard drive, powered xbox and it booted, powered off, plugged back in the HD and powered the xbox and it was fine.
Thanks guys. Keep them coming. If nothing works I'll have to find someone who can physically flash the NAND and hope that helps.
-
-
Thanks for your help.1st: try to write back original .bin - in XELL with RAWFLASH
2nd: if it works, get again 4 times and check
3rd: if necessary: remap nand
4th: update image...
5th: upload finally
I tried flashing back the original image with Xell and rawflash, but the console still won't boot (System error, E79). It will even crash earlier than with the updated image. I can always get into Xell though and I can see that the original image contains an older version, while the new image contains the newest version.
I also tried creating the image with jrunner, and also with the xebuild option "noremap", but nothing works...
-
I tried flashing the NAND that was on before using rawflash and Xell (it's really hard finding how to do these things on the web). Sadly the console crashes to E79 even earlier - before even showing the boot animation.
I had 3 or 4 bad blocks if that is any indication?
Dammit...is there anything else I can try? Can I somehow access the internal memory to check for a default.xex as brownienz suggested?
-
I took out the HDD, don't have a USB drive plugged in and can't access the internal 4GB memory anymore to check . Any idea how I can access that using only Xell or a PC? Or maybe it's an entirely different problem...
-
Thanks, but that can't be it. I took out the HDD and I still get E79 .you have a default.xex in the root of your hdd, delete it.
-
Thanks. I took out my hard drive, but I still get the error .
Sorry for double posting, but I wanted the authors of the tutorials to read it as well, maybe they know what's going on. Sorry!
-
OK, looks like I'm in deep doodoo.
I had FSD 2.2 on my Xbox 360 (Trinity (according to XeBuild GUI), Freeboot RGH 1.x).
I wanted to update everything and followed a tutorial from this forum. So after getting the CPU key, dumping the NAND and generating the hacked image with XeBuild GUI and writing it to the NAND, I can't boot my console anymore. Right after the boot animation starts, I get a screen where Microsoft tells me in all languages:
System Error - E79
I can still get into Xell by booting using the eject button. That's it.
PLEASE HELP!
Thank you.
-
OK, looks like I'm in deep doodoo.
I had FSD 2.2 on my Xbox 360 (Trinity (according to XeBuild GUI), Freeboot RGH 1.x).
I wanted to update everything and followed your tutorial. So after generating the image with XeBuild GUI and writing it to the NAND, I can't boot my console anymore. Right after the boot animation starts, I get a screen where Microsoft tells me in all languages:
System Error - E79
I can still get into Xell by booting using the eject button. That's it.
PLEASE HELP!
Thank you.
System Error E 79 after updating FreeBoot
in Support
Posted
My console is finally back in working order. The guy I got it from had to erase and hardware-flash the NAND a lot of times to get it back to work.