PS3 4.81.1 REBUG REX / D-REX + COBRA v7.31 (w/ Rebug Toolbox v02.02.11)

One more time FYI:

When i use the Soft-Reboot-Function and wait a few seconds (5 secs are enough),
the problem doesn't occur.



-----------Update: Not 5 secs but 8 secs are enough-----------
 
Last edited:
Ok, I have now checked it exactly several times:

PS3 on, XMB there, Soft-Reboot-Function, LED's go off, 8 secs after that (after the LED's go off) PS-Button (about 9 secs before coldboot appears) --> sync ok.

But 1 second earlier, it means:

PS3 on, XMB there, Soft-Reboot-Function, LED's go off, 7 secs after that (after the LED's go off) PS-Button (about 10 secs before coldboot appears) --> sync faild.
 
Ok.
Am trying now to press the PS button after soft reboot as soon as the pad led switches off. It flashes a while then syncs. 15 tests - > no problems...
I still cannot reproduce on 210x x & 250x
Has anyone else got this pad sync issue? Please report...
 
I was wondering if id be able to get help from someone regarding a strange change I noticed on my system since I'm not sure if it's normal nd to be honest I'm not exactly sure when it changed nd I'm not sure if it'll be an issue for downgrading?!?!? Some time ago on one of the older rebug fw's I was checking things out, features and such, and in this case xmb cfw settings enabled in rebug toolbox then using the following---cfw tools>service tools>display applicable version---& I'm pretty sure i clearly remember it saying 3.4x minimum downgrade version, and haven't checked it since, up until now, & now it says minimum downgrade version 3.65 :/ I'm using this latest 4.81.1 rebug Rex firmware...so any info/help/advice would be appreciated :)
 
Thx for the hint, but after a Soft-Reboot (*Custom Firmware Tools), + after that quickly hitting the PS-Button --> LED's are only flashing.
Tried several times --> No luck.


--------------Is there maybe a guy with the same problem?--------------
With debug Pad auto sync, you don't need to press PS on the gamepad. The console will look for any gamepad in the vicinity automatically & sync it!
 
Awesome thanks for the fast reply guys, I friggin love the work you guys do for the scene :) k I converted to dex & it still says the same, so I will DL & try the pup now, & if a HDD sync issue how abouts would I go about that??...but b4 I go ahead with anything more I shall mention that I did flash a different CID to it as my other one got banned couple months ago..and I have a feeling that could be the cause...would I be correct or no?? :)
 
Awesome thanks for the fast reply guys, I friggin love the work you guys do for the scene :) k I converted to dex & it still says the same, so I will DL & try the pup now, & if a HDD sync issue how abouts would I go about that??...but b4 I go ahead with anything more I shall mention that I did flash a different CID to it as my other one got banned couple months ago..and I have a feeling that could be the cause...would I be correct or no?? :)
The hdd latency issue mentioned by Joonie was about the pad sync problem reported by another user I believe....

Messing with idps can have all sorts of consequences including messing with QA but a change in Minver, am not sure...
Try the PUP if you wish, it takes 1mn...
How did you change the idps anyway? Perma change? If yes, how?
 
It's pretty simple and straight forward to flash it with IDPSet, Open up IDPSet

Press x to select edit

Edit the IDPS TO THE NEW VAILD IDPS

Simply highlight Save IDPS in EID0 & EID5

Wait for the progress bar to finish then it is officially flashed, done!!

Then restart ps3

That's how I flashed it if you wanted to know exactly how I did :)
 
It's pretty simple and straight forward to flash it with IDPSet, Open up IDPSet

Press x to select edit

Edit the IDPS TO THE NEW VAILD IDPS

Simply highlight Save IDPS in EID0 & EID5

Wait for the progress bar to finish then it is officially flashed, done!!

Then restart ps3

That's how I flashed it if you wanted to know exactly how I did :)
Oh... Lol
I know idpset very well, thank you very much.
That's not why I am asking at all.
Am trying to find out what you have done that could change Minver. Now I know you changed eid5 with another idps...
Where did you get that idps btw?
 
