xboxscene.org forums

Author Topic: What Happens If A System Update Is Triggered On The Cygnos' 2nd Na  (Read 104 times)

ILLPLEASA

  • Archived User
  • Newbie
  • *
  • Posts: 49

I know it has been stated that we are to never update the Xbox 360's onboard kernel to anything over 7371 as we would lose the Jtag hack and all ability to run homebrew. Now, my current setup has the original exploitable untouched 7371 kernel on the Xbox's onboard NAND. I am running Cygnos v2.0 revD updated to firmware 1.03.

My problem is that since I do not have the Resistor removed in order to stop the efuses from being burnt out, I am looking for alternate ways that would prevent friends and family from accidentally updating my system in the future.

What I want to do is have the 7371 kernel removed from the onboard NAND (as long as I have a backup this shouldn't be a problem). I want to install Xell on my onboard NAND so that in the event my friends and fam accidentally flip the NAND switch (from my Cygnos 2nd NAND to the onboard switch) that they will be met with Xell's blue screen and  won't be able to accidentally update my kernel.

Now my question is can updates be installed (from new games/HDD's from other xbox's with newer kernels, ect) when you are running off of the Cygnos' NAND? If so, will these updates triggered from an install on the Cygnos' NAND blow the onboard Xbox's efuse (even if it is not being run from the Xbox's onbard NAND)?

Thanks guys for reading my post, and I hope to hear from you soon.
Logged

Grandmaster56

  • Archived User
  • Newbie
  • *
  • Posts: 41
What Happens If A System Update Is Triggered On The Cygnos' 2nd Na
« Reply #1 on: February 02, 2020, 04:26:00 PM »

I believe the fuses would be burnt even if the update was on a cynos nand.The connection ports are simply connected to the nand with a cygnos and when the flip is switched the 360 uses that nand instead.I'm no expert but i would say whatever nand you decide to use would burn the efuses.By the way you don't have to remove rt63 resistor to stop blowing fuses.The is a method for bridging two alternate resistors which also stops fuses from burning and is claimed to be much easier.I cant find the post at the moment but if i do ill be sure to link to it.
Logged

juggahax0r

  • Archived User
  • Hero Member
  • *
  • Posts: 602
What Happens If A System Update Is Triggered On The Cygnos' 2nd Na
« Reply #2 on: February 02, 2020, 06:50:00 PM »

You bridge pins 2 and 3 of u6t1 or u6t2 depending on which is installed , only 1 of the two will be. Both of them are tied to r6t3 and bridging the points is supposed to be more safe than removing the resistor. Their is a technical explanation of why on xboxhacker. Basically though if for some reason a certain part were to go bad and you only had that resistor removed it would be able to power on again , that is an unlikely if , but in any case bridging those 2 points is much easier to undo if you ever wanted to update and burn the fuses.

 To answer the question , the only way really to stop it from happening is to remove that resistor or bridge the points , it literally turns off the efuse burning circuit. You can't get online with a Jtagged console so you wouldn't have to worry about an update coming from LIVE , and no you can't get online with them you get banned instantaneously i have done it. Seriously just bridge the points if you want to be safe , it is the only way other than denying the update when it asks for one , but like i said you won't be getting on LIVE with it anyways so don't worry too much about it. As an added bonus of removing the resistor , if for some reason you did try to update to 9199 it burns the fuse first so if you have that removed the update fails and you are left with a working 360 still , Before it burned the fuses after the update and you would get e80 when you would try too boot

The only thing you need to worry about is not putting a thumbdrive in thier that has the system update on it , you won't be getting any LIVE updates on a Jtagged console , and if you updated without it being Jtagged then you would lose your ability to do it indefinitely.

1 more thing to point out also , the efuses are inside your CPU die your NAND doesn't have anything to do with them , only the CPU. If it were in the NAND then every box would be exploitable by overwriting what is on the chip , or in the case of the Cygnos installing a second NAND , aka Modchip.

 And i can confirm that bridging the points stops it from happening , if you didn't see the youtube video already , go ahead and do it yourself i did. Remove the resistor or bridge the points your choice , and then inssert the USB drive in with the system update. it will start then say system update failed and reboot and when it reboots everything will be fine , except if you leave the drive in it will just ask you everytime if you want too update and it will just keep failing.
Logged