PS3 Rebug CFW change RED icons color

Hmmmmm..... I thought for sure editing wboard_plugin.rco would do the trick. No suck luck, but I'm working on it. Maybe the "What's New" section is red in the original theme? I honestly can't remember.

Well I extracted the images from the original rco but this time as png files and no it's definitely not supposed to be red naturally. It's supposed to be yellow. I extracted the rco file I edited too and sure enough the images I added are all there.

Hahah! I figured it out! Additionally, the "Home" and "What's New" section images among others have to be extracted and copied to a different folder. Working on it now.
 
Last edited:
And it works! Now I just gotta upload it :3 even the background images when you hover over icons, every single image is set back to how it would look on OFW. Though if you ask me, there's never anything wrong with a little more red ;) so I'll have to set it back to normal at some point..... maybe. It does look nice like this too.
 
Enable write access to /dev_flash in mmCM (MultiMAN) settings and copy all files (except the readme file) and the folder to /dev_blind/vsh/resource

Keep in mind you won't have enough space to copy all the files at once unless you have previously deleted something. Copy the folder first, then copy the rest of the files in chunks smaller than 3 megabytes. And remember to backup the files you will be replacing first!

This theme is compatible on 4.80-4.82. This may work on 4.83 but since there is no 4.83 CFW released yet I can't test it on 4.83 yet. If you want to be the guinea pig then by all means, try it, but don't blame me if something goes wrong :-p you have been warned.

Enjoy :)

http://www.mediafire.com/file/86pouud214q32rq/PSN_Theme_Original_4.80-4.82.rar
 
Last edited:
Just a couple of details @imkira3
You are incuding more images than needed in path dev_flash\vsh\resource\explore\icon
In your .rar there are 25, and in the list i made there was 19, look here in the small table http://www.psdevwiki.com/ps3/Talk:Rebug#Restoring_rebug_custom_icons_and_images_to_default
To make that lists i was making accurate comparisons of lot of files (everything inside dev_flash\vsh\resource folder), and eventually joonie (from rebug team) helped me, so im confident the list of changes in wiki was right
My doubt is that i made this comparisons in firmware 4.76 or so (i dont remember exactly), and for 4.82 maybe they was replacing more files, but i dont think though
Anyway, check again your 25 files inside dev_flash\vsh\resource\explore\icon and compare with the 19 in the list i made in wiki
That additional 6 images you are including probably are not needed

And the other detail is what i mentioned about compatibility since firmware 4.70 up to 4.82 is not accurate
It was just a comment because this is like an start point where im sure there could be incompatibilities
But maybe there is some more incompatibilities in 4.75 or 4.76... i dont know
To know it for sure... is needed to extract the 7 official RCO files from 4.70 (all the ones you are including except explore_plugin_full.rco) and compare his hashes with official RCO files from 4.82
If the hashes matches it means we can tell safelly that RCO files from 4.70 are 100% compatibles with 4.82... because are the same exact files in both firmwares XD

So if you decide to reupload them (but dont want to make this hash comparison of offical RCO files from 4.70 and 4.82) then is better to dont mention the "4.70-4.82" in the .rar
You can just tell the files are for 4.82 and problem solved, this way there is no room for error in the description ;)

Or... you can do the RCO hash comparison with 4.70 versus 4.83... and prepare it for rebug 4.83 (even before rebug 4.83 is released)
Is a bit risky to publish something ike this because we cant be sure if rebug 4.83 are going to change something more in this RCO files... but most probably they will not change them




--------------
Edit:
This are the 6 additional icons you are including (but are not included in the list of changes in wiki), i think you can remove from the .rar
-cinfo-fg.png
-cinfo-fgsd.png
-fah-xmb.png
-icn-DiscBenefits.png
-Icon-TeleVideoSvcs.png
-widget.png

Not sure about them though, as said i made this comparison with an old rebug firmware (not with 4.82), but please take a look at them and tell me if are needed to be added to the list of rebug changes in wiki
 
Last edited:
sandungas said:
Just a couple of details @imkira3
You are incuding more images than needed in path dev_flash\vsh\resource\explore\icon
In your .rar there are 25, and in the list i made there was 19, look here in the small table http://www.psdevwiki.com/ps3/Talk:Rebug#Restoring_rebug_custom_icons_and_images_to_default
To make that lists i was making accurate comparisons of lot of files (everything inside dev_flash\vsh\resource folder), and eventually joonie (from rebug team) helped me, so im confident the list of changes in wiki was right
My doubt is that i made this comparisons in firmware 4.76 or so (i dont remember exactly), and for 4.82 maybe they was replacing more files, but i dont think though
Anyway, check again your 25 files inside dev_flash\vsh\resource\explore\icon and compare with the 19 in the list i made in wiki
That additional 6 images you are including probably are not needed

