Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: PS3 Firmware Update 3.73 is Now Released, Improves Stability

  1. #1
    Join Date
    Apr 2005
    Posts
    23,636

    PS3 Firmware Update 3.73 is Now Released, Improves Stability

    Following up on their previous PlayStation 3 System Software update, today Sony has quietly released non-mandatory PS3 Firmware update 3.73 in both full and patch update versions which simply improves system stability.

    Download: PS3 System Software Update v3.73 (US - Full) / PS3 System Software Update v3.73 (US - Patch) / PS3 System Software Update v3.73 (EU - Full) / PS3 System Software Update v3.73 (EU - Patch)

    While the official PlayStation Blog doesn't make mention of it, their official PlayStation Twitter feed states the following to quote:

    "A new, non-mandatory PS3 firmware update, v3.73, is now available. Stability during use of certain PS3 format software has been improved."

    From eussNL on the files changes in the PlayStation 3 Firmware 3.73 update: http://pastebin.com/diDXEsfi

    Download: PS3 3.73 FW Update Files CORE OS Package Content

    Files changed:
    Code:
    \dev_flash\ :
    bdplayer
    ps1emu
    ps2emu
    pspemu
    
    \sys\external\ :
    libmp4.sprx
    libspurs_jq.sprx
    libfiber.sprx
    liblv2coredump.sprx
    libadec_internal.sprx
    libmedi.sprx
    libsail_rec.sprx
    libadec.sprx
    libadec2.sprx
    libsync2.sprx
    libsre.sprx
    libsail_avi.sprx
    libhttp.sprx
    libresc.sprx
    libvdec.sprx
    libsail.sprx
    
    \sys\internal\ :
    sys_audio.self
    sys_init_osd.self
    
    \vsh\module\ :
    avc_plugin.sprx
    profile_plugin.sprx
    msmw2.sprx
    videoeditor_plugin.sprx
    avc2_text_plugin.sprx
    friendml_plugin.sprx
    friendim_plugin.sprx
    videoplayer_util.sprx
    mcore_tk.self
    explore_category_friend.sprx
    SacModule.spu.isoself
    videodownloader_plugin.sprx
    hknw_plugin.sprx
    explore_plugin_np.sprx
    sysconf_plugin.sprx
    videoplayer_plugin.sprx
    rec_plugin.sprx
    friendtrophy_plugin.sprx
    vsh.self
    explore_plugin.sprx
    Version strings:
    Code:
    release:03.7300:
    build:52870,20111004:[email protected]
    target:0001:CEX-ww
    security:[email protected]/sdk_branches/release_373/trunk:
    system:48231[MENTION=199279]SyS[/MENTION]/sdk_branches/release_373/trunk:
    x3:[email protected]/branches/target37x:
    paf:[email protected]/branches/target37x:
    vsh:[email protected]/branches/target37x:
    sys_jp:78[MENTION=199279]SyS[/MENTION]_jp/branches/target37x:
    ps1emu:[email protected]/branches/target101/ps1:
    ps1netemu:[email protected]/branches/target370/ps1_net:
    ps1newemu:[email protected]/branches/target202/ps1_new:
    ps2emu:[email protected]/branches/target360/ps2:
    ps2gxemu:14788[MENTION=69462]bran[/MENTION]ches/target360/gx:
    ps2softemu:15529[MENTION=69462]bran[/MENTION]ches/soft190/soft:
    pspemu:[email protected]/branches/target373/psp:
    emerald:3829[MENTION=109881]eme[/MENTION]rald/target37x:
    bdp:[email protected]/prof5/branches/target37x:
    patch::
    auth:52870:
    No need to update ps3tools readself & readself2, it is still 0016 for 3.73 (same as 3.70/3.72) which afaik also means no new keys where added...
    Code:
    struct id2name_tbl t_sdk_type[] = {
    	{0, "Retail (Type 0)"},
    	{1, "Retail"},
    	{2, "Retail (Type 1)"},
    	{3, "Unknown SDK3"},
    	{4, "Retail >=3.40"},
    	{5, "Unknown SDK5"},
    	{6, "Unknown SDK6"},
    	{7, "Retail >=3.50"},
    	{8, "Unknown SDK8"},
    	{9, "Unknown SDK9"},
    	{10, "Retail >=3.55"},
    	{11, "Unknown SDK11"},
    	{12, "Unknown SDK12"},
    	{13, "Retail >=3.56"},
    	{14, "Unknown SDK14"},
    	{15, "Unknown SDK15"},
    	{16, "Retail >=3.60"},
    	{17, "Unknown SDK17"},
    	{18, "Unknown SDK18"},
    	{19, "Retail >=3.65"},
    	{20, "Unknown SDK20"},
    	{21, "Unknown SDK21"},
    	{22, "Retail >=3.70"},
    	{23, "Unknown SDK23"},
    	{24, "Unknown SDK24"},
    	{0x8000, "Devkit"},
    	{0, NULL}
    };
    From Sony PlayStation 3 hacker Mathieulh via IRC on signing PS3 executables for 3.73+ Firmware:
    Code:
    [21:00:58]	<Mathieulh>	selfs are a mess to generate properly because a lot of values need to be calculated from the original elf file
    [21:01:11]	<Mathieulh>	the problem is right now all the public tools use hardcoded values
    [21:01:19]	<Mathieulh>	that are grabbed from various self files
    [21:01:21]	<Mathieulh>	but are not calculated
    [21:01:34]	<Mathieulh>	well that's one of the many problems actually
    [21:01:35]	<jevin> 	Mathieulh, things other than elf offsets?
    [21:01:40]	<Mathieulh>	yah
    [21:02:03]	<Mathieulh>	sony also did some fancy things with the compression self format
    [21:02:12]	<Mathieulh>	where values are off by a certain offset etc etc
    [21:02:38]	<Mathieulh>	if you want to make a proper self tool
    [21:02:44]	<Mathieulh>	you first need to reverse make_fself
    [21:03:06]	<jevin> 	not too hard with hexrays *cough*
    [21:03:09]	<Mathieulh>	that's the initial step
    [21:03:15]	<Mathieulh>	yeah it's not that hard
    [21:03:29]	<Mathieulh>	then you'll figure what a big fck up the self format really is :D
    [21:05:14]	<Mathieulh>	but yeah just my self.cpp is 5 times larger than the entire source for geohot make_self/make_self_npdrm
    [21:05:27]	<Mathieulh>	in terms of lines of code
    [21:05:48]	<Mathieulh>	so his is missing shitloads of stuffs and only relies on hardcoded values
    [21:06:06]	<jevin>	        entire headers copypasta'ed from existing selfs
    [21:06:11]	<Mathieulh>	pretty much yah :D
    [21:06:23]	<Mathieulh>	the ones on the tool I use are generated
    [21:06:32]	<Mathieulh>	as in calculated and generated
    [21:06:36]	<Mathieulh>	from the original elf
    [21:06:52]	<Mathieulh>	btw unself is buggy too
    [21:06:54]	<Mathieulh>	just so you know
    [21:07:16]	<jevin>	        why haven't you labeled the control flags? :)
    [21:08:16]	<Mathieulh>	jevin I didn't feel the need to, I already know what they do anyway
    [21:08:37]	<Mathieulh>	for example 0x40 is root rights, 0x20 is debugger rights and so on
    [21:09:07]	<jevin>	        i'm guessing the self capabilities flags are offset 0x20 in the self header
    [21:09:18]	<Mathieulh>	capabilities aren't in the header
    [21:09:23]	<Mathieulh>	they are part of the metadata
    [21:09:28]	<Mathieulh>	as in, they are encrypted and signed
    [21:10:16]	<jevin>	        offset 0x10 in the section header?
    [21:10:29]	<Mathieulh>	it's after the metadata keys
    [21:10:33]	<jevin>	        no, they wouldn't be per section
    [21:10:50]	<Mathieulh>	as in, right after them
    [21:11:09]	<jevin>	        i see. so unself doesn't have enough fields in the metadata header
    [21:11:35]	<jevin>	        i really should color in the hex values that are mapped to structures in unself vs ones that arent
    [21:11:42]	<jevin>	        seems like it is missing a lot
    [21:11:49]	<Mathieulh>	everything public is missing tons
    [21:12:15]	<Mathieulh>	capabilities are optional mind you
    [21:12:35]	<jevin>	        are they restrictive or permissive?
    [21:13:11]	<Mathieulh>	restrictive
    [21:13:16]	<Mathieulh>	(for most)
    [21:42:15]	<jevin>	        Mathieulh, you said that the geohot npdrm keypair is blacklisted in 3.56
    [21:42:30]	<jevin>	        i couldnt find the decrypted or encrypted metadata keypair in 3.56 files
    [21:42:47]	<jevin>	        where does the blacklisting occur? is it a hash that is blacklisted?
    [21:43:08]	<jevin> 	its interesting to me because we can make our own keypairs now with juan nadie's work
    [21:48:45]	<Mathieulh>	<jevin> Mathieulh, you said that the geohot npdrm keypair is blacklisted in 3.56 <== not only that
    [21:49:03]	<Mathieulh>	geohot stuff doesn't generate some of the npdrm specific values
    [21:49:08]	<Mathieulh>	those were not checked in 3.55
    [21:49:13]	<Mathieulh>	but they are checked in 3.56 now
    [21:49:55]	<jevin>	        Mathieulh, gotcha
    [21:50:09]	<jevin>	        is his keypair actually blacklisted somewhere though?
    [21:50:10]	<Mathieulh>	there is no whitelist for npdrm
    [21:50:22]	<Mathieulh>	so it's actually possible to generate valid npdrm self for 3.56+
    [21:50:42]	<jevin>	        is it a check in appldr?
    [21:50:43]	<Mathieulh>	that tool I made a screenshot of actually does that
    [21:51:02]	<Mathieulh>	jevin yeah, it's enforced by lv1 though
    [21:51:16]	<jevin>	        a hash comparison?
    [21:51:27]	<Mathieulh>	yeah it's a hash
    [21:51:30]	<Mathieulh>	but I won't say more
    [21:51:35]	<jevin>	        ok :)
    [21:51:55]	<Mathieulh>	everything you need is in the 3.56 fw :p
    [21:52:16]	<jevin>	        rgr, i will poke around later
    [21:52:34]	<jevin>	        the checks are unmodified in 3.60+?
    [21:52:43]	<jevin>	        + new keys of course
    [21:52:51]	<Mathieulh>	same checks
    [21:54:53]	<Mathieulh>	jevin you won't get around crafting valid 3.56+ npdrm selfs without a proper makeself tool though
    [21:57:18]	<jevin>	        would SCE make npdrm selfs work if actually signed?
    [21:57:25]	<jevin>	        + crypted
    As always, more details will be posted below as they are available on the update should any hidden features surface.

    [imglink=http://www.ps4news.com/images/img_28374-1.jpg|PS3 Firmware Update 3.73 is Now Released, Improves Stability]http://www.ps4news.com/images.php?sm=1&f=img_28374-1.jpg&w=500&h=400[/imglink]
    More PlayStation 3 News...

  2. #2
    GrandpaHomer Guest
    Stability my bottom ... they're so desperately trying to patch this full of hole sinking ship ... it's just pathetic

  3. #3
    darkanima9 Guest

    Smile

    improves mean to not play copy games

  4. #4
    shummyr Guest
    Quote Originally Posted by GrandpaHomer View Post
    Stability my bottom ... they're so desperately trying to patch this full of hole sinking ship ... it's just pathetic
    They are trying to cover another exploit as GrandpaHomer pointed out to the point that it is just downright pathetic and pitiful.

  5. #5
    Join Date
    Apr 2005
    Posts
    23,636
    That, plus it's getting annoying to many I'm sure to keep downloading updates that don't bring any new features.

  6. #6
    momipopi Guest
    i boxed my ps3 until theres another cfw... bought myself a jtagged xbox...

  7. #7
    spunkybunny Guest
    Quote Originally Posted by darkanima9 View Post
    improves mean to not play copy games
    You cant play copied games with ANY OFW above 3.55 so wtf are you going on about?

    Quote Originally Posted by momipopi View Post
    i boxed my ps3 until theres another cfw... bought myself a jtagged xbox...
    ALL Xbox360's can be jtagged now.

  8. #8
    Mantagtj Guest
    Just makes it look like $ony is actually working... when they just doss about all day..."what shall we do today?? they said... lets do another firmware update they said... okay if we make the stars on the intro slightly brighter ...right thats update 3.73.003.2.1" PMSL... it doesn't affect me $ony... kiss it !!

  9. #9
    Natepig Guest
    Seeing as its not mandatory that would suggest that its not security related, and as they say for stability.

  10. #10
    NTA Guest
    lol 4071mb / 298GB

    wish I had that much space

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •