PS3 Cannot enable syscalls - even after reboot

[dvnlhnt]

Ive been disabling syscalls and using this unit with 4.9 PEX CFW before going online and playing games. Recently, my discs werent loading when inserted into bd. Anyways some troubleshooting later I discovered my syscalls aren't re enabling when i restart the unit.

using cobara tools to "allow restore syscalls" fails, "start syscals x," fails, show sys info" syscalls are disabled

Im not sure what to do. Was literally working fine last night. Toggling cobra not working either

 

[dvnlhnt]

OK well I completely panicked thinking I had somehow/bricked my system.

Reflecting on the situation the only questionable interactions with the bd drive in the CFW was I clicked "insert disc" in webman while the disc was inserted and it ejected and immediately inserted the disc again. And at one point i clicked the "unmount disc" in webman trying to get a psp game to show up on the xmb that I had downlaoded from PSN as a test. I thought maybe it was webman messing with the system. So I uninstalled it and tried to reinstall. Webman failed to reinstall and wouldnt load the sub menu selection. (I guess bc syscalls were disabled somehow) tried to remarry drive by dumping eid rootkey, unable to dump eid root key. unable to boot into service mode.

But the I have two other CECHA01 systems both with this same firmware. And so thinking it may be firmware related I plugged in a different unit, also on Evilnat 4.9 PEX, and immediately checked to see if disc drive was working. It was, syscalls working, I dumped the EID root key, went to ps3toolset.com dump mem, download and patched mem.
I then again had the issue of being unable to use syscalls on this seperate unit.

Does ps3toolset break syscall function after mem patch when evilnat 4.9 is already installed? fearing a similar outcome of the OP unit I installed 4.9 OFW through the recovery menu out of fear that I ruined these perfectly good CECHA01 units. 4.9 OFW installs fully and ps3 and ps2 disc games recognize load.

I then did the exact same thing to the OP unit. 4.9 OFW install fully but again no disc is being read or showing on xmp but the bd drive is working to insert and eject the disc. ps3 nor ps2 games auto-start work or show up on xmp. But to my surprise the PSP games I downloaded before but werent showing up now showed on the XMB in 4.9 OFW.

I then ps3toolset again dump mem, patch mem, and reinstall Evilnat 4.9 PEX. Syscalls now working but again no disc loading or showing on xmp but drive is inserting/ejecting discs. dump eid root key success. successfully entered factory service mode. succesffuly remarried optical drive with eid root key. bd drive again working to insert and eject disc but wont auto-start, recognize, or show on xmp?

What has happened to the blue ray drive on this unit? something went very wrong I just had this unit working fine. games were loading fine. how could the drive but pushing/pulling disc and not loading in gameOS? can someone help me fix my disc drive?

 

[GuilloteTesla]

Reflecting on the situation the only questionable interactions with the bd drive in the CFW was I clicked "insert disc" in webman while the disc was inserted and it ejected and immediately inserted the disc again. And at one point i clicked the "unmount disc" in webman trying to get a psp game to show up on the xmb that I had downlaoded from PSN as a test. I thought maybe it was webman messing with the system.

PSP games downloaded from PSN Store can not be mounted as disc games. All of them are digital EBOOT.PBP files.

What has happened to the blue ray drive on this unit? something went very wrong I just had this unit working fine. games were loading fine. how could the drive but pushing/pulling disc and not loading in gameOS? can someone help me fix my disc drive?

If you could install OFW and CFW, and not got into a boot loop, then your BD drive's daughterboard is fully functional.

On the other hand, a drive taking in and out discs only means that the mechanical part is working. But if no game data shows on the console, then the laser must be broken. That's why you can not load any disc games on that unit.

Any way, your situation is very rare and we don't have the full history of your actions, procedures, states and installed software/FW. You also mention other consoles as examples, but that adds more to the confusion.

I recommend the following: start clean, OFW 4.90, fresh install, formated HDD.

A-1. If your disc games work then it's a CFW issue.
A-2. If not, your laser must be dead.

