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

bitsbubba said:
You can have one of mine
f763e5173796085078dfa0e82de0209f.jpg
cf0ed3ed2f0ecea8ddc291cddcb0c74f.jpg
4d27157776e548fe2e0dc92fcf90c8f6.jpg
6d10f2521c5c724f926dd915e03d65f4.jpg

Can never have too many Jason's
Click to expand...
WoKVKGG.gif
 
DeViL303 said:
@habib I see. But I think there would be a work around for those rare cases, for example the user could burn a disk with the update on it, renamed accordingly, or if in the very worst case they have no usb they have no BD and they still want to go back to official FW (very rare case I think) then they would need to host the file and do a redirect or something, but I think that case would never happen as if you have no BD and no USB and no internet then I think the user will want to stay on CFW.

My idea isn't to patch the FW so that it wont update from BD, but rather so it looks for a different filename.

BTW: I patched the filename string to something else before in the update sprx, it works fine from XMB. But there must have been another entry for recovery mode somewhere because when in recovery it still looked for "PS3_UPDAT.PUP"
Click to expand...
it might be surprising but alot of people dont actually have dvd drives these days.
if you wanna patch the filename then just hex edit in emer_init
 
habib said:
it might be surprising but alot of people dont actually have dvd drives these days.
if you wanna patch the filename then just hex edit in emer_init
Click to expand...

I have been after this being done for a fair few years now
The big argument for having the block to PS3 - UPDATE -PS3UPDAT.pup from USB DVD & PSN is that so so so many people have at one point or another had there cfw lost due to an accidental update to ofw

I can fully understand your reason that a USB or DVD or network not working will stop someone's choice to update to ofw
But a broken network card or shorting USB port or broken drive chip (board) will put the persons console into an update loop anyway
Unless it's a superficial issue.

That all being said what about a redirect package like the qa enable package
Run it to redirect to CFW - UPDATE - PS3UPDAT.pup
And run it again to put it back to normal

That should cover you from getting backlash from anyone wanting to go back to ofw
And if deank adds it into mm and you add it into rebug toolbox and Aldo's adds it into webman mod
Then it will be readily available and not deletable by mistake

Oh and how did your exams go
Did you get what you were hoping for?
First time I have seen you in months to ask you [emoji4]

Sent from my hand using Tapatalk and magic
 
Last edited:
baileyscream said:
I have been after this being done for a fair few years now
The big argument for having the block to PS3 - UPDATE -PS3UPDAT.pup from USB DVD & PSN is that so so so many people have at one point or another had there cfw lost due to an accidental update to ofw

I can fully understand your reason that a USB or DVD or network not working will stop someone's choice to update to ofw
But a broken network card or shorting USB port or broken drive chip (board) will put the persons console into an update loop anyway
Unless it's a superficial issue.

That all being said what about a redirect package like the qa enable package
Run it to redirect to CFW - UPDATE - PS3UPDAT.pup
And run it again to put it back to normal

That should cover you from getting backlash from anyone wanting to go back to ofw
And if deank adds it into mm and you add it into rebug toolbox and Aldo's adds it into webman mod
Then it will be readily available and not deletable by mistake

Oh and how did your exams go
Did you get what you were hoping for?
First time I have seen you in months to ask you [emoji4]

Sent from my hand using Tapatalk and magic
Click to expand...
that could make people not even go to cfw(you do know you can install from disc as well right?)
as for consoles being stuck in loop, i meant if USB is BROKEN so people can iinstall through disc(not a damaged bt/bd)

for the app....hmm we can do that with cobra payload easily but in other cfws you cantdo that, i mean you can but writing to nand/nor like that....wont be safe.
but yeah with cobra we can, that would be a nice idea actually.
next cobra iteration with this feature then...lol

and thanks for asking about my exams, yeah they went smoothly, this would be the last year for my gcse finally
 
Oh yes I know you can normally update via disk but I know you can turn off that function it's in mfw builder
It's been a nagging pain that network updates bring turned off was never disabled in cfw's

Anyway if the actual pup search is for PS3UPDAT.pup is changed to CFWUPDAT.pup via cobra (as @DeViL303 suggested the name to be) will then stop network and USB updates of ofw and turn disc update off in the actual firmware will stop any disc updates then the accidental ofw update will finally be avoided

Writing to NAND / nor never is safe but then installing cfw is never safe
**cough** ferrox
**cough** ps3ita dex
**cough** controversial [emoji12]

And I am glad about your results
I take it your going to follow your programming interest into higher education without saying and asking too much in an open forum obviously [emoji846]


Sent from my hand using Tapatalk and magic
 
I still can't see any downside to Changing the filename string, it will also block OFW updates from disk, the ONLY disadvantage is that pups will need to be renamed to be installed. So if someone wants to install OFW from a disk or USB all they need to do is use a different name.??
 
DeViL303 said:
I still can't see any downside to Changing the filename string, it will also block OFW updates from disk, the ONLY disadvantage is that pups will need to be renamed to be installed. So if someone wants to install OFW from a disk or USB all they need to do is use a different name.??
Click to expand...

that is the way it's done on the 360. its update is called $SystemUpdate, but it's renamed to $$ystemUpdate through dashlaunch if u have it blocking updates. renaming the update will allow it to install.
 
If someone has broken usb they can use burned optical disk. Like I said in the extremely rare case someone has broken optical disk AND broken USB and they STILL want to go to OFW (?) then they would have to host the renamed file and do a redirect(or use ftp and debug update if on Rebug), but I cant see that ever being an issue.
 
DeViL303 said:
If someone has broken usb they can use burned optical disk. Like I said in the extremely rare case someone has broken optical disk AND broken USB and they STILL want to go to OFW (?) then they would have to host the renamed file and do a redirect, but I cant see that ever being an issue.
Click to expand...
Yes in any case there are options available in such rare cases... No one would get stuck & the majority would benefit.
 
i think i should just disable bd update then....
actually how many people are there who have usb ports not working or internet not working.
yep should just take that route i guess :)

as for nand/nor writing its not safe because, what if the electricity goes out?your ps3 is dead.

well then, ill take a peek again at emer_init and check the patches
also the patches in mfw builder, i never tried those, if those are good enough, we will just use them then.
i see that joonie added those patches in rebug already though.
PATCHED – Recovery: Prevent accidental OFW update while on Recovery mode
you will see the feature in my seperate cfw as well when i update cobra revision.
as you guys know my cfw are only released when i find new stuff and i think i have enough up my sleeves :p
btw it doesnt mean im not with rebug, all my work, even the cfw i release have features so that people can review and maybe we could add that to rebug
 
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.
 
Last edited:
Wifi not working I have seen a lot but then I do get ppl sending me consoles for downgrade that are going to prison so wifi and BT have been deliberately disabled hardware wise
LAN I don't see faulty that often
USB I have had 2 and both were easy fixes

Is the area that's changed on nor NAND really that critical
I thought it was just a name change
If it's changed in the pup so it's a fixed edit in the cfw then it's no more risky then installing the cfw right (In normal cfw not cobra)

BD update patch:-
I assumed the re named pup was only going to work on USB and network so if it works on disc as well as @DeViL303 said then no need for the patch (back to cobra cfw ;) )




Sent from my hand using Tapatalk and magic
 
We all know the risks associated with NOR/NAND writing but we already take those risks on a regular basis if only with update operations, don't we?
 
Last edited:
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.
knowledge for devs:
if you use cobra and do hooks at cellfsstat, mount you can see what emer_init is checking for.
its not really hard to reverse these functions of emer_init, hell 50% is solved just by looking text inside xD
 
You must log in or register to reply here.

Similar threads

Back
Top