And the other detail is what i mentioned about compatibility since firmware 4.70 up to 4.82 is not accurate
It was just a comment because this is like an start point where im sure there could be incompatibilities
But maybe there is some more incompatibilities in 4.75 or 4.76... i dont know
To know it for sure... is needed to extract the 7 official RCO files from 4.70 (all the ones you are including except explore_plugin_full.rco) and compare his hashes with official RCO files from 4.82
If the hashes matches it means we can tell safelly that RCO files from 4.70 are 100% compatibles with 4.82... because are the same exact files in both firmwares XD

So if you decide to reupload them (but dont want to make this hash comparison of offical RCO files from 4.70 and 4.82) then is better to dont mention the "4.70-4.82" in the .rar
You can just tell the files are for 4.82 and problem solved, this way there is no room for error in the description ;)

Or... you can do the RCO hash comparison with 4.70 versus 4.83... and prepare it for rebug 4.83 (even before rebug 4.83 is released)
Is a bit risky to publish something ike this because we cant be sure if rebug 4.83 are going to change something more in this RCO files... but most probably they will not change them




--------------
Edit:
This are the 6 additional icons you are including (but are not included in the list of changes in wiki), i think you can remove from the .rar
-cinfo-fg.png
-cinfo-fgsd.png
-fah-xmb.png
-icn-DiscBenefits.png
-Icon-TeleVideoSvcs.png
-widget.png

Not sure about them though, as said i made this comparison with an old rebug firmware (not with 4.82), but please take a look at them and tell me if are needed to be added to the list of rebug changes in wiki
Click to expand...

Yeah, sorry man, I admit I took your word for it that everything would work backwards as far as 4.70, you seem like a smart guy so I saw no need to doubt you. As for the extra images, I noticed that too but I didn't see the harm in it, everything worked fine in my tests. I kind of just copied all the images, I know it's no excuse but it was 3 AM, I just wanted sleep lol and my tests all proved successful. It was kind of a rush release and I was going to give it another look over in the morning anyway. I'll remove the extra images in any case. As far as the older firmwares go, I will alter the title of my tutorial so it will say it works on 4.82 only, then I'll do the appropriate hash comparisons. I'm not a guy who likes to leave a project half finished. And I won't be adding 4.83 support until I can test it for myself, which involves waiting for a new DEX 4.83 Rebug release.

But first, coffee :)

Btw, I don't think you mentioned, but the original rco files all use zlib compression, this is important to know when recompiling.

Btw, love your profile image lmao
 
Last edited:
Hmmm, did you know that javascript automatically puts https on all links? That's all well and good, however, unless I disable javascript when I post it fucks with my mediafire links. They all gave me errors when I tested. Maybe it wouldn't do that if it already had http:// in fron't, but mediafire keeps things simple, it only uses www.

I wonder how many posts have been fucked up in this way unbeknownst to it's poster...... :(
 
Last edited:
sandungas said:
Just a couple of details @imkira3
You are incuding more images than needed in path dev_flash\vsh\resource\explore\icon
In your .rar there are 25, and in the list i made there was 19, look here in the small table http://www.psdevwiki.com/ps3/Talk:Rebug#Restoring_rebug_custom_icons_and_images_to_default
To make that lists i was making accurate comparisons of lot of files (everything inside dev_flash\vsh\resource folder), and eventually joonie (from rebug team) helped me, so im confident the list of changes in wiki was right
My doubt is that i made this comparisons in firmware 4.76 or so (i dont remember exactly), and for 4.82 maybe they was replacing more files, but i dont think though
Anyway, check again your 25 files inside dev_flash\vsh\resource\explore\icon and compare with the 19 in the list i made in wiki
That additional 6 images you are including probably are not needed

And the other detail is what i mentioned about compatibility since firmware 4.70 up to 4.82 is not accurate
It was just a comment because this is like an start point where im sure there could be incompatibilities
But maybe there is some more incompatibilities in 4.75 or 4.76... i dont know
To know it for sure... is needed to extract the 7 official RCO files from 4.70 (all the ones you are including except explore_plugin_full.rco) and compare his hashes with official RCO files from 4.82
If the hashes matches it means we can tell safelly that RCO files from 4.70 are 100% compatibles with 4.82... because are the same exact files in both firmwares XD

