Jump to content
RealModScene

phaze

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About phaze

  • Rank
    RMS Freshman
  1. 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. :-)
  2. I believe the block data is the same as in XELL.
  3. 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]
  4. 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!
  5. 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...
  6. 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..
  7. 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.
  8. 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
  9. 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.
×
×
  • Create New...