If you have updated to dash 8XXX or above - what can you do - read HERE !

[jelle2503]

is that guy trolling or what 

[v0ster]

Oh no... I bought my jasper arcade in summer 2008, I got December 2007 manufacture date console. I didn't know about hacks of it, I went to LIVE, was updated on 8955 kernel... in October I saw THAT, my console now is not hackable ... So I think in China it possible to find an explotable xbox360, I live in a border with China, many things are cheap there.

[n00bpwner360]

So if I'm correct in my understanding, with the JTAG hack, the system is exploited after the CB is loaded. The new CB won't load a 45xx kernel, which is what we used to load the 45xx kernel to then exploit the system. Makes sense to me. Could we rename the 45xx kernel as kernel 8955 or like kernel 9000? I'm assuming no, because the kernel revision is probably signed.

[Arakon]

Exactly. Also, it's not a version number check that keeps it from booting, but the efuse configuration "tells" the kernel that it is not permitted to launch. The kernel itself checks against that.

[globolizator]

What U6T2 on motherboard? Nobody knows?

[n00bpwner360]

What U6T2 on motherboard? Nobody knows?

It's some type of IC, voltage converter/regulator, transistor, mosfet, etc, that isn't present on retail boxes.

[globolizator]

What U6T2 on motherboard? Nobody knows?

It's some type of IC, voltage converter/regulator, transistor, mosfet, etc, that isn't present on retail boxes.

Hmm .... What is IC, voltage converter / regulator, transistor is understandable)))) (what chip?), Only 1 pin her connect with R6T3, so why then the IC is needed. Try it unsolder, died at the same time the voltage on the R6T3, continue to think like torment my Xbox))))
Sorry for the curve English

[n00bpwner360]

Your english is too bad. I'm sorry. I can't understand what you're asking. Try typing your question in your native language and we can put it through google translator or something.

[Blackaddr]

U6T2 is not populated because U6T1 is populated.  Either one will provide the 3.5V necessary for powering the circuit that burns eFuses.  R6T3 connects the ENABLE on the regulator to 5V.  When you remove teh resistor it prevent the regulator from turning on.  Notice that U6T1 and U6T2 do not have the same footprint.  MS probably wanted to have some choice in which component they wished to install.

[globolizator]

Your english is too bad. I'm sorry. I can't understand what you're asking. Try typing your question in your native language and we can put it through google translator or something.

Я хотел узнать точное название U6T2. Хочу по подробнее разобраться с T6R3, точнее узнать его полное назначение, к чему он подключен, не может ведь он подключен к CPU напрямую, или я неправ?
PS. Еще раз извините за мою безграмотность в англиском, японский щас изучаю)))))

[globolizator]

U6T2 is not populated because U6T1 is populated.  Either one will provide the 3.5V necessary for powering the circuit that burns eFuses.  R6T3 connects the ENABLE on the regulator to 5V.  When you remove teh resistor it prevent the regulator from turning on.  Notice that U6T1 and U6T2 do not have the same footprint.  MS probably wanted to have some choice in which component they wished to install.

thanks

[Joka Macer]

so, what you just telling is, if I do this to "rt@@8t1" it can be possible to ger dvd key on kernel 8xxx ??

[Arakon]

where the hell did you get that idea from? this discussion has nothing to do with enabling the hack on updated consoles. there is NO WAY to do any of the existing hacks on 8xxx, period.

[globolizator]

where the hell did you get that idea from? this discussion has nothing to do with enabling the hack on updated consoles. there is NO WAY to do any of the existing hacks on 8xxx, period.

Explain? why? sure 100%

[HiTec]

Explain? why? sure 100%

Cant you people read? First post. Use google translate or something.

[n00bpwner360]

The existing hack methods do not work on 8xxx consoles simply because of this. 8xxx updates install a new bootloader which will only boot 8xxx kernels. The current JTAG hack at some point in the boot process loads a 4xxx kernel because 2 of the 4xxx kernels were exploitable (4532 was it? 4548? I always forget)

Without the ability to boot a 4xxx kernel, you can't run the hack. And the new 8xxx bootloader does just that, restricts booting to anything but 8xxx and above.

Why can't we downgrade the bootloader to the old one? The one that boots any kernel? Well because an efuse is burned to prevent any lower bootloader from booting.

Basically

console does this

get efusevalue;
If(efusevalue == newbootloadervalue && bootloaderinnand==oldbootloader )
{do not boot;}
If(efusevalue == newbootloadervalue && bootladerinnand==newbootloader)
{boot;}

However the old consoles that haven't been updated to 8xxx, the efuse value that the Xbox retrieves, isn't == newbootladervalue, its == oldbootloadervalue, and the oldbootladerinnand will boot;

Am I making any sense? I tried to make it as simple and dumbed down as I could.

