PLEASE HELP. HABIB to REBUG. is it possible? newbie (solved)

habib said:
ok then
/dev_bdvd/PS3_UPDATE/PS3UPDAT.PUP
find this in emer_init, change it to anything
/dev_bdvd/PS3/UPDATE/PS3UPDAT.PUP
this would still be there.
Click to expand...

I'm not following this no matter how I read it this still says it's going to get the update from default location PS3/UPDATE/PS3UPDAT.pup with you saying that this would still be there
So why not also change that
This change is just for the bdvd right. It must be as the directory starts dev_bdvd so this is not for network or USB updates
And what's the difference in PS3_UPDATE and PS3/UPDATE
i noticed @DeViL303 kept referring to PS3_UPDATE but I assumed it was a typo. Obviously it's not



Sent from my hand using Tapatalk and magic
 
bguerville said:
Isn't PS3_UPDATE the path used in Games (isos, JB folders & discs) & PS3/UPDATE/ the USB update path?
Click to expand...

Yes I think that is the way it is, Games have a folder called /PS3_UPDATE/ that contains the PUP, but PUPs can still be burned onto disk in the USB location PS3/UPDATE/ afaik. So I suppose if just the game path is blocked then that would block most accidental OFW updates and still allow burned disks for emergencies.
 
DeViL303 said:
Yes I think that is the way it is, Games have a folder called /PS3_UPDATE/ that contains the PUP, but PUPs can still be burned onto disk in the USB location PS3/UPDATE/ afaik. So I suppose if just the game path is blocked then that would block most accidental OFW updates and still allow burned disks for emergencies.
Click to expand...

Ah this makes sense now why PS3/UPDATE is left alone in dev_bdvd


Sent from my hand using Tapatalk and magic
 
bguerville said:
Or we could change the PS3_UPDATE game path to whatever else... This way we are not really blocking anything, just changing a path so no ofw can install unintentionally....?
Click to expand...

Well yes that's kind of what I meant by blocking , but changing that path would only do for game disks, but if the filename was changed instead of the path, then that exact same naming solution could be used to block internet OFW updates too (from XMB and recovery). Don't want to make it too confusing for people so best if it can be a universal solution across all media.
 
bguerville said:
I agree. No need to change path really. Leave everything as is.

Change the file name though.
This way any update has to be manually done, no unintentional updates but nothing really blocked.
Click to expand...

Yes that's what I was thinking.

On the other hand,(just thought of this), changing/blocking just the game path only, and changing the URL for OFW updates would also work while leaving the current USB system unchanged..maybe that would be better? There are a few ways to do it..
 
DeViL303 said:
Yes that's what I was thinking.

On the other hand,(just thought of this), changing/blocking just the game path only, and changing the URL for OFW updates would also work while leaving the current USB system unchanged..maybe that would be better? There are a few ways to do it..
Click to expand...
Yes that was what I had in mind at first! [emoji3]
Both ways seem acceptable I suppose...
 
I see. Along with a URL block/change it sounds good.

While on the subject, Im sure the "New FW is available" nag pop up could be used to let users know a new CFW is out instead of OFW as a little extra feature.

CFW creators would just have to host their own Ps3-updatelist.txt file and change the URL to point to it in their FW. They wouldn't have to host the actual new FW PUP if they didn't want to. Then they could also change the nag message to say (for example) "New version of Rebug is available, go to Rebug.me to find out more" or something like that.

Because it is when a new OFW comes out that a lot of accidental OFW updates happen..kids etc..seeing the message and just updating, so this could be a nice extra feature IMO.
 
Last edited:
bguerville said:
Yes.
Click to expand...
im a cech user, all I did after changing to rebug was to enable webman, cobra and change normal to rebug.

what so I need to change if I want to play online and to protect my ps3. sorry there are too many changes after converting to rebug.

what do I need to enable or check on this to play online at

webman, rebug tool, psnpatch and debug setting

https://m.reddit.com/r/ps3homebrew/wiki/psnpatch/ - is this also the right guide? should I follow all of this?
 
Last edited:
lahnz13 said:
im a cech user, all I did after changing to rebug was to enable webman, cobra and change normal to rebug.

what so I need to change if I want to play online and to protect my ps3. sorry there are too many changes after converting to rebug.

what do I need to enable or check on this to play online at

webman, rebug tool, psnpatch and debug setting

https://m.reddit.com/r/ps3homebrew/wiki/psnpatch/ - is this also the right guide? should I follow all of this?
Click to expand...
We have already answered those questions & told you where to get reliable information.
With Rebug Toolbox 02.02.10, enable Cobra, webman & Rebug Mode. You can safely leave everything else as-is for now.
Download the webMAN-MOD 1.43.35 updater pkg from aldostools github, install it then run the update.
After reboot, configure webMAN-MOD as required.
Download the psnpatch 2015/11A pkg from store.brewology.com & read the release notes while you are there. Install it.
Launch psnpatch, press Select button on your gamepad to open the Cobra Toolbox.
Choose to install the psnpatch plugin but NOT webman, apply the changes with the Start button.
On reboot, you should see 2 pop ups (top right of screen), one telling you webman is loaded & the other about psnpatch.

