Sponsored Links

Sponsored Links

Page 4 of 20 FirstFirst ... 2345614 ... LastLast
Results 31 to 40 of 191



  1. #31
    Senior Member elser1's Avatar
    Join Date
    Oct 2010
    Posts
    2,419
    Sponsored Links
    Sponsored Links
    is anybody actually working on it with talent? i mean if they knew how to do it i'm sure it wouldn't take long.. and it would be released already. i don't really care, i sort of think we've got enough now.. if you have to have the new games to play buy another ps3 to play them on or upgrade to ofw.. simple really!! i don't want psn on cfw.. theres too many cheats on there now... that's my opinion.

    Quote Originally Posted by Tepoo View Post
    Haha, owned.. i like people who don't know what they are doing, and getting messed up by those fakes
    while i myself find it somewhat amusing inside (being honest) i still feel bad also and want to help..
    Last edited by elser1; 05-28-2011 at 12:55 AM Reason: Automerged Doublepost

  2. #32
    Senior Member HeyManHRU's Avatar
    Join Date
    Dec 2010
    Posts
    3,017
    Sponsored Links
    Sponsored Links
    People need to check with a reliable source before updating Firmwares. Anyone can post on Youtube, Facebook etc...

    If there is a 3.60+ CFW you will see it here (In the news section).

  3. #33
    Junior Member Studs's Avatar
    Join Date
    Jan 2010
    Posts
    48
    Sponsored Links

    CFW 3.61 Can someone confirm?

    Sponsored Links
    Not to up to scratch on the latest methods. So wanted to highlight this link to more talented devs.

    Can anyone confirm this working?

  4. #34
    Forum Moderator PS3 News's Avatar
    Join Date
    Apr 2005
    Posts
    27,733
    I removed the link, it's just spam on a free Web host. If/when something legit is released it will be posted on regular PS3 scene sites.

  5. #35
    Contributor unimatrix725's Avatar
    Join Date
    Jun 2010
    Posts
    20

    Confused I would say in time...

    Quote Originally Posted by bob808 View Post
    I am looking at getting a ps3 slim and lobbing on CFW... I know that right now I would need to ensure the system comes with no newer than 3.55, and I wont be able to play most new games on it due to the 3.6 issues.

    With the iminent new FW coming out with the relaunch of PSN, there is surely going to be more security rolled in... as no-one has yet been able to make a CFW of 3.6, should we be concerned that the good days are coming to an end, or are you hopeful of a 3.7 (or whatever they call it) CFW coming out in the near future?
    They still don't have complete control over the ps3 yet... Also with rumors of the "QA Flag", may bring us a bit closer. Allot of games work on the 3.41 & 3.55 variants, some require a "patched" eboot.bin to work. (example 3.6 fw required games)

    Even yet some of those havent been patched yet. There is a lot of work on the "Linux/OtherOS" front as well, which may bring the devs closer to the 3.6/7x cfw. I would just keep a close eye on the usual trusted ps3 sites, this is one. I have been following the ps3 bandwagon for awhile and still have my blackcat dongle in case.

    I do see a possibility by the end of summer a CFW or at least a solid method of "rigging/patching" all games. Graf is very skilled and a lot of people should try to send him a little bit of money in his fight against sony. (Don't flame me for leaving out the other great ones, excluding GeoDuche - Whom never released anything until a CFW Builder was released, and stirred the shat pot with sony to begin with).

    Deanrr has made great strides in his backup manager, the only one I use, since the others are not working for me that great. Sony is already whispering about a PS4, so its a matter of time, although they said they expect the ps3 to last for 10 years.

  6. #36
    Forum Moderator PS3 News's Avatar
    Join Date
    Apr 2005
    Posts
    27,733

    Arrow Waninkoko Explains How to Develop a PS3 CFW 3.60 / 3.61

    Here is a brief update from PS3 hacker Waninkoko, sharing his thoughts on how to develop a full-fledged PS3 CFW 3.60 / 3.61 followed by some details from groveritos below.

    This news comes following a PlayStation 3 Custom Firmware hybrid update to PS3 CFW VENIX S-PLUS Spoofing 3.65. To quote, roughly translated:

    1. Private keys can not be calculated for any firmware> = 3.56, and are NOT in any site, which for some are private (only the Sony has, and if we make a mistake it was thanks to them which they applied the algorithm So encryption of data and a few mathematical operations could calculate the private keys).

    2. IF you can create a CFW 3.61, the only obstacle is to get the public keys, which can be drawn SI, with varying degrees of difficulty but you can. Each loader is encrypted with a private key and decrypted with the corresponding public key. But the lowest level loader in a FW is encrypted and decrypted with the root key, which is invariably because the root public key used to decrypt the loader is located in the metldr (obviously, the metldr will have to have the public key to decrypt the loader) and metldr NOT be updated in any way, so that the root key can not be changed from one version to another firmware because it is sad if any.

    So if you want to create a CFW of 3.61, changing the LV2 to add new features, we have to go hacking the chain of loaders to get on. Example:

    METLDR -> LV0LDR -> LV0 -> LV1LDR -> LV1 -> LV2LDR -> LV2

    More or less this is the chain of loaders (do not know if there is some small variation in FW 3.61).

    METLDR, as I said, NO you can update.

    METLDR LV0LDR decode the root key (LV0LDR loader is the lowest level, if we do not have to METLDR) and executes it.

    LV0LDR LV0 decode the LV0-key (this key if you can change between versions of firmware as LV0LDR SI is upgradeable and can therefore LV0 encrypt a private key and update LV0LDR to decode it with the new corresponding public key) and runs.

    Decrypts LV0 LV1LDR ....

    LV2 LV2LDR decrypts the lv2-key and executes it.

    Therefore, if you want a CFW, we need to decipher LV0LDR (with the root key, which geohot public and will never change), change LV0LDR change LV0 decryption key (the change of a key that is capable of decoding a LV0 encrypted with a private key that we DO know ... that private key? anyone, as if we generate a key), encrypt LV0LDR with the root key, and we can modify LV0 to our liking and is now LV0 deciphered with a different public key, which we know the private key. And so we change the whole chain to LV2, modify and recifrarlo with the new key we've chosen.

    Well, that's the way broadly told (when I say encrypt / decrypt, I do not mean the contents of the loaders, because it works with AES encryption and symmetric and there is no question of public / private key, but I mean really at the head of such loaders, for signature, which uses RSA keys is where public / private partnerships, with the sole purpose of checking that these loaders have NOT been changed).

    In the case of FW 3.61 the track is a bit more complex as there are RSA public key and AES keys that are easy to obtain, but hey, there are methods to obtain, there are people who have them, and therefore it is not impossible .

    Now, we must take into account that a CFW can be installed only if the console is in a FW 3.55 or lower, because higher versions will make use of a new updater, which verifies the upgrade package (internal data the PUP, so I understand) by checking with new firms (which had not previously existed and are now mandatory) which we have neither the public nor the private key (the public can take, but privately we can forget and here no no chain so we can prevent this ... the updater is a separate application of FW and no longer has to do with the above explained).

    Said this last, some will think that if the upgrade to a CFW 3.56/3.60/3.61 and thou mayest not reinstall any other CFW (that is, you stay forever in that CFW or FW actualizais an official). The answer is yes, but hey, is not inevitable and that, in creating this CFW, we can modify the VSH (or one) to use the old updater (which does not check new firms and therefore we have no obstacle to install new CFW), or modify the APPLDR to allow us to load the new updater but modified to not check signatures (the new updater can be changed, of course, but also need to modify our FW APPLDR currently installed to the recifrar updater with a private key known and APPLDR then be able to decrypt and run).

    And that's all.

    From groveritos: teknoconsolas.es/foro/viewtopic.php?f=214&t=98319&hilit=
    Code:
        SELF header
        elf # 1 offset: 00000000_00000090
        header len: 00000000_00000500
        target offset: 00000000_000001e0
        PhDr offset: 00000000_00000040
        shdr offset: 00000000_0003cc68
        file size: 00000000_0003cab8
        auth id: 1ff00000_01000001 (Unknown)
        vendor id: FF000000
        info offset: 00000000_00000070
        sinfo offset: 00000000_00000140
        offset version: 00000000_00000180
        control info: 00000000_00000190 (00000000_00000070 bytes)
        app version: 1.90.0
        SDK type: Retail (Type 0)
        app type: level 0
    
        Control info
        control flags:
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
        digest file:
        The 8th 7c 62 80 b1 b9 8c 38 e3 2c the 6th August 17, 1972 09 57 25 86 e4 9e
        F5 d8 24 60 94 98 48 4c b6 ae af bd 2c 47 92 ba e5 7b April 1919
    
        Section header
        unk2 unk1 offset encrypted compressed size
        00000000_00010500 00000000_00000ae8 [NO] 00000000 00000000 [YES]
        00000000_00020720 00000000_0001c590 [NO] 00000000 00000000 [YES]
    
        Metadata Encrypted
        Unable to decrypt metadata (not the metadata decrypy)
    
        ELF header
        type: Executable file
        machine: PowerPC64
        version: 1
        PhDr offset: 00000000_00000040
        shdr offset: 00000000_0003c7f8
        entry: 00000000_00037b48
        flags: 00000000
        header size: 00000040
        Head size: 00000038
        program headers: 2
        section header size: 00000040
        section headers: 11
        section header string table index: 10
    
        Program headers
        vaddr offset type paddr
        SPE PPU filesize memsize align RSX
        LOAD 00000000_00010000 00000000_00000000 00000000_00000000
        00000000_00000ae8 00000000_00000ae8 00000000_00010000 rwx --- ---
        LOAD 00000000_00020220 00000000_00020220 00000000_00020220
        00000000_0001c590 00000000_00020f08 00000000_00010000 rwx --- ---
    
        Section headers
        [Nr] Name Type Addr ES Flg Lk Inf Al
        Off Size
        [00] NULL <no-name> 00000000_00000000 00 00 000 00
        00000000_00000000 00000000_00000000
        [01] <no-name> PROGBITS 00000000_00000000 00 08 00 000 WAE
        00000000_00000ae8 00000000_00010000
        [02] <no-name> PROGBITS 00000000_00020220 wa 00 000 08 00
        00000000_00014e10 00000000_00020220
        [03] <no-name> PROGBITS 00000000_00035030 00-00 000 08
        00000000_00002110 00000000_00035030
        [04] <no-name> PROGBITS 00000000_00037140 00 000 16 00 e
        00000000_00000890 00000000_00037140
        [05] <no-name> PROGBITS 00000000_000379d0 00 000 01 00 WAE
        00000000_00000188 00000000_000379d0
        [06] <no-name> PROGBITS 00000000_00037b60 00 000 08 00 e
        00000000_00003b88 00000000_00037b60
        [07] <no-name> PROGBITS 00000000_0003b6e8 00 000 08 00 e
        00000000_00000090 00000000_0003b6e8
        [08] <no-name> PROGBITS 00000000_0003b780 00 000 08 00 e
        00000000_00001030 00000000_0003b780
        [09] 00 ae 00000000_0003c800 NOBITS <no-name> 00,000,128
        00000000_00004928 00000000_0003c7b0
        [10] <no-name> STRTAB 00000000_00000000 00 00 000 01
        00000000_00000047 00000000_0003c7b0
    
        and that of 3.61:
    
        SELF header
        elf # 1 offset: 00000000_00000090
        header len: 00000000_00000500
        target offset: 00000000_000001e0
        PhDr offset: 00000000_00000040
        shdr offset: 00000000_000b51d8
        file size: 00000000_000b4fe8
        auth id: 1ff00000_01000001 (Unknown)
        vendor id: FF000000
        info offset: 00000000_00000070
        sinfo offset: 00000000_00000140
        offset version: 00000000_00000180
        control info: 00000000_00000190 (00000000_00000070 bytes)
        app version: 3.61.0
        SDK type: Retail (Type 0)
        app type: level 0
    
        Control info
        control flags:
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
        digest file:
        The 8th 7c 62 80 b1 b9 8c 38 e3 2c the 6th August 17, 1972 09 57 25 86 e4 9e
        The 8th d9 7c 7d 3b 58 02 74 15 09 65 a0 b6 04 eb b8 42 d5 86 bd
    
        Section header
        unk2 unk1 offset encrypted compressed size
        00000000_00010500 00000000_00000c70 [NO] 00000000 00000000 [YES]
        00000000_00020500 00000000_00094d28 [NO] 00000000 00000000 [YES]
    
        Metadata Encrypted
        Unable to decrypt metadata ------> more of the same
    
        ELF header
        type: Executable file
        machine: PowerPC64
        version: 1
        PhDr offset: 00000000_00000040
        shdr offset: 00000000_000b4d68
        entry: 00000000_00000c60
        flags: 00000000
        header size: 00000040
        Head size: 00000038
        program headers: 2
        section header size: 00000040
        section headers: 10
        section header string table index: 9
    
        Program headers
        vaddr offset type paddr
        SPE PPU filesize memsize align RSX
        LOAD 00000000_00010000 00000000_00000000 00000000_00000000
        00000000_00000c70 00000000_00000c70 00000000_00010000 rwx --- ---
        LOAD 00000000_00020000 00000000_08000000 00000000_08000000
        00000000_00094d28 00000000_00099c50 00000000_00010000 rwx --- ---
    
        Section headers
        [Nr] Name Type Addr ES Flg Lk Inf Al
        Off Size
        [00] NULL <no-name> 00000000_00000000 00 00 000 00
        00000000_00000000 00000000_00000000
        [01] <no-name> PROGBITS 00000000_00000000 00 08 00 000 WAE
        00000000_00000c70 00000000_00010000
        [02] <no-name> PROGBITS 00000000_08000000 wa 00 000 04 00
        00000000_0001657c 00000000_00020000
        [03] <no-name> PROGBITS 00000000_08016580 00-00 000 16
        00000000_000026c0 00000000_00036580
        [04] <no-name> PROGBITS 00000000_08018c40 00 000 16 00 e
        00000000_00076ee8 00000000_00038c40
        [05] <no-name> PROGBITS 00000000_0808fb30 00 000 08 00 e
        00000000_00004188 00000000_000afb30
        [06] <no-name> PROGBITS 00000000_08093cb8 00 000 08 00 e
        00000000_00000080 00000000_000b3cb8
        [07] <no-name> PROGBITS 00000000_08093d40 00 000 08 00 e
        00000000_00000fe8 00000000_000b3d40
        [08] 00 ae 00000000_08094d80 NOBITS <no-name> 00,000,128
        00000000_00004ed0 00000000_000b4d28
        [09] <no-name> STRTAB 00000000_00000000 00 00 000 01
        00000000_0000003d 00000000_000b4d28
    Waninkoko Explains How to Develop a PS3 CFW 3.60 / 3.61

    More PlayStation 3 News...

  7. #37
    Contributor Lacourse2012's Avatar
    Join Date
    Jan 2011
    Posts
    11
    Does anybody honestly think if there is new cfw it will be plastered and passed around? I think its a dumb idea to think that cause then sony can dl it and hack it. I honestly think the new 3.65 is just 3.61 with new psn updates sony is testing us and when we slip up aka post the new cfw they will sue then crack and screw everyone once again.

    So I believe any person saying they have cfw could be lying or could be telling the truth so when it comes to real or fake it could be very well real, unfortunately people will have to go through fakes before real ones if what I say is true which if I was sony or any company that would be the game plan.

    I am actually going through fakes and I got one cfw for 3.61 that gets to 22 % then fails but the fact is the ps3 takes it that's a big start. If I pissed anybody off I'm sorry but it needed to be said and please feel free to pm me and comment I wanna know what others think .

  8. #38
    Senior Member Natepig's Avatar
    Join Date
    Feb 2010
    Posts
    727
    Going through fakes will eventually lead to disaster, if you keep it up. If any other cfw pops up the well known people in scene will give it the thumbs up. Until that happens if ever it would be better not to get sucked in by everyone that posts some bs for attention/site traffic.

  9. #39
    Contributor Lacourse2012's Avatar
    Join Date
    Jan 2011
    Posts
    11
    Well I do agree going through fakes will lead in disaster I believe it should be at your own risk and when the the person rather it be me or someone else finds it we should find away to get it to people but not make it a post or public download just cause I believe sony is waiting for us to slip

  10. #40
    Senior Member elser1's Avatar
    Join Date
    Oct 2010
    Posts
    2,419
    everyone on 3.60+ waiting for cfw may as well upgrade to the newest and play psn as you will not be able to load 3.60+cfw on a ps3 past 3.55.. thanks for this...

    if he can't do it nobody that will release it can..
    Last edited by elser1; 06-08-2011 at 05:20 PM Reason: Automerged Doublepost

 

Sponsored Links
Page 4 of 20 FirstFirst ... 2345614 ... LastLast
Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News