Рубить существующие методы не работают на 8xxx консоль просто из-за этого. 8xxx обновлений установите новый загрузчик которая будет загружаться только 8xxx ядер. Нынешний JTAG рублю в определенный момент в процессе загрузки нагрузок 4xxx ядра, поскольку 2 из 4xxx орехов были Пригодный (4532 это было? 4548? Я всегда забывают)

Без способности к загрузке 4xxx ядра, вы не можете запустить рубить. А новые 8xxx загрузчик делает как раз то, ограничивает загрузку ни к чему, но 8xxx и выше.

Почему мы не можем понизить загрузчик в старый? Тот, что любое ядро сапогах? Ну так efuse сжигается для предотвращения любой загрузчик из нижней загрузкой.

Основной

Консоль это

получить efusevalue;
Если (efusevalue == newbootloadervalue & & bootloaderinnand == oldbootloader)
(DO NOT загрузки
Если (efusevalue == newbootloadervalue & & bootladerinnand == newbootloader)
(BOOT;)

Однако старые приставки, которые не были обновлены до 8xxx, efuse значение, которое извлекает Xbox, не == newbootladervalue, его == oldbootloadervalue и oldbootladerinnand будет загружаться;

Я каких-либо смысл? Я попытался сделать его максимально простым и упрощенных вниз, как только мог.

[globolizator]

The existing hack methods do not work on 8xxx consoles simply because of this. 8xxx updates install a new bootloader which will only boot 8xxx kernels. The current JTAG hack at some point in the boot process loads a 4xxx kernel because 2 of the 4xxx kernels were exploitable (4532 was it? 4548? I always forget)

Without the ability to boot a 4xxx kernel, you can't run the hack. And the new 8xxx bootloader does just that, restricts booting to anything but 8xxx and above.

Why can't we downgrade the bootloader to the old one? The one that boots any kernel? Well because an efuse is burned to prevent any lower bootloader from booting.

Basically

console does this

get efusevalue;
If(efusevalue == newbootloadervalue && bootloaderinnand==oldbootloader )
{do not boot;}
If(efusevalue == newbootloadervalue && bootladerinnand==newbootloader)
{boot;}

However the old consoles that haven't been updated to 8xxx, the efuse value that the Xbox retrieves, isn't == newbootladervalue, its == oldbootloadervalue, and the oldbootladerinnand will boot;

Am I making any sense? I tried to make it as simple and dumbed down as I could.

Рубить существующие методы не работают на 8xxx консоль просто из-за этого. 8xxx обновлений установите новый загрузчик которая будет загружаться только 8xxx ядер. Нынешний JTAG рублю в определенный момент в процессе загрузки нагрузок 4xxx ядра, поскольку 2 из 4xxx орехов были Пригодный (4532 это было? 4548? Я всегда забывают)

Без способности к загрузке 4xxx ядра, вы не можете запустить рубить. А новые 8xxx загрузчик делает как раз то, ограничивает загрузку ни к чему, но 8xxx и выше.

Почему мы не можем понизить загрузчик в старый? Тот, что любое ядро сапогах? Ну так efuse сжигается для предотвращения любой загрузчик из нижней загрузкой.

Основной

Консоль это

получить efusevalue;
Если (efusevalue == newbootloadervalue & & bootloaderinnand == oldbootloader)
(DO NOT загрузки
Если (efusevalue == newbootloadervalue & & bootladerinnand == newbootloader)
(BOOT;)

Однако старые приставки, которые не были обновлены до 8xxx, efuse значение, которое извлекает Xbox, не == newbootladervalue, его == oldbootloadervalue и oldbootladerinnand будет загружаться;

Я каких-либо смысл? Я попытался сделать его максимально простым и упрощенных вниз, как только мог.

Рубить, звучит сочень смешно в переводе с англиского на руский, наверно также и я писал с русского на англиский))))
Thanks
сегодня сниму прошивку с Xbox kernel 8xxx (нужно идти к другу, так как у меня notebook) и буду ее смотреть, моя цель вытащить DVD key, так как привод у меня умер. Спасибо всем большое больше не буду беспокоить. Если что-то получиться напишу

[Arakon]

stick to english. if you want to discuss something in your own language, please do it in PM.

[globolizator]

stick to english. if you want to discuss something in your own language, please do it in PM.

I have already apologized, and I will not bother anyone, English I understand but cannot speak it.
PS.sorry for my bad English
in Russia just a few people in some savvy (((

[Joka Macer]

Sorry, guys, but its very hard to bulieve an update have bloking all chances, nothing change in hardwere, if we have a buy new one, it has no exploit will more simple to get, but a update...must be a hole...

what we create a donete or something, to get money for the person or team who did exploit the new update consoles.

for invest time and knowledge in !

I think its vary many in this update...