If you get to point A-1, try installing CFW 4.90 CEX (I don't know why you went with PEX version) and repeat the experiment:

B-1. If your disc games work then it's another issue.
B-2. If not, your console has something bad with the NAND that can't take CFW (very unlikely but possible).

If you get to point B-1, try installing WebMAN MOD and repeat the experiment:

C-1. If your disc and digital PSP games work, then your issue was a bad installation of CFW or homebrew.
C-2. If not, maybe there is some issue with WebMAN MOD (surely a bad setting in the config).

Try these steps and get notes of each step, before and after executing them, to have a trace.

Good luck!

 

[dvnlhnt]

Sorry for being so long winded in this reply, just trying to be as thorough as possible to help identify the issue.

But if no game data shows on the console, then the laser must be broken. That's why you can not load any disc games on that unit.

I fully accept that this may be possible just seems ridiculous that less than 24 hrs after use and testing all BD functions as working the laser just craps.

Examing some YT vids of people with dead laser my system mimics issues documented by others for dead laser; Physical insert/eject functional, no disc loading or xmb display, spinning wheel top right xmb

Any way, your situation is very rare and we don't have the full history of your actions, procedures, states and installed software/FW. You also mention other consoles as examples, but that adds more to the confusion.

My apologies, I'll try to be more clear in my steps.

1. Unit was on 4.4x when received; tested ps3/ps2 disc functionality working

2. Dumped NAND/flashed mem patch via ps3toolset

3. Installed Evilnat 4.90 PEX; tested disc game functionality working, played online and offline with physical disc

4. Installed Samsung 870 EVO // format; tested disc game functionality working, played online and offline with physical disc

5. Installed Webman mod 1.47.45 FULL // installed File Manager 1.42 // installed Managunz 1.42 // installed PSP remasters

6. Experienced issue of physical ps3 discs softlocking during loadings; file manager and managunz softlocking system when used, no input responses // forced hard resets; made forum post (no responses)
https://www.psx-place.com/threads/m...reezing-or-soft-locking-physical-discs.42756/

PSP downloads from PSN not showing on XMB but taking up space on SSD; made forum post (1 responses)
https://www.psx-place.com/threads/w...tored-in-the-file-directory-of-the-ps3.42755/

7. Uninstalled all packages // reinstalled webman mod 1.47.45 FULL // reinstalled PSP remasters. All ps3 disc functionality working, played ps3 titles offline and offline for a couple days

8. Short time later, ps3 disc not launching or showing from XMB when inserted. SYSCALLS no longer reenabling on reboot (See OP)

9. Uninstall PSP remasters // Uninstall Webman Mod; still no disc reading or launching from XMB.

10. Reinstalled webman mod // failed install webman mod xmb menu not working (icon but no functionality (syscalls disabled)

11. attempt to remarry BD // unable, syscalls not reenabling

12. panic... loaded ps3toolset.com // dumped NAND // loaded mem patch http // applied mem patch

13. reinstalled OFW 4.90 // success // XMB now shows PSN downloaded PSP games from before

14. (did not test ps3 discs, false assumption discs were now working, assumed CFW culprit) reformatted SSD to hopefully purge problematic files // success // PS3 disc not launching or loading on XMB still

15. panic... loaded ps3toolset.com // dumped NAND // loaded mem patch http // applied mem patch

16. reinstalled Evilnat 4.90 PEX // success // PS3 disc not launching or loading on XMB still, spinning wheel in top right XMB indicating acknowledgement of disc insertion, but no audible disc spin or indication of disc reading

17. SYScalls now working again // Dumped EID root key, backed up // entered factory service // remarry BD drive // Success // PS3 disc not launching or loading on XMB still, spinning wheel in top right XMB indicating acknowledgement of disc insertion, but no audible disc spin or indication of disc reading.

18. Installed Webman mod 1.47.45 FULL // Success // attempted hold select, dump BD drive to HDD // no action, no disc drive audible spin or read indication

19. current time // determining next steps.

I recommend the following: start clean, OFW 4.90, fresh install, formated HDD.

A-1. If your disc games work then it's a CFW issue.
A-2. If not, your laser must be dead.

If you get to point A-1, try installing CFW 4.90 CEX (I don't know why you went with PEX version)

I chose Evilnat 4.90 PEX as thats what i saw others in tutorials choosing. I read that the added debug options would prove useful/necessary in threads here at PSX-place // I will attempt a reinstall of OFW 4.90 // format SSD again //

Do I need to download and apply the ps3toolset.com mem patch every time or can i freely install CFW/OFW 4.9 at this point? Can I go directly to Evilnat 4.9 CEX? Should I attempt downgrade to OFW 3.55 then upgrade to 4.9 OFW or Evilnat 4.90 CEX?

You also mention other consoles as examples, confusion

sorry, I panicked because the Evilnat PEX CFW install was performed the exact same way as described above initially on my other two CECHA01 systems (I have three.)

I first booted and test one of the other two CECHA01 // tested disc game functionality working

Fearing and assuming the CFW ruined my optical drive, I dumped my EID root key for that unit and reinstalled OFW 4.90. That unit has OG HDD still. tested disc functionality is fully working OFW 4.90. So i atleast have a working OFW system to play on despite its only 60 gb HDD

I also have a fourth unit // CECHG01 (dead RSX YLOD) // I could rob BD Optical from, kept around as donor. If it comes to it.

 

[GuilloteTesla]

Thanks for the clear explanation, now we can specify potential issues.

4. Installed Samsung 870 EVO // format; tested disc game functionality working, played online and offline with physical disc

This is key and was never mentioned before. PS3 has issues with SSDs. And it so happens that your disc reading problems started to appear after your installed the SSD.

It's known that SSDs work for a while, but after some time the console starts to behave erroneously, from corrupting your whole filesystem to not loading PS1 and PS2 games.

Try to put back an HDD and check if everything works as it should.

11. attempt to remarry BD // unable, syscalls not reenabling

Don't waste efforts in remarring your BD drive, it's already attached to your console and should work once you try an HDD.

Again, it's very unlikely that your laser went bad after a week of use and tests.

Do I need to download and apply the ps3toolset.com mem patch every time or can i freely install CFW/OFW 4.9 at this point? Can I go directly to Evilnat 4.9 CEX? Should I attempt downgrade to OFW 3.55 then upgrade to 4.9 OFW or Evilnat 4.90 CEX?

If you happen to install OFW then yes, you must apply mem patch in order to install CFW. If you already installed CFW, you can install any other CFW version as long as they are the same number and for the same type of system (if you are on retail, you must install CEX or PEX; if you are on debug, you must install DEX or D-PEX). In order to install other number of CFW and be able to downgrade, you must QA flag your console, but it's not gonna change your situation.

Don't bother going down to OFW 3.55, it will not help and will bring more headaches. Quick story: it's being reported that installing CFW above 4.86 (or from 4.8x version, can't remember right now) directly over OFW 3.55 will fail, with only the solution being to install an intermediate version CFW (4.76 for example) and then installing 4.90 version. Very cumbersome, check the forums and you will find these reports I'm talking about.

 

[NiQ]

Do I need to download and apply the ps3toolset.com mem patch every time or can i freely install CFW/OFW 4.9 at this point? Can I go directly to Evilnat 4.9 CEX? Should I attempt downgrade to OFW 3.55 then upgrade to 4.9 OFW or Evilnat 4.90 CEX?

If you ever switch back to OFW then yes, you would need to use bgtoolset again in order to reinstall CFW. You do not need to use bgtoolset again if you already have CFW and just want to update it to a newer (/older) version and/or switch from one CFW to another.
If you want to go back to OFW you should also consider Dual Boot firmware. DB is 99.9% identical to OFW, with a single difference - the system update mechanism is pre-patched to allow the reinstallation of CFW, therefore saving you the need to run bgtoolset again.

You do not need to downgrade to 3.55 in order to install CFW after running bgtoolset and in fact you can't, because bgtoolset patches don't enable downgrading. You have to install a CFW based on whatever OFW version you currently have (or higher). If you want to downgrade to a lower version you have to first install CFW, then use it to QA flag your PS3 and downgrade, but atm this is really pointless - Evilnat 4.90 contains every feature that every CFW ever had (yes, even Rebug) so downgrading will not give you any features you don't already have.

 

[dvnlhnt]

If you install OFW then yes, you must apply mem patch in order to install CFW. If you already installed CFW, you can install any other CFW version as long as they are the same number and for the same type.

If you ever switch back to OFW then yes, you would need to use bgtoolset again in order to reinstall CFW. You do not need to use bgtoolset again if you already have CFW and just want to update it to a newer (/older) version and/or switch from one CFW to another.

ok, thank y'all for clearing that up for me. I took a bit of a mental break as I felt I have been racking my brain on this unit malfunction for some time now. Since I have progressed beyond the OP issue should I start a different thread for the optical drive issue? or continue posting here?
_________________________________________________________________________________

... Try to put back an HDD and check if everything works as it should...

I put the SSD from this unit into my alternate other fully working CECHA01 that i reverted back to OFW 4.90 mentioned previously. formatted, etc. I have been gaming on that unit via physical and DLC content the last couple days with great performance relatively speaking. While I certainly recognize the warnings here its very hard for me to believe the SSD could corrupt the system in such a way to seize functionality of the optical drive without definitive proof.

1. I replaced the original HDD into the CECHA01 unit that is no longer reading disc. // physical disc still not reading

2. Tried rebuilding data base // physical disc still not reading

3. tried a couple partial insert two disc nonsense I saw online to trigger bd optical to seat/read
// physical disc still not reading

4. reinstalled 4.9 OFW // success // rebuilt data base // physical disc still not reading

5. ps3tool set mem patch // installed Evilnat 4.9 CEX (no debug) // rebuilt data base // physical disc still not reading

6. installed webman FULL (I realized previously I wasnt holding L1 down long enough and had webman light installed) // attempted eject, insert, unmount, backup disc to hdd webman optical drive functions // physical disc still not reading (ejects/accepts disc but I cannot here the disc spin up or the laser moving)

7. attempted to use webman file manager to see if system file structure could view//read disc. // negative, browsed all BD optical/optical directories I could see and did not note any type of game disc files

can someone define the exact directory of files of the BD optical if it were reading within the system?

8. determining next steps... will try to read BD optical through PC file zilla via FTP

... Again, it's very unlikely that your laser went bad after a week of use and tests...

I have no idea at this point and am more and more leaning towards this as possibility.

I cant really point any fingers as I truly have no idea what has happened. However, either the CFW and/or CFW pckgs somehow "unmounted" my disc drive or corrupted it in some way // there's some sort of error and the disc are unable to remount? or the optical laser // bd optical motor has truly failed. again, I do not hear any motorized action of the bd optical other than the ejection and insertion of disc. I also acknowledge the SSD warnings but as far as culprits go it's at the bottom of my list.

The only thing I can think to try at this point is to rob and swap the bd optical from my YLOD CECHG01 unit and try to remarry and attempt to read physical disc again.

 

[GuilloteTesla]

The only thing I can think to try at this point is to rob and swap the bd optical from my YLOD CECHG01 unit and try to remarry and attempt to read physical disc again.

It's the only thing left for you to try.