So if you decide to reupload them (but dont want to make this hash comparison of offical RCO files from 4.70 and 4.82) then is better to dont mention the "4.70-4.82" in the .rar
You can just tell the files are for 4.82 and problem solved, this way there is no room for error in the description ;)

Or... you can do the RCO hash comparison with 4.70 versus 4.83... and prepare it for rebug 4.83 (even before rebug 4.83 is released)
Is a bit risky to publish something ike this because we cant be sure if rebug 4.83 are going to change something more in this RCO files... but most probably they will not change them




--------------
Edit:
This are the 6 additional icons you are including (but are not included in the list of changes in wiki), i think you can remove from the .rar
-cinfo-fg.png
-cinfo-fgsd.png
-fah-xmb.png
-icn-DiscBenefits.png
-Icon-TeleVideoSvcs.png
-widget.png

Not sure about them though, as said i made this comparison with an old rebug firmware (not with 4.82), but please take a look at them and tell me if are needed to be added to the list of rebug changes in wiki
Click to expand...

I had a look at those images you mentioned, and you are right, the 6 images you mentioned were unaltered. I'll be removing them from the rar. No need to update your changelog. I have extracted the dev_flash from 4.70 and am doing the appropriate hash checks now.
 
explore_category_game OFW 4.70: 2CF61ACD5799E417D164EE4EF5A434C8
explore_category_game OFW 4.82: F73414F4D2475621A3CFD05163ACC6A8
explore_category_psn OFW 4.70: AFCDD7AB77294747F9681BD8672220D9
explore_category_psn OFW 4.82: AFCDD7AB77294747F9681BD8672220D9
explore_category_video OFW 4.70: 825AA07B4FB0E5B13890BEC3963DAE52
explore_category_video OFW 4.82: 825AA07B4FB0E5B13890BEC3963DAE52
explore_plugin_full OFW 4.70: 2B32DBA27785971AE03FF2AB43CE62FB
explore_plugin_full OFW 4.82: DB47D79296CEEDE41AF7E43D27E81F92
npsignin_plugin OFW 4.70: FAB1DE45A7FD293E704B2730F895CC7E
npsignin_plugin OFW 4.82: 6F498DD327E2B56E60EDEC8EA84D1B36
wboard_plugin OFW 4.70: 01013194C96A3A501D7B4C9A2664C2F8
wboard_plugin OFW 4.82: 01013194C96A3A501D7B4C9A2664C2F8
xmb_ingame OFW 4.70: 04ED4ECCA76C6927154470CC8E497B83
xmb_ingame OFW 4.82: 04ED4ECCA76C6927154470CC8E497B83
xmb_plugin_normal OFW 4.70: 9EDEFC55FDF0403B98A0BCE3AD71F3D6
xmb_plugin_normal OFW 4.82: 9EDEFC55FDF0403B98A0BCE3AD71F3D6

3 files were altered between 4.70 and 4.82. Gonna download more firmwares and see how far backwards compatibility can be taken.

On second thought, I won't be removing the 6 images from my rar. Just because Rebug didn't alter the images in their OS doesn't mean they weren't altered in other CFW ;) and as long as it's installed on the correct firmware this should theoretically work on any CFW.
 
Last edited:
explore_category_game OFW 4.76: 2CF61ACD5799E417D164EE4EF5A434C8
explore_category_game OFW 4.82: F73414F4D2475621A3CFD05163ACC6A8
explore_category_psn OFW 4.76: AFCDD7AB77294747F9681BD8672220D9
explore_category_psn OFW 4.82: AFCDD7AB77294747F9681BD8672220D9
explore_category_video OFW 4.76: 825AA07B4FB0E5B13890BEC3963DAE52
explore_category_video OFW 4.82: 825AA07B4FB0E5B13890BEC3963DAE52
explore_plugin_full OFW 4.76: 2B32DBA27785971AE03FF2AB43CE62FB
explore_plugin_full OFW 4.82: DB47D79296CEEDE41AF7E43D27E81F92
npsignin_plugin OFW 4.76: FAB1DE45A7FD293E704B2730F895CC7E
npsignin_plugin OFW 4.82: 6F498DD327E2B56E60EDEC8EA84D1B36
wboard_plugin OFW 4.76: 01013194C96A3A501D7B4C9A2664C2F8
wboard_plugin OFW 4.82: 01013194C96A3A501D7B4C9A2664C2F8
xmb_ingame OFW 4.76: 04ED4ECCA76C6927154470CC8E497B83
xmb_ingame OFW 4.82: 04ED4ECCA76C6927154470CC8E497B83
xmb_plugin_normal OFW 4.76: 9EDEFC55FDF0403B98A0BCE3AD71F3D6
xmb_plugin_normal OFW 4.82: 9EDEFC55FDF0403B98A0BCE3AD71F3D6