Now mount a game with webMAN-MOD or any other mounting tool, if you want psn access for gaming. If you don't intend to play you can omit this step.

Use the "Unload Webman" combo with your gamepad to trigger psnpatch. Check the webMAN-MOD combo list at the bottom of the wMM setup page if you don't already know it.

That's it. You are ready to connect to PSN.
Remember not to use any brews after triggering psnpatch, it won't work anyway.
When you are done with PSN, reboot to regain CFW features. You would also need to reboot in order to change game...

I also suggest you get additional information from the psnpatch
http://www.psx-place.com/threads/psnpatch-usage-info-releases-info-official-support-thread.125/
& webMAN-MOD
http://www.psx-place.com/threads/webman-mod-general-information-thread.27/
general threads in this forum (not reddit...) where most questions have already been answered.

As for Rebug in general, why don't you begin by reading the extensive information about the CFW & the Toolbox on rebug.me? You will get answers to most questions you may have there.

If you still have questions after all that, get back to us. [emoji6]

Btw all ps3 users are CECH users! [emoji5]️It's the rest of the SKU code that's important...
 
Last edited:
DeViL303 said:
Well I'm not sure if bd update needs to be blocked fully, as that could cause people problems with faulty USB like you said . but if it looks for different path or filename then we get the best of both worlds, nothing blocked except Pups named PS3_UPDAT.PUP

Edit, maybe you just mean to block BD and to leave DVD and CD open, that would be good too.
Click to expand...

FYI emer_init.self is already patched in Rebug since last year (or maybe before) with these paths:
/dev_bdvd/NOT_UPDATE/PS3UPDAT.PUP
/dev_bdvd/NOT/UPDATE/PS3UPDAT.PUP

It only patches the paths on /dev_bdvd because these are the risky ones (all game discs have /PS3_UPDATE folder and the user could forget to remove them while updating). The USB paths in emer_init.self could be risky too, but only if the user left stored OFW pups in /PS3/UPDATE.

If /PS3/UPDATE would be blocked then the users could not update the CFW using a pendrive or USB drive. That's why they are not blocked in emer_init.self.

Also webMAN MOD blocks /dev_bdvd/PS3_UPDATE and the online ps3-updatelist.txt when it loads, so it's very *unlikely* that an user could update accidentally from a disc or from network... The chances are there, but reduced compared to years ago.
 
aldostools said:
FYI emer_init.self is already patched in Rebug since last year (or maybe before) with these paths:
/dev_bdvd/NOT_UPDATE/PS3UPDAT.PUP
/dev_bdvd/NOT/UPDATE/PS3UPDAT.PUP

It only patches the paths on /dev_bdvd because these are the risky ones (all game discs have /PS3_UPDATE folder and the user could forget to remove them while updating). The USB paths in emer_init.self could be risky too, but only if the user left stored OFW pups in /PS3/UPDATE.

If /PS3/UPDATE would be blocked then the users could not update the CFW using a pendrive or USB drive. That's why they are not blocked in emer_init.self.

Also webMAN MOD blocks /dev_bdvd/PS3_UPDATE and the online ps3-updatelist.txt when it loads, so it's very *unlikely* that an user could update accidentally from a disc or from network... The chances are there, but reduced compared to years ago.
Click to expand...

Oh, I only knew about some of those patches. So looks like nothing needs doing then. Anyone who still updates to official FW accidently after that would be real unlucky/stupid.

Sorry for the thread derailment guys. :)
 
Am never getting tired of thanking Aldo so..
Thanks Aldo for those important details.
I was aware of the webMAN-MOD's features but I must admit the Rebug changes got lost on me somehow...


Is there such a emer_init.self patch in other CFW than Rebug? Ferrox?

As is in last Rebug we can't update from disc then?

I still think it's better to change the name rather than the path.
It would avoid unnecessary restrictions.
 
bguerville said:
Is there such a emer_init.self patch in other CFW than Rebug? Ferrox?

As is in last Rebug we can't update from disc then?

I still think it's better to change the name rather than the path.
It would avoid unnecessary restrictions.
Click to expand...

I thought that at first, but really its not fully blocked. Users can still burn disks with PUPs at the path "dev_bdvd/NOT/UPDATE/PS3UPDAT.PUP". The only advantage to a permanent XMB patch I can see would be for when webman unloads, atm an OFW update from disk is possible via XMB with the current setup, I think.
 
You must log in or register to reply here.

Similar threads

Back
Top