Post by: kingpickle on January 20, 2010, 01:08:00 PM
QUOTE(cardboardbox @ Jan 20 2010, 02:42 PM) 
I know I cant jtag this 360 but is there any reason to believe in the near future it will be able to be jtagged? The LT nfo says we should update before updating to the latest firmware so I guess I have to decide what I want to do now.
Update it. If a new exploit becomes available (dont expect this anytime soon) you really wont have any trouble finding a box to mod.
Post by: craz3d on January 20, 2010, 01:10:00 PM
...as it has been stated many times in many other similar topics, there is currently no known method of downgrading or reprogramming the eFUSEs which prevent older kernels from being run.
Whether or not you want to hold onto an non-exploitable box is your decision. If keeping a spare 360 around isn't an issue for you (ie you can afford or already have a primary 360 console) then I'd say keep the system software at this version. We know for a fact that updating doesn't help the situation.
That said, the technical documents I've read do not lead me to believe that there will be any solution for downgrading in the near future. The devs behind the hack are busy reverse engineering other sub-systems to allow us full-speed CPU and other niceties. They aren't going to waste their time on finding a new hack when their plates are already full.
Post by: cardboardbox on January 20, 2010, 01:43:00 PM
Post by: cardboardbox on January 22, 2010, 12:18:00 AM
Post by: krizalid on January 22, 2010, 12:53:00 AM
QUOTE(craz3d @ Jan 20 2010, 03:10 PM)
...as it has been stated many times in many other similar topics, there is currently no known method of downgrading or reprogramming the eFUSEs which prevent older kernels from being run.
I like being optimistic here, but Think about the possibility of finding an exploit on newer kernels that depend on efuses that haven't been blown. Only this way we may have homebrew to all consoles up to date.
I'm no expert at this, but I've seen this happen in other scenes (PSP for example) and even though the 360 is far more complex than a PSP, XBOX1 or a Wii, I'm sure one day, a new kernel exploit will be found.
Think about XBR currently... it's homebrew running on Dash 8955, and who knows what kinds of tools the devs might have to find loopholes or exploitability withing that kernel that might bring a newer softmod/hardmod in the future.
Never say never, and than again, don't hope too much for something not even we can understand it fully.
Cheers.
July 2009.... Dash 7363.... have you at least dumped the NAND just to be sure that the CB is not exploitable?
I know that there are some manufacturing dates that refer to updated 2BL, but give it a shot, you can't loose anything.... well, you may loose your 360 if you do something stupid.
Post by: cardboardbox on January 22, 2010, 10:46:00 AM
QUOTE(krizalid @ Jan 22 2010, 08:53 AM)
I know that there are some manufacturing dates that refer to updated 2BL, but give it a shot, you can't loose anything.... well, you may loose your 360 if you do something stupid.
I'm pretty good at doing something stupid 
Post by: craz3d on January 22, 2010, 01:34:00 PM
QUOTE(krizalid @ Jan 22 2010, 02:53 AM)
I like being optimistic here, but Think about the possibility of finding an exploit on newer kernels that depend on efuses that haven't been blown. Only this way we may have homebrew to all consoles up to date.
I'm no expert at this, but I've seen this happen in other scenes (PSP for example) and even though the 360 is far more complex than a PSP, XBOX1 or a Wii, I'm sure one day, a new kernel exploit will be found.
Think about XBR currently... it's homebrew running on Dash 8955, and who knows what kinds of tools the devs might have to find loopholes or exploitability withing that kernel that might bring a newer softmod/hardmod in the future.
Never say never, and than again, don't hope too much for something not even we can understand it fully.
The biggest flaw in your argument is the assumption that everyone on this board shares the same degree of understanding in regards to the SMC/JTAG hack. Most of the people here only know what they've read in other topics. This information is generally only half-true or pure speculation. Sometimes it is flat out wrong.I'm no expert at this, but I've seen this happen in other scenes (PSP for example) and even though the 360 is far more complex than a PSP, XBOX1 or a Wii, I'm sure one day, a new kernel exploit will be found.
Think about XBR currently... it's homebrew running on Dash 8955, and who knows what kinds of tools the devs might have to find loopholes or exploitability withing that kernel that might bring a newer softmod/hardmod in the future.
Never say never, and than again, don't hope too much for something not even we can understand it fully.
I like being optimistic, too, but the problem is that the 360 has been out for over 4 years. Assuming there have been people working on trying to exploit it since launch, this means in 4 years we've only found 2 exploits. I have read much of the technical documentation for both hacks (moreso and more recently with the SMC/JTAG hack) and coupled with my formal education in electronics and computer science, I have fairly high degree of understanding in regards to the workings of the hack and a lot of appreciation for the shear amount of work that it must have taken to reverse engineer something like the XBOX 360.
Homebrew is not running on the legit 8955 kernel. The kernel booted by XBR is a _hacked_ version of 8955. The underlying code running behind the scenes of a JTAG box running 8955 is very different from that of retail boxes. If the developers behind the hack say that it is very hard to reverse engineer the CPU JTAG in attempts to access potentially-nonexistant functions to reverse eFUSE changes, I would listen to them.