I'm posting these here for reference purposes, since I'm checking the hashes anyway. Next I'm trying 4.80.
 
Last edited:
explore_category_game OFW 4.80: F73414F4D2475621A3CFD05163ACC6A8
explore_category_game OFW 4.82: F73414F4D2475621A3CFD05163ACC6A8
explore_category_psn OFW 4.80: AFCDD7AB77294747F9681BD8672220D9
explore_category_psn OFW 4.82: AFCDD7AB77294747F9681BD8672220D9
explore_category_video OFW 4.80: 825AA07B4FB0E5B13890BEC3963DAE52
explore_category_video OFW 4.82: 825AA07B4FB0E5B13890BEC3963DAE52
explore_plugin_full OFW 4.80: DB47D79296CEEDE41AF7E43D27E81F92
explore_plugin_full OFW 4.82: DB47D79296CEEDE41AF7E43D27E81F92
npsignin_plugin OFW 4.80: 6F498DD327E2B56E60EDEC8EA84D1B36
npsignin_plugin OFW 4.82: 6F498DD327E2B56E60EDEC8EA84D1B36
wboard_plugin OFW 4.80: 01013194C96A3A501D7B4C9A2664C2F8
wboard_plugin OFW 4.82: 01013194C96A3A501D7B4C9A2664C2F8
xmb_ingame OFW 4.80: 04ED4ECCA76C6927154470CC8E497B83
xmb_ingame OFW 4.82: 04ED4ECCA76C6927154470CC8E497B83
xmb_plugin_normal OFW 4.80: 9EDEFC55FDF0403B98A0BCE3AD71F3D6
xmb_plugin_normal OFW 4.82: 9EDEFC55FDF0403B98A0BCE3AD71F3D6

All right! Now were getting somewhere! Backwards compatible to 4.80, now I just gotta test 4.78 and I'm done :)
 
Wow guys, what an effort and power to create something wonderful for this cfw, thank you. Today I am going to play more with these icons, to see, what's causing the missing clock and the photo gallery app.
 
Dude, scroll up and use the link I posted :) installing that will fix your clock, and restore your icons back to the originals :P
 
imkira3 said:
Btw, I don't think you mentioned, but the original rco files all use zlib compression, this is important to know when recompiling.
Click to expand...
Yes, but this doesnt have much importance though, just for curiosity sake (and because the way how is represented in rcomage is a bit confusing), the rco internal structure have an area at top that works as an "index" and also contains all the info rcomage extracts as the main xml (but is not an xml when inside the rco). This area is what you can choose to compress in zlib in rcomage, the size reduction is small
After that it comes all the files, and for every file you can choose compression (none, zlib or lzma iirc)... this is set in the main xml (if you look at it in notepad, you have the files under <ImageTree> and for every image an attribute (compression="zlib"), by changing this you can choose the compression type "per file"
Usually (but not always) all the files are compressed in zlib, and the index at top in zlib too
imkira3 said:
Btw, love your profile image lmao
Click to expand...
Lulz, i made it lof of time ago, is a tribute to 2 things i like, videogames and bob marley music :)

imkira3 said:
Hmmm, did you know that javascript automatically puts https on all links? That's all well and good, however, unless I disable javascript when I post it fucks with my mediafire links. They all gave me errors when I tested. Maybe it wouldn't do that if it already had http:// in fron't, but mediafire keeps things simple, it only uses www.

