Shocking news of the new fall dashboard

[Arakon]

actually, same reason. that way you can flash an old NAND dump. without cpu key you couldn't update the LDV and couldn't go back to an older dump.

[Shaun]

why would u remove r6t3 ? so that the efuse remians the same when using diff dashboards / kernels. more reason to do this if you dont have your cpukey.  ldv (efuse) data is held in the hash of cb and cf and can ONLY be calculated fi you have your cpukey.  cb hash can SOMETIMES be guess via the timing attack but that still leaves cf.
Curiously it seems to have taken a year for new updates to check for ldv update before applying the update.
This is present in the zephyr + falcon boot sector and kernel (not sure which) but applying an update on these boards with no resistor in place throws up e82 iirc.
process has gone from
apply update
call blowfuse routine
finish

to

readcurrentfuse
call blowfuseroutine
readcurrentfuse
if newfuse = oldfuse+1
{
 installupdate
}
else
{
 error
}

[marcel2552]

good to hear that the NXE update preview does works with back ups and IXtreme. Can anyone confirm if multidisk games (blue dragon, Lost odyssey, Invinite undiscovery) are being put in one file and doesnt need disk swappen (not that it boathers me) or is it still lame like in the leaked dashb. update?

[Cpasjuste]

Could someone explain what exactly is the LDV values ?
Also does someone know the NXE LDV values ?

Since i have an XD-mod, i played a bit with mutiples dashboard and LDV value but i'm unable to bypass the e80 error (i do not have thr r6t3 anymore ..)

[Arakon]

good to hear that the NXE update preview does works with back ups and IXtreme. Can anyone confirm if multidisk games (blue dragon, Lost odyssey, Invinite undiscovery) are being put in one file and doesnt need disk swappen (not that it boathers me) or is it still lame like in the leaked dashb. update?

since each disk has its own seperate security data, that's not doable.

[marcel2552]

if thats so, than could it be possible for developers in the future that multidisk games (FF13) can be played with one disk in the tray because i dont think that game will come with less than 4 disks.

[jacksback]

Hey everybody, I'm having a bit of trouble installing the recently leaked NXE preview update. My dashboard is 6717 and no matter what I do I keep getting an E80 error code the moment it finishes updating. I've tried going back to 1888 and updating from there but I still get the same error. The leaked Fall Update works perfectly on this console so I'm really stumped. Xbox has an Infectus version 1 chip installed and a flashed Benq drive. I've tried updating with and without the hard drive connected but still get the same error. Anyone have any theories?

[Arakon]

uhm.. read back like 10 postings? if you have the R6T3 efuse power supply resistor removed, you get E80.

[jacksback]

uhm.. read back like 10 postings? if you have the R6T3 efuse power supply resistor removed, you get E80.

Thanks Arakon, I guess that solves it then

[jz_5_3]

why would u remove r6t3 ? so that the efuse remians the same when using diff dashboards / kernels. more reason to do this if you dont have your cpukey.  ldv (efuse) data is held in the hash of cb and cf and can ONLY be calculated fi you have your cpukey.  cb hash can SOMETIMES be guess via the timing attack but that still leaves cf.
Curiously it seems to have taken a year for new updates to check for ldv update before applying the update.
This is present in the zephyr + falcon boot sector and kernel (not sure which) but applying an update on these boards with no resistor in place throws up e82 iirc.
process has gone from
apply update
call blowfuse routine
finish

to

readcurrentfuse
call blowfuseroutine
readcurrentfuse
if newfuse = oldfuse+1
{
 installupdate
}
else
{
 error
}

okay, based on your new update process, it looks like the update was not applied yet.

so If I put r6t3 back in place, will this fix the problem for my console which has E80 error already? I do not have an infectus, but I am planning to make a tool using a prototype board to flash the nand back to the original 4548 kernel. If my assumption is correct, it will be much simpler and I will not take time to make and test this tool.

[MoDInside]

why would u remove r6t3 ? so that the efuse remians the same when using diff dashboards / kernels. more reason to do this if you dont have your cpukey.  ldv (efuse) data is held in the hash of cb and cf and can ONLY be calculated fi you have your cpukey.  cb hash can SOMETIMES be guess via the timing attack but that still leaves cf.
Curiously it seems to have taken a year for new updates to check for ldv update before applying the update.
This is present in the zephyr + falcon boot sector and kernel (not sure which) but applying an update on these boards with no resistor in place throws up e82 iirc.
process has gone from
apply update
call blowfuse routine
finish

to

readcurrentfuse
call blowfuseroutine
readcurrentfuse
if newfuse = oldfuse+1
{
 installupdate
}
else
{
 error
}

okay, based on your new update process, it looks like the update was not applied yet.

so If I put r6t3 back in place, will this fix the problem for my console which has E80 error already? I do not have an infectus, but I am planning to make a tool using a prototype board to flash the nand back to the original 4548 kernel. If my assumption is correct, it will be much simpler and I will not take time to make and test this tool.

If you don't have a nand backup, you are out of luck, and putting the r6t3 back in place won't make a difference in your case, it has to be there before applying the NXE update.

[jz_5_3]

If you don't have a nand backup, you are out of luck, and putting the r6t3 back in place won't make a difference in your case, it has to be there before applying the NXE update.

I have a nand dump of kernel 4548. After having obtained the cpu key, I removed the r6t3 and then immediately upgraded the console to the latest 67xx kernel.

I am trying to make a nand flash tool using a xilinx fpga programming board. hopefully I will get the 4548 kernel flashed back soon.

by the way, when I do the flash, I should disconnect the console PSU and connect an external voltage source of 3.3v to the nand, right? do I need to disconnect the nand 3.3v pin from the rest of motherboard?

[gigabite]

finally seems some people are on my side  - kind of re-asking what Cpasjuste asked but what are the correct LDV values "supposed" to be...before the NXE and after the NXE (if possible)

gigabite

[MoDInside]

If you don't have a nand backup, you are out of luck, and putting the r6t3 back in place won't make a difference in your case, it has to be there before applying the NXE update.

I have a nand dump of kernel 4548. After having obtained the cpu key, I removed the r6t3 and then immediately upgraded the console to the latest 67xx kernel.

I am trying to make a nand flash tool using a xilinx fpga programming board. hopefully I will get the 4548 kernel flashed back soon.

by the way, when I do the flash, I should disconnect the console PSU and connect an external voltage source of 3.3v to the nand, right? do I need to disconnect the nand 3.3v pin from the rest of motherboard?

you can use the same 3.3v source as shown on the infectus diagram and let the psu connected, or provide an external 3.3v source, by the way, once you update to the new NXE (with r6t3 in place) if you want to go back to 4548 you need to modify the LDV of the 4548 backup.

[MoDInside]

Could someone explain what exactly is the LDV values ?
Also does someone know the NXE LDV values ?

Since i have an XD-mod, i played a bit with mutiples dashboard and LDV value but i'm unable to bypass the e80 error (i do not have thr r6t3 anymore ..)

I believe LDV values are not the same for most people, since they change depending of the updates and the amount of updates done to a particular console, in your case you need to have a r6t3 in order to get the NXE update working, as Shaun said
readcurrentfuse
call blowfuseroutine
readcurrentfuse
if newfuse = oldfuse+1
{
 installupdate
}
else
{
 error
}
there is a check now that complicate things for people that removed the r6t3.
I'll try today to pass the e80 error, putting back the r6t3 and updating the console to NXE from the last dash I updated the console to, I guess this will work, however my LDV should be very different if I never removed r6t3, I hope this won't be a problem, at least not with this update.

[Arakon]

The LDV is basically the amount of fuses blown at the time of a certain update. a console with an old kernel will have an LDV of 0. Anything after that is entirely dependant on how many updates you did, i.e. if you downgraded and then updated again from cd/internet, or if you skipped updates (i.e. went from 4xxx directly to 67xx), etc. each time you update, the LDV value will be moved up by one.

[MoDInside]

Updating to NXE with r6t3 did the trick for the e80 problem.

[jacksback]

Updating to NXE with r6t3 did the trick for the e80 problem.

Can you still downgrade to an exploitable kernel after updating?

[NebUz]

can i use this 10k ohm resistor?

http://www1.conrad.de/scripts/wgate/zcop_b2c/?~template=PCAT_PRODUCT_DETAILS_DOCUMENT&object_guid=654C0D437293F58CE10000000A010221&master_guid=&master_desc=&master_group=&p_load_area=0206710&master_typ=&master_first_row=&master_last_row=&max_tab_items=10&no_brotkrumennavi=&cachedetail=

or this http://www.rapidfiremods.com/product.php?id_product=27

[MoDInside]

Updating to NXE with r6t3 did the trick for the e80 problem.

Can you still downgrade to an exploitable kernel after updating?

Unfortunately not, tried to go back to 4532 and it did not work, it shows e79, with the modified LDV, tried different LDV setups and got 3 red lights (0022), after I get some sleep I'll try some more.