(adsbygoogle = window.adsbygoogle || []).push({}); can we expect a 3.56 downgrade/cfw in the near future,because a lot of people like me are stuck with 3.56(i have v1).maybe now is the right time to create a cfw/downgrade because sony are fighting lg..

The only downgrade I'm aware of requires you to brick your ps3.
Should have stuck with 3.55 :\

PS: If you want people to help you, you shouldn't come off as a l33cher :p

well,i didn't know much about ps3 hacking and cfw's then...
oh well,i'll just have to wait

Yeah that one guy posting shit about his teams CFW, and a downgrade possibility, don't even try. It would have been posted here, if it worked. Despite him saying 'we are new, so we're trying to get noticed', or wtfe he said, don't buy it. Until someone with a convincing argument did this, and it DID, in fact, work, then I'll give it a shot. Until then, no. Just a mother effing no. I bypassed their gay 3.60 update, because I don't give a flying **** about using their cloud feature. We shall see...

geohot is actually helping the impossible ... making them look dumn



GEOHOT SAYS....

#795944 - Pastie
geohot: well actually it's pretty simple
geohot: i allocate a piece of memory
geohot: using map_htab and write_htab, you can figure out the real address of the memory
geohot: which is a big win, and something the hv shouldn't allow
geohot: i fill the htab with tons of entries pointing to that piece of memory
geohot: and since i allocated it, i can map it read/write
geohot: then, i deallocate the memory
geohot: all those entries are set to invalid
geohot: well while it's setting entries invalid, i glitch the memory control bus
geohot: the cache writeback misses the memory
geohot: and i have entries allowing r/w to a piece of memory the hypervisor thinks is deallocated
geohot: then i create a virtual segment with the htab overlapping that piece of memory i have
geohot: write an entry into the virtual segment htab allowing r/w to the main segment htab
geohot: switch to virtual segment
geohot: write to main segment htab a r/w mapping of itself
geohot: switch back
geohot: PWNED
geohot: and would work if memory were encrypted or had ECC
geohot: the way i actually glitch the memory bus is really funny
geohot: i have a button on my FPGA board
geohot: that pulses low for 40ns
geohot: i set up the htab with the tons of entries
geohot: and spam press the button
geohot: right after i send the deallocate cal


wich means it is POSSIBLE for 3.56 cfw ..(if you bypassed 3.60) YOU can jailbreak your system when they figure this out i am gonna post a thread about this soon with more info so KEEP YOUR EYES PEELED..
:hitman:

Go make it yourself.

well done dipsh*t you screwed it up then because if your on 3.56 v1 your sorted

Please explain

Maybee it will hapen soon cuz many are stuck in servce mode :p lol but now 3.60 is out im not gunna update

Yea, I'd like to know what this "sorted" means as well...

Does it mean that Sony took note of all MAC addresses of PS3's in OFW 3.56 v1+? Or is it that the Keys and loaders were changed? I know they were changed, just don't know when they were. From what I understand, I'd say that it means the loaders were changed, and keys signed in 3.56+.

As for staying on topic, I think that a 3.56 downgrade should be worked on by one team, since the keys are out, even though it's 3.55 with slight changes in security. Many people would appreciate this, as 3.60 is going to take a while to develop a downgrade/CFW because the keys and loaders were definitely changed and no longer use the metldr or the other ldr (forgot the name, sue me like Sony likes to...).

I know quite a few people that would appreciate a 3.56 something or other, because of the changes in 3.60. Either way, Sony's starting to crack down, but I don't think that's going to stop people from starting over with 3.60.