I wonder how many posts have been fucked up in this way unbeknownst to it's poster...... :(
Click to expand...
I have javascript disabled too, and for me works fine, i usually paste the link and no worry, sometimes i use the [url=www.etc.here]LINK NAME[/url] (and same with IMG) by typing it manually, is easy to remember
imkira3 said:
I had a look at those images you mentioned, and you are right, the 6 images you mentioned were unaltered. I'll be removing them from the rar. No need to update your changelog. I have extracted the dev_flash from 4.70 and am doing the appropriate hash checks now.
Click to expand...
I think is better to remove them because is only for rebug, if the 6 images are the same then is pointless to overwrite them
Also, maybe this helps a bit to reduce the total file sizes, so can be copyed to flash in less steps

Let me think a bit about this hashes you are posting and i will give you a suggestion, by now it seems it can be said the files are fully compatible since 4.80 up to 4.82 right ?
 
sandungas said:
Yes, but this doesnt have much importance though, just for curiosity sake (and because the way how is represented in rcomage is a bit confusing), the rco internal structure have an area at top that works as an "index" and also contains all the info rcomage extracts as the main xml (but is not an xml when inside the rco). This area is what you can choose to compress in zlib in rcomage, the size reduction is small
After that it comes all the files, and for every file you can choose compression (none, zlib or lzma iirc)... this is set in the main xml (if you look at it in notepad, you have the files under <ImageTree> and for every image an attribute (compression="zlib"), by changing this you can choose the compression type "per file"
Usually (but not always) all the files are compressed in zlib, and the index at top in zlib too
Click to expand...

Yeah the difference is small, I tested with an rco and found the difference with one file to be the difference between 237kb and about 400-450kb. But when you keep in mind how little space is free in dev_flash, well, it does become significant.

sandungas said:
Lulz, i made it lof of time ago, is a tribute to 2 things i like, videogames and bob marley music :)
Click to expand...

Lulz, seeing all the weed symbols, I had to comment. It's legalization day in Canada :P for the first time I can smoke legally. :D Took them long enough.

sandungas said:
I have javascript disabled too, and for me works fine, i usually paste the link and no worry, sometimes i use the [url=www.etc.here]LINK NAME[/url] (and same with IMG) by typing it manually, is easy to remember
Click to expand...

You may have javascript disabled, but what about the other users? How many links will be corrupted if you ignore this issue?

sandungas said:
I think is better to remove them because is only for rebug, if the 6 images are the same then is pointless to overwrite them
Also, maybe this helps a bit to reduce the total file sizes, so can be copyed to flash in less steps

Let me think a bit about this hashes you are posting and i will give you a suggestion, by now it seems it can be said the files are fully compatible since 4.80 up to 4.82 right ?
Click to expand...

The entire folder was only about 2mb, free space on dev_flash by default in Rebug is about 3mb. And without any alterations this should be compatible with other CFW too, and those CFW may have altered those images as well, or the user may have installed some custom images at one point. It just makes sense to leave them in. And yup, working from 4.80 to 4.82, now I just gotta test 4.78 and I'm done :)

Speak of the devil, 4.78 just finished downloading
 
vr6cer said:
Wow guys, what an effort and power to create something wonderful for this cfw, thank you. Today I am going to play more with these icons, to see, what's causing the missing clock and the photo gallery app.
Click to expand...

explore_category_game OFW 4.78: 2CF61ACD5799E417D164EE4EF5A434C8
explore_category_game OFW 4.82: F73414F4D2475621A3CFD05163ACC6A8
explore_category_psn OFW 4.78: AFCDD7AB77294747F9681BD8672220D9
explore_category_psn OFW 4.82: AFCDD7AB77294747F9681BD8672220D9
explore_category_video OFW 4.78: 825AA07B4FB0E5B13890BEC3963DAE52
explore_category_video OFW 4.82: 825AA07B4FB0E5B13890BEC3963DAE52
explore_plugin_full OFW 4.78: 2B32DBA27785971AE03FF2AB43CE62FB
explore_plugin_full OFW 4.82: DB47D79296CEEDE41AF7E43D27E81F92
npsignin_plugin OFW 4.78: FAB1DE45A7FD293E704B2730F895CC7E
npsignin_plugin OFW 4.82: 6F498DD327E2B56E60EDEC8EA84D1B36
wboard_plugin OFW 4.78: 01013194C96A3A501D7B4C9A2664C2F8
wboard_plugin OFW 4.82: 01013194C96A3A501D7B4C9A2664C2F8
xmb_ingame OFW 4.78: 04ED4ECCA76C6927154470CC8E497B83
xmb_ingame OFW 4.82: 04ED4ECCA76C6927154470CC8E497B83
xmb_plugin_normal OFW 4.78: 9EDEFC55FDF0403B98A0BCE3AD71F3D6
xmb_plugin_normal OFW 4.82: 9EDEFC55FDF0403B98A0BCE3AD71F3D6

