phaze 0 Posted February 7, 2016 Hello everyone, Although it is my first post, but I have been reading this forum since 2012 and it helped me alot! Unfortunately, I can not find the solution for the problem I have come to.. I have an old phat falcon XBOX, which is RGH2 (if i am correct). I have successfully updated my kernel version to 17489, although I had three bad blocks, I have injected the updated kernel. So I had some problems at first - I have received error code e79, right after updating kernel. So I have used USB stick with my older kernel in it and used XELL via DVD ROM button on start up to install older kernel again. It fixed the problem, I have dumped my kernel once more, used clean Original NAND and fixed bad blocks with JtagTool. Then, I have updated kernel to 17489 again with Jrunner. And installed it using NANDFLASHER v1.2 It worked! I have launched my xbox and simply transfered aurora folder to HDD via ftp. (I am not sure if it was a good idea) I have not deleted FSD3 folder. I have launched Aurora using *xex file - it launched completely fine. Then I have changed setting of the launch.ini for autostart. It worked fine, Aurora was booting on start-up. Now to the REAL problem - it happened right after I have tried to set a static IP on my XBOX in order to use xboxunity. I went to the console settings - I have done everything according to this manual (http://portforward.com/networking/staticip-xbox360.htm). Restarted my XBOX and boom, I get the error e79 all the time. I have tried to reinject older NAND via USB like the first time and it did not work anymore. I have tried injecting updated NAND via USB - nothing helped. I get the e79 error all the time.. Would anyone be able to recommend anything? I would be extremely thankful for any kind of input. Maybe I should provide some more details? Best regards EDIT: I have forgot to mention, that removing the hard drive does nothing. i still get the e79. Quote Share this post Link to post Share on other sites
superted76 64 Posted February 7, 2016 Boot to Xell and rewrite the flash that way if you can then follow your own procedure until setting the static IP, what exactly do you mean by that or are you meaning inputting the IP of the router for Unity and ConnectX? I have pretty much the same setup and DHCP settings are what I use just default all the way and my unity is fine and connectx works very well from a 2tb pc hdd. I know that when my xbox was first done and the flash written I got E79 error around 15 times before a normal boot so keep I dont think it's too messed up 1 Quote Share this post Link to post Share on other sites
phaze 0 Posted February 7, 2016 Thank you for the answer. Yes, I have tried to set up manual (static) IP in order to use Unity and ConnectX. The thing is I am unable to boot my xbox to dashlaunch anymore, I am always getting e79 error no matter what I do. I have tried multiple times (like 15) and tried various versions of my older NAND. Nothing seems to work anymore, that is why i am so confused.. I mean, is it even possible that xbox would give E79 error right after messing something up with the IP? Maybe the thing is that I have accidentaly tried to check internet connection? Although it showed that only the LAN was working properly, and xbox was unable to connect to the internet at the time. maybe the console got banned? :s Quote Share this post Link to post Share on other sites
superted76 64 Posted February 7, 2016 SO booting to Xell and writing the flash can be done but the 360 wont boot NXE after the fact ? Gimmie 5 mins I'll see if I can find any info and hopefully Swizzy will be around soon he's about your best bet for issues like this i'd say Can you write the original NAND back and see if the console boots that way >> http://www.se7ensins.com/forums/threads/e79-after-writing-xell-aud-clamp.795133/ from there?? Quote Share this post Link to post Share on other sites
phaze 0 Posted February 7, 2016 That is correct. I am unable to boot NXE, FSD or AURORA. I am unable to go past the e79 error anymore. The strange part is that I was able to reinstall older NAND the first time i got e79 and it worked fine, and now it does not help anymore. I do not understand what might have gone wrong. The thing is, I do not have my original NAND. I have only previous RGH versions of my NAND which were working fine before. Now they do not work. Should I try to rebuild original NAND using my CPU/DVD keys and all the info Jrunner has saved? I am going to try and do this. Quote Share this post Link to post Share on other sites
superted76 64 Posted February 7, 2016 Can you boot Xell by powering the console using he eject tray button?.....power the console till e79 then power off leave 5 secs then press eject you should get the blue XELL screen http://team-xecuter.com/forums/threads/67324-E79-error-after-writing-Xell-Xellous-XBR-to-Xenon-mootherboard-exahusted-options http://www.xboxhacker.org/index.php?topic=15655.0 Quote Share this post Link to post Share on other sites
phaze 0 Posted February 7, 2016 Yes, I am able to boot into XELL by using eject button. Although it is not booting properly by itself - it can not find the xenon.elf file, but I have put the xenon.elf to my USB drive and then XELL boots fine. It goes past the blue screen to the black screen, where it starts installing the NAND which is in the USB drive. It mentions all the bad blocks even though J-runner can not see them anymore after fixing it with Jtagtool. After installing the NAND, it says I should shut down the console. EDIT: I believe it should not be the problem with the soldering, as I have been using this XBOX for two years without a problem, and I have not moved it an inch. I believe it should be software problem.. Quote Share this post Link to post Share on other sites
superted76 64 Posted February 7, 2016 Do you have the original NAND dump that you took? If so put that on the root of the usb and flash the Original Dump back to the 360 so thus makin the console retail. If this works delete all the udp.bin files that you have messed with and keep only the original dump and again work from that to create the new flash then try writing from scratch. http://forum.homebrew-connection.org/index.php?topic=144 <<< Swizzy's post on updating the kernel I'd give that a good read if you haven't already Quote Share this post Link to post Share on other sites
phaze 0 Posted February 7, 2016 I do not have original DUMP from a retail console, as I have paid money for someone to make it RGH. I have only the DUMP file of previous RGH version, which was working perfectly fine for more than a year. I have updated the console several times after that with a success previously. I have used this first DUMP file (I have made it in 2015) to recover my console after getting the error e79 for the first time. Unfortunately it does not help anymore, no matter what NAND i am injecting (old "original" which was working, "original" with fixed bad blocks, updated NAND with or without fixed bad blocks) - it does not help. I am getting the error e79 all the time, with every NAND I have used previously. They have worked fine before, thus I do not understand where is the problem. I have read all the tutorials several times, i might have missed something though... Quote Share this post Link to post Share on other sites
superted76 64 Posted February 7, 2016 My only suggestion would be to write the NAND you were sent by the modder power down and repeat the procedure another once at least maybe twice without powering to NXE making sure the NAND was deffo written Quote Share this post Link to post Share on other sites
phaze 0 Posted February 7, 2016 Well, it did not help.. Maybe my hard disk is dead and that is the reason for this problem? Is it possible to upload all the dash/FSD/Aurora files to USB instead of HDD and boot it from the USB? I mean, complete dashboard boot, strictly from the USB stick and with disconnected HDD. BIG thanks for your time and effort anyway! Quote Share this post Link to post Share on other sites
superted76 64 Posted February 7, 2016 Sorry was shopping. Yes I have removed my phat hdd and used external with aurora dash before so that can be done for sure but not sure how that would work with the retail NXE files though, could give it a try don't see what you have to lose lol let me know how you get on bud. I'd remove my 360 hdd and try booting but if its still giving E79 I'd PM Swizzy and ask his advice Just out of curiosity are you booting with the USB WIFI or and ethernet cable attached when getting the E79? if so remove and see if that may help Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted February 7, 2016 The error code "E79" means there was one or more errors within xam.xex (a vital part of the NAND that covers a large portion of it), it's usually caused by a bad block not being handled correctly Do you have a hardware flasher at your disposal? what i would recommend doing is build a clean image (no remapping) using xeBuild GUI (J-Runner takes in itself to fix ANY badblocks for you, even tho you don't want to and it may more often then not lead to it remapping things incorrectly because it doesn't actually check the data fully and whatnot) Anyways, you do a clean build by either selecting "Extract Vital Parts" (advanced mode feature) which simply extract the important data from your nand (the per-console data essentially) and build a image from just those parts, which means the output image has no information about any badblocks or you tell xeBuild to not remap anything... Once you have this clean image, write it to the console, it won't boot still at this point, but should hopefully still boot XeLL (it depends where exactly the badblocks are located) from here, you dump the nand once again, this image will now have your actual badblocks, use this dump to build a new nand (again with xeBuild GUI as it doesn't mess with anything after xeBuild has finished, just copy it to the output path...) flash this, now if everything is good, your console should boot again as you want it to If it still don't work, you need to erase the nand using hardware 2-3 times before writing the clean image and repeating the above process, you may also want to take note of which blocks are mentioned along with the error codes given as they may tell me what the underlying cause is (some blocks aren't always being marked bad and may not hold the data properly, which means they have to be dealt with manually) And to answer your question before regarding changing your IP settings being possible to cause this problem -> Yes, it's indeed very possible, it's highly unlikely, but possible, any changes to the settings of the console will cause a block to be re-written in the nand, if there are existing badblocks in the nand and they're not handled properly it may overwrite the good data for that block and cause the console to not function properly anymore, usually it's just with that image tho... Quote Share this post Link to post Share on other sites
superted76 64 Posted February 7, 2016 Just couldn't find the words to say exactly that Swizzy lol Quote Share this post Link to post Share on other sites
phaze 0 Posted February 7, 2016 Hey Swizzy, First of all, I am really grateful for a post like this. I really appreciate your time. Unfortunately, I do not have the hardware, so I am trying to play with USB stick. I am going to do as you told tomorrow morning and post detailed reply how it went. As you have asked, I will paste which blocks are bad. This is a log from J-runner. • Bad Block ID @ 0x1DA [Offset: 0x7A3400] • Bad Block ID @ 0x203 [Offset: 0x84C600] • Bad Block ID @ 0x225 [Offset: 0x8D8A00] • Bad Block ID @ 0x1DA Found @ 0x3FD[Offset: 0x1073A00] • Bad Block ID @ 0x203 Found @ 0x3FE[Offset: 0x1077C00] • Bad Block ID @ 0x225 Found @ 0x3FF[Offset: 0x107BE00] Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted February 7, 2016 Hey Swizzy, First of all, I am really grateful for a post like this. I really appreciate your time. Unfortunately, I do not have the hardware, so I am trying to play with USB stick. I am going to do as you told tomorrow morning and post detailed reply how it went. As you have asked, I will paste which blocks are bad. This is a log from J-runner. • Bad Block ID @ 0x1DA [Offset: 0x7A3400] • Bad Block ID @ 0x203 [Offset: 0x84C600] • Bad Block ID @ 0x225 [Offset: 0x8D8A00] • Bad Block ID @ 0x1DA Found @ 0x3FD[Offset: 0x1073A00] • Bad Block ID @ 0x203 Found @ 0x3FE[Offset: 0x1077C00] • Bad Block ID @ 0x225 Found @ 0x3FF[Offset: 0x107BE00] Those may or may not be fully accurate, what does xell tell you?Sent from my SM-G903F Quote Share this post Link to post Share on other sites
phaze 0 Posted February 8, 2016 I believe the block data is the same as in XELL. Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted February 8, 2016 I believe the block data is the same as in XELL. Yes, they appear to be the same, let me know how the tests went, with the whole re-writing with a clean (un-remapped) image and building from a new dump from that Quote Share this post Link to post Share on other sites
phaze 0 Posted February 8, 2016 Well, I think I have just made it worse. I have used a tutorial on 7signs forum on clean NAND building using donor NAND, installed it (somehow still got bad block messages upon install). I believe I might have accidentaly put in LDV value when building an image and now I am getting 3 red rings. I suppose correct LDV value is more important than I thought. XELL does not boot anymore, so I believe I have messed it up pretty bad now. I think I might need to get it to someone who has hardware and more knowledge than me.. Anyway, I really appreciate the time You guys have spent looking into this matter of mine. :-) Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted February 8, 2016 Getting the badblocks is normal, basically your NAND have a few blocks that cannot be trusted, they need to be remapped... Not sure why you chose to go donor route, it's not what i told you to do... you haven't lost any of your own data... you have it, and it's good... it's just that the badblocks aren't being handled correctly for whatever reason... LDV isn't particularly important anymore, however choosing the correct hack is... perhaps that's where you messed it up? Either way, you need a NAND-X or JRProgrammer (or a equivalent by other manufacturers) to reflash your nand using hardware Give whoever you leave it to the dump you had since before, tell them to use the data from that and not what's currently in the NAND... Quote Share this post Link to post Share on other sites
