Ps3 Service Mode Jig Files Free Apps
2021年7月22日Download here: http://gg.gg/vhe36
*Ps3 Service Mode Jig Files Free Apps Downloads
*Ps3 Service Mode Jig Files Free Apps Free
First things first, the title says “why I don’t like the hermes Payload” so this has nothing to do with Hermes himself. I don’t know him, I never spoke to him, so I don’t know what kind of person he is and so I have no opinion on him personally. Now, I want to make some things clear, I’ve seen a lot of people criticize me for ‘bashing Hermes’, and many people seem to think that I’m trying to say “I’m better than him” or something. Also, it looks like I created some confusion with my comments from my previous blog post. So I want to apologize and make sure there is no confusion anymore : When I said that the hermes payload is ‘dangerous’, people misunderstood me. no it is not specifically dangerous for your PS3, it won’t brick it or anything, the only ‘danger’ there is, is that it could (in some situations) crash… then you’d need to reboot, that’s it. so don’t freak out about his work being harmful or anything, because as far as I know, it’s not! Some people also told me “give credit where its due”, and I want to do it, I’ve always given credit to people, every time I achieved something, I gave credit to those who helped me achieve it. I’m not looking for fame here (if I did, I would have announced PL3’s release 3 weeks ago when I created it) I’m just having some fun in my free time doing something that I like. Hermes did contribute some nice things, and I appreciate what he did, mainly he figured out how to fix the controller issues with some games, that was something very difficult to fix and I’m surprised at how fast he came up with a solution and it was a smart solution and all I can say is “good job”. The other stuff he did in his payload, I don’t like that much, and that’s what I want to cover in this post. I may have been ‘harsh’, but I don’t see the point in trying to be diplomatic, I’m a programmer, not a politician. I don’t like his code, and I speak my mind, I’m being honest, and I’m not trying to criticize him without any reason, as far as I know, I’ve stayed respectful and that’s all that matters to me. To those who don’t want to know about all the technical details, let me ‘conclude’ here by saying that if the hermes payload works for you, then good, use it, I’m not telling people to stop using it, I’m not saying that PL3 works better either, maybe his payload works better in some situations, maybe not, but overall, the user’s choice should always be “whatever works for you”. The PL3 initiative is about having a standard repository for payloads, and having a common code base for everyone to work on, so in the future, PL3 might evolve faster and have more features, or maybe it won’t, the thing to note is that it’s better for payload developers to base their work off PL3. But again, this is meaningless for most users, apart from maybe clearing up the confusion about all these payloads and nobody knows which one to use. Also, I talked about PL3, which is a common repository for contributors to work on, people seem to have nicknamed it “kakaroto’s payload” or “kakaroto’s pl3”, but I never said it was my payload, PL3 is PL3, it’s not all my work, and if you look at the commit log, you will see that I’m not the only contributor to it. PL3 itself integrates patches and solutions provided by Hermes, Waninkoko and Mathieulh, I improved some of their patches to make sure it works better for non-3.41 firmwares, but it’s still credited to be their work. PL3 is not my payload, PL3 is a payload repository for everyone. Also, PL3 as a project is a repository containing multiple payloads (default one, development one, dump_lv2, dump_elfs, etc.). PL3 is not perfect, nothing in the world is perfect, so it might have bugs, it might not work for some people, who knows what might happen. But I never said that it was perfect, so people should stop thinking that I said that. It’s written more cleanly, it’s better in terms of the infrastructure behind it, but that’s the only thing I can vouch for. Also for those complaining about me adding a donate button to the blog post, I don’t see how that’s relevant, I’m not begging people for money (and I haven’t received any donations in the last ~3 weeks just so you know). If you don’t want to donate, then don’t, no reason to bitch about it. I’ve put the button there so that people who appreciate the work and want to donate something have a way of doing it. I asked for donations before because I needed to buy a PS3 for development, I already raised enough money to buy it, so I don’t need any more donations, so I’m not asking people for donation money anymore, as simple as that. Anyways, here are the more detailed/technical explanations on the reasons why I don’t like his payload : First, the code is not clean, it’s unmaintainable. The fact that he gives his source code in .rar files instead of a git fork is the biggest issue I have with it. And yes, that does not matter for users, it only matters for developers. The problem with his method of delivery is that you have no way of knowing what he based his code off, so it’s hard to figure out what he changed. also, when you find out his base, and do a diff, you get a huge diff for everything he did, all in one shot, and then you have to reverse engineer it to understand what he patched. That’s complicated and annoying for developers! For those who follow my twitter, you can see how many commits I do, I always like having “small commits” because each commit becomes independent, self explanatory and easy to review. It also makes things easier to integrate, if you want a specific thing, you just merge/cherry-pick that single commit, instead of copy/pasting code, and editing it to remove the clutter. The other reason I like git is that if he used it and I merge a commit from him, then the code stays credited to his name in the commit log, it allows me to have his code without ‘taking ownership’ of his work, it allows everyone to be credited for what they did, and I think it’s the first thing to have for an open source and community project. The reason why I said his code could crash is because his payload got too big and couldn’t fit anymore in the allocated memory we have in the kernel (1296 bytes), so he decided to just move the code to a random position (0x7fff000 I think). This means that his payload will work as long as no application, game or kernel allocates memory which ‘randomly’ ends up in that area. if it does, then the payload would get overwritten and the kernel will crash. The proper way of doing it (PL3 does that) is to allocate memory during the initialization of the payload, copy the functions we want in that memory that we own, and write those functions to be position independent so they would work no matter where they are placed in RAM. Another reason is the way his syscall8 works, I tried to read his assembly and reverse engineer it, and I seriously was lost and couldn’t understand what was happening. there are no comments (you’ll notice that my payload has a comment on almost every instruction), so how can I integrate his syscall if i don’t even know what it does… if at least it was on git, I could see the commit messages and understand what each chunk of code did, but he doesn’t use git, so… The way he fixed the controller issue was also not very good, he patched two offsets to jump to a function that decides on some kind of enum on what response to return and you controlled that with his own system call 8. why do something like that? it makes the fix dependent on people using this new syscall, and it’s useless when you can just patch it directly to return the right value. I also didn’t like the fact that his code became a mess that is 3.41 independent, and it would have taken a huge amount of work just to try to make it work again on 3.15. I already spent time cleaning up the payloads and making them work for older firmwares, so why fork and write code that doesn’t integrate that, it just makes collaboration harder. There’s also the whole syscall 35 versus 36 issue, but that has nothing to do with his payload since I added sc35 after he released his payload. It’s not about his payload being bad because it doesn’t support it, it’s simply about PL3 having a ‘superior’ (if I may say so) system call. What it means for users? nothing at the moment, maybe it will be used for doing fancier stuff later on, maybe you can map a game to your bluray and a different game to /app_home, that could be useful for users, but for now, it’s simply more flexible and cleaner code. There are many other small things that I didn’t like, but it mostly just summarizes to “the code is not clean and it’s unmaintainable” and “he doesn’t use git”. Like I said, if you don’t care about that, then I see no reason for you not to use his payload. It doesn’t mean either that he’s not skilled, it simply means that he may lack experience in code sharing and experience in open source. But that doesn’t make his work any less valuable. I hope this clears things up a bit. I criticized his work, said what I thought of it and people over reacted, I wanted to make sure people didn’t misunderstand me, and didn’t think I don’t respect Hermes for what he’s done already. Everything else is just drama and people trying to get attention. If this post stirs up even more trouble, then so be it, I don’t think I have much more to say. I said what I think, people should take it or leave it. I do not however tolerate people insulting me for no reason at all. So please, criticize me all you want, just stay respectful. Thank you, KaKaRoTo
*When you run the app it will beep once and reboot if successful. Three beeps indicates a failure, report the contents of factory.txt in this thread for help. (Factory.txt will save to the USB flash if you put on in the right most USB port of the PS3.) At this point you will come back up in Factory Service Mode (FSM).
*Brandonw has released PS3Jig for the PS3. PS3Jig is a homebrew program for the PSP that emulates the official Sony “jig” stick for entering Factory/Service mode. All you need to do is attach a USB cable between your PS3 and PSP, run the program, and turn on your PS3, just like any other downgrade/service mode method.
Superceded by : lv2diag remarry (mirror)
http://pastie.org/5138910 :
In this tutorial, I will show you how to get free wii games using USB Loader GX!IMPORTANT UPDATE: I will no longer be providing links to ROM/emulator website. The USB Loader GX is a popular game loader which allow you to load games from a USB drive. LINKS Homebrewing your wii - https://youtu.b. Installing usb loader gx wii. I’ve been very happy with my USBLoader GX setup, but it occurred to me that since my Wii always boots directly into the loader (thanks to Priiloader), I was neglecting my VC and WiiWare games! A quick Google search later and I found this WiiHacks guide for creating ISO forwarders to. Downloading Extract USB Loader GX and put it in the apps folder on your USB drive or SD card. Insert your USB drive, and SD card if you’re using one, into your Wii and launch USB Loader GX from the Homebrew Channel. In my experience, using IOS250 works best for WiiWare/VC and IOS249 works best for disc games. I had that same problem before messing around with this, eventually I settled on using IOS250 as the global IOS in USB Loader GX, then enabled IOS249 manually on whichever disc games weren’t working properly.
Apps for your PlayStation 3. With social networks, music, movies and catch-up TV, you can do it all on your PS3. Expand your entertainment. Pick your perfect PS3 app. With Spotify now available on PlayStation Music, you have a new way to enjoy streaming music on your PlayStation 3. Put unrar’ed remarry files on a blank USB stick & add a 2.30 (PS3 FAT only) or 3.15 (PS3 Slim) PUP Put in the service mode JIG/dongle and get into factory service mode. Put the created USB stick into port 0 (closest to the reader) and run. Drive Init Executing File:PS3 Remarry DriveInit Executing.jpg means it is starting the remarry process. Put console in service mode with JIG (in case you left service mode and ran the prepatched firmware in normal mode) Use normal lv2diag.self and unpatched official firmware (e.g. 3.55) on USB Mass Storage device in root and let the system reinstall that in factory service mode (FSM). After installation is finished console will turn off.
3.30 pup (mirror) / remarry files 3.55 (mirror)
old page kept for historic reference.
*1Remarry BluRay drive
*1.4CFG Settings
*1.5Remarry breakdown
*1.5.1full CFG breakdown
*1.63.55 downgrader
*1.73.50 downgrader
*1.8OtherRemarry BluRay drive[edit]
Hardware is interlocked on the PS3, so exchanging a bluray drive from one unit to another requires remarriage of the components.Procedure[edit]
*Make sure you don´t have any CD/DVD/BD on the drive
*Put unrar’ed remarry files on a blank USB stick & add a 2.30 (PS3 FAT only) or 3.15 (PS3 Slim) PUP
*Put in the service mode JIG/dongle and get into factory service mode.
*Put the created USB stick into port 0 (closest to the reader) and run.
*Drive Init Executing File:PS3 Remarry DriveInit Executing.jpg means it is starting the remarry process
*Drive Init Failed with big pink letters ’NG’ (No Good!) File:PS3 Remarry Pink-NG DriveInit Fail.jpg means the process failed. Most likely solved by first downgrading the console or fix the communication issue with the drive.
*After you run the initial remarry process, do not take it out of factory service mode.
*Put a BD movie disc in and run it on the PS3. (This restores your DRL files!)
*Then you can take it out of factory service mode.
*Launch as normal.Needed files on USB stick[edit]
dev_usb000.rar (856.52 KB) :
for comparison:Additional Notes on Remarry Procedure[edit]
*2.30 and 3.15 are not ’special’, iirc firmware <=3.30 should be fine (>3.30 won’t work) to use as reinstaller PUP.
*Lv2diag.self for 3.55 downgrade has BD patched out. So in case you have a 3.55 console you wish to remarry, you can either:
*lv2diag.self downgrade it first to 3.50 or lower and then use the remarry procedure ; or (if possible):
*QA-flag extra it, then QA downgrade via recovery to <3.50 followed by remarry procedure.
*without working BD packages won’t work :(
*If console was previously downgraded from >= 3.56:
*syscon hashes must be either patched out (lv1 patches)
*e.g. Rogero_CFW3.50_LV1Patched_NoBD_for_Re-marry.PUP
*or dehashed (double FSM)
Alternative method for restoring DRL : [Downgrade BluRay Playback Issue]
If you have problems with remarry, but still get a good ’Drive Init’ message or where able to restore the original DRL backup from dev_flash3 of that BD-drive and it still does not work: try Restore Filesystem in the Recovery Menu.CFG Settings[edit]
Remark: For some reason people are not looking in the CFG file for other selectable options.
e.g. (line 269 until line 280 quoted):
This will remarry the drive to the console and remake the DRL files (setting it to 0 will NOT remarry it)
This will install the firmware PUP that is on the USB stick in root (setting it to 0 will NOT install firmware)Warning about editing CFG[edit]
Default is both options set to 1 and is confirmed to work on both PS3 FAT (NAND and NOR) and PS3 Slim (NOR). Strange things can happen when messing with the CFG and using nonvalid values or combinations.
Remarry breakdown[edit]full CFG breakdown[edit]Drive Init[edit]
This will remarry the drive to the console and remake the DRL files (setting it to 0 will NOT remarry it) Install Systemsoftware[edit]
This will install the firmware PUP that is on the USB stick in root (setting it to 0 will NOT install firmware) freebdp[edit]
If enabled will give error 0x80010006 (file does not exist) and results in ’Initialize revocation list FAIL’. It needs free_bdp.self to be presentInstall Systemsoftware Updater[edit]
the filename of the SELF used for updating the firmware
lv2diag.self (remarry)[edit]manufacturing_updater_for_reset.self (remarry)[edit]
Free software il signore dell 60olimpo zeus by tabor rd..
fdm_spu_module.self (remarry)[edit]
3.55 downgrader[edit]Lv2diag.self (file1 - 3.55 downgrader)[edit]Lv2diag.self (file2 - 3.55 downgrader)[edit]
(same as 3.50--)
3.50 downgrader[edit]Lv2diag.self (file1 - 3.50 downgrader)[edit]Lv2diag.self (file2 - 3.50 downgrader)[edit]
(same as 3.55--)
Other[edit]manufacturing_updater_for_reset.self (ifcaro @ elotrolado)[edit]CONSOLE_SETUP_CEX.SIG.XML (ObjectiveSuites files)[edit]Ps3 Service Mode Jig Files Free Apps Downloads
Ps3 Service Mode Jig Files Free Apps FreeGeneralBluedisk EID0 reDRM·Boot Order·Bugs & Vulnerabilities·Dumping Bootldr·Dumping Metldr·Files on the PS3·KaKaRoTo_Kind_of_´Jailbreak´·PS3Cobra Payload Reverse Engineering·PS3UserCheat·QA Flagging·ReDRM / Piracy dongles·Revoke List·RSOD Fix·rtcalarm.dat·Whitelisting·VTRMHypervisorHypervisor Reverse Engineering·Repository NodesServicesAppliance Information Manager·AV Manager·Dispatcher Manager·Factory Data Manager·Indi Info Manager·SB Manager·SC Manager·Secure LPAR Loader·Secure Profile Loader·Secure RTC Manager·Security Policy Manager·Storage Manager·Update Manager·Updater Frontend·USB Dongle Authenticator·User Token Manager·Virtual TRM ManagerPlugin
Interfacesap_plugin·audioplayer_plugin·audiop_plugin_dummy·audiop_plugin_mini·auth_plugin·autodownload_plugin·autoupdateconf_plugin·avc_plugin·avc_util·avc2_game_plugin·avc2_game_video_plugin·avc2_text_plugin·bdp_disccheck_plugin·bdp_plugin·bdp_storage_plugin·campaign_plugin·category_setting_plugin·comboplay_plugin·custom_render_plugin·data_copy_plugin·deviceconf_plugin·dlna_plugin·download_plugin·dtcpip_util·edy_plugin·esehttp·eseibrd·eseidle·eselock·eula_cddb_plugin·eula_hcopy_plugin·eula_net_plugin·explore_plugin·explore_plugin_ft·explore_plugin_game·explore_plugin_np·filecopy_plugin·friendim_plugin·friendml_plugin·friendtrophy_plugin·game_ext_plugin·game_indicator_plugin·game_plugin·gamedata_plugin·gamelib_plugin·gameupdate_plugin·hknw_plugin·idle_plugin·impose_plugin·kensaku_plugin·msgdialog_plugin·mtpinitiator_plugin·musicbrowser_plugin·nas_plugin·netconf_plugin·newstore_plugin·np_eula_plugin·np_matching_plugin·np_multisignin_plugin·np_sns_plugin·npsignin_plugin·np_trophy_ingame·np_trophy_plugin·osk·oskfullkeypanel·oskpanel·pesm_plugin·photo_network_sharing_plugin·photolist_plugin·photoviewer_plugin·playlist_plugin·poweroff_plugin·premo_plugin·premo_game_plugin·print_plugin·profile_plugin·ps3_savedata_plugin·ps3_savedata_plugin_game·ps3_savedata_plugin_psp·rec_plugin·regcam_plugin·remotedownload_plugin·sacd_plugin·scenefolder_plugin·screenshot_plugin·software_update_plugin·soundvisualizer_plugin·strviewer_plugin·sysconf_plugin·system_plugin·thumthum_plugin·upload_util·user_info_plugin·user_plugin·videodownloader_plugin·videoeditor_plugin·videoplayer_util·videoplayer_plugin·vmc_savedata_plugin·wboard_plugin·webbrowser_plugin·webbrowser
https://diarynote-jp.indered.space
*Ps3 Service Mode Jig Files Free Apps Downloads
*Ps3 Service Mode Jig Files Free Apps Free
First things first, the title says “why I don’t like the hermes Payload” so this has nothing to do with Hermes himself. I don’t know him, I never spoke to him, so I don’t know what kind of person he is and so I have no opinion on him personally. Now, I want to make some things clear, I’ve seen a lot of people criticize me for ‘bashing Hermes’, and many people seem to think that I’m trying to say “I’m better than him” or something. Also, it looks like I created some confusion with my comments from my previous blog post. So I want to apologize and make sure there is no confusion anymore : When I said that the hermes payload is ‘dangerous’, people misunderstood me. no it is not specifically dangerous for your PS3, it won’t brick it or anything, the only ‘danger’ there is, is that it could (in some situations) crash… then you’d need to reboot, that’s it. so don’t freak out about his work being harmful or anything, because as far as I know, it’s not! Some people also told me “give credit where its due”, and I want to do it, I’ve always given credit to people, every time I achieved something, I gave credit to those who helped me achieve it. I’m not looking for fame here (if I did, I would have announced PL3’s release 3 weeks ago when I created it) I’m just having some fun in my free time doing something that I like. Hermes did contribute some nice things, and I appreciate what he did, mainly he figured out how to fix the controller issues with some games, that was something very difficult to fix and I’m surprised at how fast he came up with a solution and it was a smart solution and all I can say is “good job”. The other stuff he did in his payload, I don’t like that much, and that’s what I want to cover in this post. I may have been ‘harsh’, but I don’t see the point in trying to be diplomatic, I’m a programmer, not a politician. I don’t like his code, and I speak my mind, I’m being honest, and I’m not trying to criticize him without any reason, as far as I know, I’ve stayed respectful and that’s all that matters to me. To those who don’t want to know about all the technical details, let me ‘conclude’ here by saying that if the hermes payload works for you, then good, use it, I’m not telling people to stop using it, I’m not saying that PL3 works better either, maybe his payload works better in some situations, maybe not, but overall, the user’s choice should always be “whatever works for you”. The PL3 initiative is about having a standard repository for payloads, and having a common code base for everyone to work on, so in the future, PL3 might evolve faster and have more features, or maybe it won’t, the thing to note is that it’s better for payload developers to base their work off PL3. But again, this is meaningless for most users, apart from maybe clearing up the confusion about all these payloads and nobody knows which one to use. Also, I talked about PL3, which is a common repository for contributors to work on, people seem to have nicknamed it “kakaroto’s payload” or “kakaroto’s pl3”, but I never said it was my payload, PL3 is PL3, it’s not all my work, and if you look at the commit log, you will see that I’m not the only contributor to it. PL3 itself integrates patches and solutions provided by Hermes, Waninkoko and Mathieulh, I improved some of their patches to make sure it works better for non-3.41 firmwares, but it’s still credited to be their work. PL3 is not my payload, PL3 is a payload repository for everyone. Also, PL3 as a project is a repository containing multiple payloads (default one, development one, dump_lv2, dump_elfs, etc.). PL3 is not perfect, nothing in the world is perfect, so it might have bugs, it might not work for some people, who knows what might happen. But I never said that it was perfect, so people should stop thinking that I said that. It’s written more cleanly, it’s better in terms of the infrastructure behind it, but that’s the only thing I can vouch for. Also for those complaining about me adding a donate button to the blog post, I don’t see how that’s relevant, I’m not begging people for money (and I haven’t received any donations in the last ~3 weeks just so you know). If you don’t want to donate, then don’t, no reason to bitch about it. I’ve put the button there so that people who appreciate the work and want to donate something have a way of doing it. I asked for donations before because I needed to buy a PS3 for development, I already raised enough money to buy it, so I don’t need any more donations, so I’m not asking people for donation money anymore, as simple as that. Anyways, here are the more detailed/technical explanations on the reasons why I don’t like his payload : First, the code is not clean, it’s unmaintainable. The fact that he gives his source code in .rar files instead of a git fork is the biggest issue I have with it. And yes, that does not matter for users, it only matters for developers. The problem with his method of delivery is that you have no way of knowing what he based his code off, so it’s hard to figure out what he changed. also, when you find out his base, and do a diff, you get a huge diff for everything he did, all in one shot, and then you have to reverse engineer it to understand what he patched. That’s complicated and annoying for developers! For those who follow my twitter, you can see how many commits I do, I always like having “small commits” because each commit becomes independent, self explanatory and easy to review. It also makes things easier to integrate, if you want a specific thing, you just merge/cherry-pick that single commit, instead of copy/pasting code, and editing it to remove the clutter. The other reason I like git is that if he used it and I merge a commit from him, then the code stays credited to his name in the commit log, it allows me to have his code without ‘taking ownership’ of his work, it allows everyone to be credited for what they did, and I think it’s the first thing to have for an open source and community project. The reason why I said his code could crash is because his payload got too big and couldn’t fit anymore in the allocated memory we have in the kernel (1296 bytes), so he decided to just move the code to a random position (0x7fff000 I think). This means that his payload will work as long as no application, game or kernel allocates memory which ‘randomly’ ends up in that area. if it does, then the payload would get overwritten and the kernel will crash. The proper way of doing it (PL3 does that) is to allocate memory during the initialization of the payload, copy the functions we want in that memory that we own, and write those functions to be position independent so they would work no matter where they are placed in RAM. Another reason is the way his syscall8 works, I tried to read his assembly and reverse engineer it, and I seriously was lost and couldn’t understand what was happening. there are no comments (you’ll notice that my payload has a comment on almost every instruction), so how can I integrate his syscall if i don’t even know what it does… if at least it was on git, I could see the commit messages and understand what each chunk of code did, but he doesn’t use git, so… The way he fixed the controller issue was also not very good, he patched two offsets to jump to a function that decides on some kind of enum on what response to return and you controlled that with his own system call 8. why do something like that? it makes the fix dependent on people using this new syscall, and it’s useless when you can just patch it directly to return the right value. I also didn’t like the fact that his code became a mess that is 3.41 independent, and it would have taken a huge amount of work just to try to make it work again on 3.15. I already spent time cleaning up the payloads and making them work for older firmwares, so why fork and write code that doesn’t integrate that, it just makes collaboration harder. There’s also the whole syscall 35 versus 36 issue, but that has nothing to do with his payload since I added sc35 after he released his payload. It’s not about his payload being bad because it doesn’t support it, it’s simply about PL3 having a ‘superior’ (if I may say so) system call. What it means for users? nothing at the moment, maybe it will be used for doing fancier stuff later on, maybe you can map a game to your bluray and a different game to /app_home, that could be useful for users, but for now, it’s simply more flexible and cleaner code. There are many other small things that I didn’t like, but it mostly just summarizes to “the code is not clean and it’s unmaintainable” and “he doesn’t use git”. Like I said, if you don’t care about that, then I see no reason for you not to use his payload. It doesn’t mean either that he’s not skilled, it simply means that he may lack experience in code sharing and experience in open source. But that doesn’t make his work any less valuable. I hope this clears things up a bit. I criticized his work, said what I thought of it and people over reacted, I wanted to make sure people didn’t misunderstand me, and didn’t think I don’t respect Hermes for what he’s done already. Everything else is just drama and people trying to get attention. If this post stirs up even more trouble, then so be it, I don’t think I have much more to say. I said what I think, people should take it or leave it. I do not however tolerate people insulting me for no reason at all. So please, criticize me all you want, just stay respectful. Thank you, KaKaRoTo
*When you run the app it will beep once and reboot if successful. Three beeps indicates a failure, report the contents of factory.txt in this thread for help. (Factory.txt will save to the USB flash if you put on in the right most USB port of the PS3.) At this point you will come back up in Factory Service Mode (FSM).
*Brandonw has released PS3Jig for the PS3. PS3Jig is a homebrew program for the PSP that emulates the official Sony “jig” stick for entering Factory/Service mode. All you need to do is attach a USB cable between your PS3 and PSP, run the program, and turn on your PS3, just like any other downgrade/service mode method.
Superceded by : lv2diag remarry (mirror)
http://pastie.org/5138910 :
In this tutorial, I will show you how to get free wii games using USB Loader GX!IMPORTANT UPDATE: I will no longer be providing links to ROM/emulator website. The USB Loader GX is a popular game loader which allow you to load games from a USB drive. LINKS Homebrewing your wii - https://youtu.b. Installing usb loader gx wii. I’ve been very happy with my USBLoader GX setup, but it occurred to me that since my Wii always boots directly into the loader (thanks to Priiloader), I was neglecting my VC and WiiWare games! A quick Google search later and I found this WiiHacks guide for creating ISO forwarders to. Downloading Extract USB Loader GX and put it in the apps folder on your USB drive or SD card. Insert your USB drive, and SD card if you’re using one, into your Wii and launch USB Loader GX from the Homebrew Channel. In my experience, using IOS250 works best for WiiWare/VC and IOS249 works best for disc games. I had that same problem before messing around with this, eventually I settled on using IOS250 as the global IOS in USB Loader GX, then enabled IOS249 manually on whichever disc games weren’t working properly.
Apps for your PlayStation 3. With social networks, music, movies and catch-up TV, you can do it all on your PS3. Expand your entertainment. Pick your perfect PS3 app. With Spotify now available on PlayStation Music, you have a new way to enjoy streaming music on your PlayStation 3. Put unrar’ed remarry files on a blank USB stick & add a 2.30 (PS3 FAT only) or 3.15 (PS3 Slim) PUP Put in the service mode JIG/dongle and get into factory service mode. Put the created USB stick into port 0 (closest to the reader) and run. Drive Init Executing File:PS3 Remarry DriveInit Executing.jpg means it is starting the remarry process. Put console in service mode with JIG (in case you left service mode and ran the prepatched firmware in normal mode) Use normal lv2diag.self and unpatched official firmware (e.g. 3.55) on USB Mass Storage device in root and let the system reinstall that in factory service mode (FSM). After installation is finished console will turn off.
3.30 pup (mirror) / remarry files 3.55 (mirror)
old page kept for historic reference.
*1Remarry BluRay drive
*1.4CFG Settings
*1.5Remarry breakdown
*1.5.1full CFG breakdown
*1.63.55 downgrader
*1.73.50 downgrader
*1.8OtherRemarry BluRay drive[edit]
Hardware is interlocked on the PS3, so exchanging a bluray drive from one unit to another requires remarriage of the components.Procedure[edit]
*Make sure you don´t have any CD/DVD/BD on the drive
*Put unrar’ed remarry files on a blank USB stick & add a 2.30 (PS3 FAT only) or 3.15 (PS3 Slim) PUP
*Put in the service mode JIG/dongle and get into factory service mode.
*Put the created USB stick into port 0 (closest to the reader) and run.
*Drive Init Executing File:PS3 Remarry DriveInit Executing.jpg means it is starting the remarry process
*Drive Init Failed with big pink letters ’NG’ (No Good!) File:PS3 Remarry Pink-NG DriveInit Fail.jpg means the process failed. Most likely solved by first downgrading the console or fix the communication issue with the drive.
*After you run the initial remarry process, do not take it out of factory service mode.
*Put a BD movie disc in and run it on the PS3. (This restores your DRL files!)
*Then you can take it out of factory service mode.
*Launch as normal.Needed files on USB stick[edit]
dev_usb000.rar (856.52 KB) :
for comparison:Additional Notes on Remarry Procedure[edit]
*2.30 and 3.15 are not ’special’, iirc firmware <=3.30 should be fine (>3.30 won’t work) to use as reinstaller PUP.
*Lv2diag.self for 3.55 downgrade has BD patched out. So in case you have a 3.55 console you wish to remarry, you can either:
*lv2diag.self downgrade it first to 3.50 or lower and then use the remarry procedure ; or (if possible):
*QA-flag extra it, then QA downgrade via recovery to <3.50 followed by remarry procedure.
*without working BD packages won’t work :(
*If console was previously downgraded from >= 3.56:
*syscon hashes must be either patched out (lv1 patches)
*e.g. Rogero_CFW3.50_LV1Patched_NoBD_for_Re-marry.PUP
*or dehashed (double FSM)
Alternative method for restoring DRL : [Downgrade BluRay Playback Issue]
If you have problems with remarry, but still get a good ’Drive Init’ message or where able to restore the original DRL backup from dev_flash3 of that BD-drive and it still does not work: try Restore Filesystem in the Recovery Menu.CFG Settings[edit]
Remark: For some reason people are not looking in the CFG file for other selectable options.
e.g. (line 269 until line 280 quoted):
This will remarry the drive to the console and remake the DRL files (setting it to 0 will NOT remarry it)
This will install the firmware PUP that is on the USB stick in root (setting it to 0 will NOT install firmware)Warning about editing CFG[edit]
Default is both options set to 1 and is confirmed to work on both PS3 FAT (NAND and NOR) and PS3 Slim (NOR). Strange things can happen when messing with the CFG and using nonvalid values or combinations.
Remarry breakdown[edit]full CFG breakdown[edit]Drive Init[edit]
This will remarry the drive to the console and remake the DRL files (setting it to 0 will NOT remarry it) Install Systemsoftware[edit]
This will install the firmware PUP that is on the USB stick in root (setting it to 0 will NOT install firmware) freebdp[edit]
If enabled will give error 0x80010006 (file does not exist) and results in ’Initialize revocation list FAIL’. It needs free_bdp.self to be presentInstall Systemsoftware Updater[edit]
the filename of the SELF used for updating the firmware
lv2diag.self (remarry)[edit]manufacturing_updater_for_reset.self (remarry)[edit]
Free software il signore dell 60olimpo zeus by tabor rd..
fdm_spu_module.self (remarry)[edit]
3.55 downgrader[edit]Lv2diag.self (file1 - 3.55 downgrader)[edit]Lv2diag.self (file2 - 3.55 downgrader)[edit]
(same as 3.50--)
3.50 downgrader[edit]Lv2diag.self (file1 - 3.50 downgrader)[edit]Lv2diag.self (file2 - 3.50 downgrader)[edit]
(same as 3.55--)
Other[edit]manufacturing_updater_for_reset.self (ifcaro @ elotrolado)[edit]CONSOLE_SETUP_CEX.SIG.XML (ObjectiveSuites files)[edit]Ps3 Service Mode Jig Files Free Apps Downloads
Ps3 Service Mode Jig Files Free Apps FreeGeneralBluedisk EID0 reDRM·Boot Order·Bugs & Vulnerabilities·Dumping Bootldr·Dumping Metldr·Files on the PS3·KaKaRoTo_Kind_of_´Jailbreak´·PS3Cobra Payload Reverse Engineering·PS3UserCheat·QA Flagging·ReDRM / Piracy dongles·Revoke List·RSOD Fix·rtcalarm.dat·Whitelisting·VTRMHypervisorHypervisor Reverse Engineering·Repository NodesServicesAppliance Information Manager·AV Manager·Dispatcher Manager·Factory Data Manager·Indi Info Manager·SB Manager·SC Manager·Secure LPAR Loader·Secure Profile Loader·Secure RTC Manager·Security Policy Manager·Storage Manager·Update Manager·Updater Frontend·USB Dongle Authenticator·User Token Manager·Virtual TRM ManagerPlugin
Interfacesap_plugin·audioplayer_plugin·audiop_plugin_dummy·audiop_plugin_mini·auth_plugin·autodownload_plugin·autoupdateconf_plugin·avc_plugin·avc_util·avc2_game_plugin·avc2_game_video_plugin·avc2_text_plugin·bdp_disccheck_plugin·bdp_plugin·bdp_storage_plugin·campaign_plugin·category_setting_plugin·comboplay_plugin·custom_render_plugin·data_copy_plugin·deviceconf_plugin·dlna_plugin·download_plugin·dtcpip_util·edy_plugin·esehttp·eseibrd·eseidle·eselock·eula_cddb_plugin·eula_hcopy_plugin·eula_net_plugin·explore_plugin·explore_plugin_ft·explore_plugin_game·explore_plugin_np·filecopy_plugin·friendim_plugin·friendml_plugin·friendtrophy_plugin·game_ext_plugin·game_indicator_plugin·game_plugin·gamedata_plugin·gamelib_plugin·gameupdate_plugin·hknw_plugin·idle_plugin·impose_plugin·kensaku_plugin·msgdialog_plugin·mtpinitiator_plugin·musicbrowser_plugin·nas_plugin·netconf_plugin·newstore_plugin·np_eula_plugin·np_matching_plugin·np_multisignin_plugin·np_sns_plugin·npsignin_plugin·np_trophy_ingame·np_trophy_plugin·osk·oskfullkeypanel·oskpanel·pesm_plugin·photo_network_sharing_plugin·photolist_plugin·photoviewer_plugin·playlist_plugin·poweroff_plugin·premo_plugin·premo_game_plugin·print_plugin·profile_plugin·ps3_savedata_plugin·ps3_savedata_plugin_game·ps3_savedata_plugin_psp·rec_plugin·regcam_plugin·remotedownload_plugin·sacd_plugin·scenefolder_plugin·screenshot_plugin·software_update_plugin·soundvisualizer_plugin·strviewer_plugin·sysconf_plugin·system_plugin·thumthum_plugin·upload_util·user_info_plugin·user_plugin·videodownloader_plugin·videoeditor_plugin·videoplayer_util·videoplayer_plugin·vmc_savedata_plugin·wboard_plugin·webbrowser_plugin·webbrowser
https://diarynote-jp.indered.space
コメント