Looks like it should be backwards compatible as far back as 4.80 on any CFW, and no further. I bet these MD5's will be useful to anybody looking to make this work on an older CFW. I feel I have done enough though :D now I'll go edit the info into the title of my rar, the readme, the tutorial thread, past posts, and the title of the tutorial thread. Then it's time for another coffee. And @vr6cer, in case you missed my message, SCROLL UP! I posted a link that should solve all your theme and clock issues! I even sent you a message about it :-p I'll be editing the link soon, so if you get a 404, don't worry. Just wait a few minutes and the new link will be online :)

What is causing your issue is actually quite simple, if the size or location listed in the rco file you used (from the wrong OFW you said) is even a little off, it can cause your clock or any icon really to wind up in the wrong location. My guess is your clock IS in fact being shown, it's just being shown outside the border of the screen. That is why you are supposed to use files from the same firmware, it's VERY IMPORTANT!

I believe @sandungas pointed this out.

Yep, he did mention it in post 19. Remember dude, nothing is more irritating then helping someone only to have them not read their messages.

Simply install the files in my rar, they are from 4.82 and should fix your clocks position.
 
Last edited:
I made a table in wiki with the hashes, and a screenshoot to post it here
nvZt4X5.jpg

I know, i could have made the table with files in rows and firmwares in columns, but before starting i thought it was better this way, because is intended for rebug only, and this rco files are the only ones needed to worry about in rebug
Here can be seen well in a fast overview the files changed in 4.80 :)
To know what was changed in 4.80... this is another longer story, but without further research is safe to say the compatibility is 4.80-4.82

imkira3 said:
You may have javascript disabled, but what about the other users? How many links will be corrupted if you ignore this issue?
Click to expand...
Sorry i misundertood yu, i thought you was saying you was having problems with javascript enabled, and i was trying to explain i dont have that problems with javascript disabled, but i got you now
I dont know when/why happens that problems of automatic completion of URLs made by the code corrector of the forum, i never noticed it before, but you can report it here http://www.psx-place.com/forums/feedback-suggestions.19/

imkira3 said:
The entire folder was only about 2mb, free space on dev_flash by default in Rebug is about 3mb. And without any alterations this should be compatible with other CFW too, and those CFW may have altered those images as well, or the user may have installed some custom images at one point. It just makes sense to leave them in. And yup, working from 4.80 to 4.82, now I just gotta test 4.78 and I'm done :)
Click to expand...
But the problem is this files are only for rebug, i can tell there is not other cfw using them, so your files are like a "rebug patch" (or a un-rebug style patch) and is pointless to overwrite files that are the same, specially when writing to dev_flash
 
sandungas said:
I made a table in wiki with the hashes, and a screenshoot to post it here
nvZt4X5.jpg

I know, i could have made the table with files in rows and firmwares in columns, but before starting i thought it was better this way, because is intended for rebug only, and this rco files are the only ones needed to worry about in rebug
Here can be seen well in a fast overview the files changed in 4.80 :)
To know what was changed in 4.80... this is another longer story, but without further research is safe to say the compatibility is 4.80-4.82
Click to expand...

Thanks! Looks useful!

sandungas said:
Sorry i misundertood yu, i thought you was saying you was having problems with javascript enabled, and i was trying to explain i dont have that problems with javascript disabled, but i got you now
I dont know when/why happens that problems of automatic completion of URLs made by the code corrector of the forum, i never noticed it before, but you can report it here http://www.psx-place.com/forums/feedback-suggestions.19/
Click to expand...

Oh good now I know where to post bugs found on the website :)

sandungas said:
But the problem is this files are only for rebug, i can tell there is not other cfw using them, so your files are like a "rebug patch" (or a un-rebug style patch) and is pointless to overwrite files that are the same, specially when writing to dev_flash
Click to expand...

It's true, I have never heard of another CFW using custom images in this way, but I have seen other rco based themes online. Like the green theme designed for Rebug that I reverse engineered to find where the images to replace the "What's New" icon were supposed to be placed. My point is it's harmless to include the extra image files, in fact, if somebody installed a theme they didn't like they could be quite useful to restore things back to normal. I get what you mean though, it's original purpose was for Rebug and Rebug alone, but you never know, somebody out there may have screwed up their images somehow without backing things up, and may want a way to restore their images back to normal. Not only is including the extra files harmless, under very specific conditions where those files were replaced, it could be useful as a form of recovery. Of course there is the extra image for the Rebug Package Manager to consider, but I doubt having an extra unused image in the index for non-rebug CFW's would cause any harm.
 
