[Elegant]

Originally Posted by pip1 Why can we change it and not sony? doesn't make sence either neither of us can change it or both of us can or am I missing somthing, Is it behind e-fuses but acessible through jtag? I thought the whole point was once we get the keys from the beginning of the boot process that NO ONE can change we can alter everything from there on which is the entirety of the firmware updates.

AFAIK If Sony made such an update it would have to know the bootldr key. But it can't because it's different per console! In the off chance they did this would involve an update specifically for ONE console. This also wouldn't make any difference since the hardware only responds to this one key even if they updated the bootldr I could still just as easily create my own yet again since the key cannot be altered, EVER.

[pax109]

So we know the bootldr is encrypted at the factory with the unique per console keys, what is the chance of the decrypted bootldr being the same for each console with the only difference being the keys used to encrypt it? Could if it was ever released by someone with the required hardware to dump it and decrypt it with their matching per console keys be patched and re-encrypted with your own dumped per console key?

[VIRGIN KLM]

Originally Posted by Elegant So you're proposing we can sign the bootldr with the console key? If we can (I believe it's the same key) and it runs then I don't see how you can't. But consider this: If you can modify the bootldr and sign it AND it cannot be altered with updates. Why not write one to dump lv0 keys while on 3.60? (This requires soldering since we can't use linux or SSH, or its possible since it's not updated to create one that will dump to USB or something and just have it do that then update to 3.60) Then maybe write a lv0 to dump everything else? We have the majority of the needed code from Mathieulh am I wrong?

I just meant that something like bootmii on PS3 would be groundbreaking in the PS3 community, possibly one of the top 5 best ever things materialized in PS3 community. It would alow you to avoid 75% of todays bricks plus it would save up reaaally much time from doing update processes plus developers could use it to test safely their code without having extremelly high risk of a brick that would require a hardware solution to bring back the console to life.
Think of it like a super advanced with more features Pandora Battery of PSP but for PS3 instead.

[TizzyT]

Hmm, this is super exciting, I don't get much of it now but I have been doing further research into similar things as this, hopefully I will eventually completely understand the whole thing., although I doubt I will ever be able to contribute to something so complex (or at least that's how I see it now). Really really great and exciting stuff. Man I wish I was born in a more technically educated place......FML.

[pip1]

whats stopping sony from reading the per console key during an update and changing bootloader? bootloader is on the flash memory so it can be changed and if we can use software to read the key why can't sony?

I love when people say can't because in life almost allways you can no matter what it is as long as your smart and try.

[Elegant]

Originally Posted by pip1 whats stopping sony from reading the per console key during an update and changing bootloader? bootloader is on the flash memory so it can be changed and if we can use software to read the key why can't sony? I love when people say can't because in life almost allways you can no matter what it is as long as your smart and try.

I also just stated this... Try rereading my post... I stated that it is IMPOSSIBLE (as in NOT POSSIBLE!) to change the console key therefore if they by some miracle could change the bootldr they can go ahead and change as many times as they feel fit to. Unfortunately for them I still know my key and can change it back when the update is done. They cannot block this, it would require them to physically come to my house disassemble my PS3 and change my parts.

@VIRGIN KLM I agree it would be helpful, in fact after posting I realized the easiest way for us to get the 3.6x+ keys safely could be to enable dual booting because we'll have the ability to explore the 3.60 side of the boot from 3.55 side. Thus skipping the need to solder and edit from that end. Also if I'm not mistaken waninkoko released a flash creator that will create a dev_fflash (that will not conflict with dev_flash), I'm guessing that would be a great place to start

[hackeyking]

Lets hope we still have talented people (who havent been pushed away by stupid comments and small children) who can get us somewhere....

[hackeyking]

Originally Posted by zaeReiroh2 For us small people, this will do nothing, the devs will be able to play with it and we will, benefit from the end results, so don't worry about it until later

im no Hobbit...

[GregoryRasputin]

lol @hackeyking and @nzie , the user @zaeReiroh2 is a spam bot.

[hackeyking]

Must get to grips better with this place!