Hdd can cause sync issues too, due to delay from dev_flash


Sent from my iPhone using Tapatalk

This is interesting. I have replaced my old HDD with a new one, on May 2013.

The new one is a hybrid drive:
Seagate SSHD SATA III 1TB 8GB FLASH 5400RPM 2,5'' ST1000LM014

Maybe this is the problem. Maybe this 5400RPM SSHD is slower (transfer rates, latency, seek times) than the old one.
 
Oh yes I most definitley figured you'd know out of all people, I just mentioned it incase you wanted to know how exactly I changed it for my situation tis all :P lol & yes I believe that's how you make it permanent is by choosing that EID0 & EID5 option right, & I got my CID from a supposably trusted seller at radicalexploitz, which was found out to be a CID generator scammer when Sony patched the CID glitch so afterwards non of his CID's worked anymore including mine, i then reported him asap then he got banned from that site asap & i got my refund from paypal asap no problem :) so ya I still have that invalid CID flashed on my system as Im not to in a hurry to get another CID for online :P but I will soon again that's for sure..so I'm thinking it is the cause & I assume you think it's the cause as well?? Oh ND it still says 3.65 on the minver pup
 
Btw do you still have a nor dump from before the idpset change?

It may be related but I cannot confirm....
I have my own idea about this but I would prefer to get @Joonie or @habib's opinion about it & more important about what to do next...(guys postings about this begin at #147, random idps changed in eid5 by idpset & Minver changes?)
 
Last edited:
This is interesting. I have replaced my old HDD with a new one, on May 2013.

The new one is a hybrid drive:
Seagate SSHD SATA III 1TB 8GB FLASH 5400RPM 2,5'' ST1000LM014

Maybe this is the problem. Maybe this 5400RPM SSHD is slower (transfer rates, latency, seek times) than the old one.

I have tested your situation and I cannot replicate the problem as well & I got the original 5400rpm HDD, it's prolly to do with your controller, iv been thru a few controllers that had annoying messed up sync/charge/power on issues even though I knew for a fact they worked perfectly like new from playing on them b4 the problems occurred & from testing them after the problems occured on computer, phone over bluetooth etc etc...and that happened both on OFW ps3 & cfw ps3!!
 
With debug Pad auto sync, you don't need to press PS on the gamepad. The console will look for any gamepad in the vicinity automatically & sync it!

I am not really understanding, how it works. What i have to do?

- Debug Menu Type: switched from CEX QA to DEX
- Pad Auto Detect switched from "Off" to "On" --> the message appeared "To reflect the settings, restart the system"
- Restarted PS3 using Soft-Reboot-Function but nothing special happend

???
 
@WTF-IGO
True. That can happen.
I have also had various issues with a couple of ssd drives some time back...
One thing you might want to do use the jumper to change the sata mode on the hdd to sata 150.
Sata speed over 150 is not supported by the ps3 & with some hdd running in another sata mode seems to be an issue.
Look at this page
http://www.psdevwiki.com/ps3/Harddrive
Especially this part:
"Replacing the internal harddrive:
For compatibility, if you have a SATA-300 (sometimes called SATA-II or SATA2) or SATA-600 (sometimes called SATA-III or SATA3) harddrive, you should sometimes set the harddrive via jumper to enforce the slower SATA-150 speed, instead of default 3 Gb/s of SATA-300 / 6Gb/s of SATA-600."
 
Btw do you still have a nor dump from before the idpset change?

It may be related but I cannot confirm....
I have my own idea about this but I would prefer to get @Joonie or @habib's opinion about it & more important about what to do next...(guys postings about this begin at #147, random idps changed in eid5 by idpset & Minver changes?)

No I don't have one & I have never taken a dump of it, period, since I got it brand new on ebay originally with the 3.55 fw for a pretty penny so there was no downgrading involved with my 2501 ps3 ever :)
 
Back
Top