By publishing it as something generic (not specific for rebug) you are overcomplicating the installation for rookies (i mean... in the actual format you have released the files). There is going to be people that are going to overwrite 6 unneeded files, and you are going to need to add an explaination in the readme.txt with something like "dont copy this 6 images incase...blablabla" (you know, the kind of thing hard to explain in short, or containing too much scene slang not understandable for rookies)

And im thinking... to make the installation more noob friendly (and also safer) it could be made a PKG to overwrite the files in flash :)
@DeViL303 is the man, i guess is pretty much the same procedure than what does the HAN toolbox PKG installation

But if someone does the PKG installer remove the 6 additional images we was talking about dudes, sorry but i have to insist in it, this is a "rebug patch only" and is only compatible with rebug REX 4.80, 4.81 and 4.82 firmwares based on CEX (not sure if could be applyed to D-REX and DECR rebug firmwares)
If eventually someone makes a PKG installer, then is more obvious that is better to remove the 6 images
And the reason why is "rebug only" is because you are including the explore_plugin_full.rco with custom contents that are specific for the "rebug package manager", otherway if the user have a different firmware and wants to revert back the visual style of the RCOs to the official look the best way is to extract the official rco files from pup and overwrite them (no special procedures with explore_plugin_full.rco). In other words the file that is "rebug only" is explore_plugin_full.rco but because you are publishing all them together then all them becomes a "pack" compatible with "rebug only"



Edit:
And you should include also http://www.psdevwiki.com/ps3/Coldboot.raf
Is the same file since 2.70 up to 4.82 (never was updated) MD5:FBFD819D6CD834AC2BDDA02EE3D5375F
 
Last edited:
sandungas said:
By publishing it as something generic (not specific for rebug) you are overcomplicating the installation for rookies (i mean... in the actual format you have released the files). There is going to be people that are going to overwrite 6 unneeded files, and you are going to need to add an explaination in the readme.txt with something like "dont copy this 6 images incase...blablabla" (you know, the kind of thing hard to explain in short, or containing too much scene slang not understandable for rookies)

And im thinking... to make the installation more noob friendly (and also safer) it could be made a PKG to overwrite the files in flash :)
@DeViL303 is the man, i guess is pretty much the same procedure than what does the HAN toolbox PKG installation

But if someone does the PKG installer remove the 6 additional images we was talking about dudes, sorry but i have to insist in it, this is a "rebug patch only" and is only compatible with rebug REX 4.80, 4.81 and 4.82 firmwares based on CEX (not sure if could be applyed to D-REX and DECR rebug firmwares)
If eventually someone makes a PKG installer, then is more obvious that is better to remove the 6 images
And the reason why is "rebug only" is because you are including the explore_plugin_full.rco with custom contents that are specific for the "rebug package manager", otherway if the user have a different firmware and wants to revert back the visual style of the RCOs to the official look the best way is to extract the official rco files from pup and overwrite them (no special procedures with explore_plugin_full.rco). In other words the file that is "rebug only" is explore_plugin_full.rco but because you are publishing all them together then all them becomes a "pack" compatible with "rebug only"
Click to expand...

I have tested this on DEX and it works fine. In any case, even if it's main purpose is for Rebug it can still be used for another OS. I do intend to test it on Ferrox on my L01 model just to be sure it won't cause any issues, if it does then I could always have 2 installation methods, I was already intending to make a pkg lol. For example, running it normal could be for rebug, but running it while holding start or something could restore the original explore_plugin_full.rco instead of the modified one. Regardless, I see no reason to omit the 6 images from MY release. Feel free to make your own if you want. To be clear, this is NOT just for rebug. With a few simple tweaks it can also be used as an XMB icon recovery tool, in the event somebody were to screw up their icons. In the event of a normal installation, the extra 6 icons will not cause any issues, as you would be overwriting the files with the same files. It may be unnecessary, but it won't cause any issues. I see no reason to omit them, even when installing on Rebug. It won't cause any issues since they are the same files.
 
You must log in or register to reply here.

Similar threads

Back
Top