hit tracker

RELEASE: REBUG Cobra v7.02 D-REX & REX Editions

Discussion in 'Codename: REBUG PS3 CFW Releases and Support' started by GaryOPA, Oct 30, 2014.

Thread Status:
Not open for further replies.
  1. 1
    3
    0
    MaTT26

    MaTT26 Loyal Member

    Joined:
    Dec 8, 2014
    Location:
    France
    Don't let one person ruin your enthusiasm REBUG Team. I'm currently using your CFW 4.65.1 and I really enjoy it !
    Thanks for your contributions as Devs on the PS3 scene !
     
    gDrive, DeeLaRoc and STLcardsWS like this.
  2. 14
    0
    0
    kyogo

    kyogo Loyal Member

    Joined:
    Jun 22, 2008
    The only release that I trust is from the official REBUG website.
     
  3. 6
    0
    0
    l3allermann

    l3allermann Loyal Member

    Joined:
    Nov 7, 2014
    True so many guys try bullshit
     
  4. 16
    2
    0
    Rasterian

    Rasterian Loyal Member

    Joined:
    Sep 25, 2013
    I hanged out on this forum when I was new to the PS3 scene and Rebug was in hibernation after 4.46 and the release of Cobra. Just wanted to chime in to say that I am thrilled to learn Rebug lives on. It is great to see so many pieces from the PS3 scnee come together in this firmware, from so many talented developers over the years. It seems to me that this is shaping up to be the firmware to rule them all, and the one that will survive on many CFW PS3s for years to come.

    Congratulations to the whole team, and take your time for the new builds.
     
    dsmalls likes this.
  5. 18
    0
    1
    justeve

    justeve Loyal Member

    Joined:
    Feb 7, 2007
    I can't wait till this gets released .it would be a nice christmas present.
     
  6. 7
    0
    0
    mohsen57

    mohsen57 Loyal Member

    Joined:
    Mar 5, 2012
    i wonder if that PS2 menu issue is solved on your next release?

    I have a BC ps3 and i am on last rebug 4.65.1 cobra , and when i press PS button when playing ps2 games the menu is invisible, please solve this problem.
    also i am having ps2 controller sync problem which a cable must connected to regain sync,

    before of this i want on habib 4.46 cobra, there was no issue with ps2 whatsoever, no sync problem no need for cable it sync automatically, and ps menu is shown very clearly,

    i wonder if these problem will be solved on your upcoming firmware for BC system or not? thanks again for your hard work.
     
  7. 36
    7
    0
    wa7ly

    wa7ly Loyal Member

    Joined:
    Jul 11, 2014
    It looks like the rebug team has done it again! They have fixed the ps2 emu issues....check it out....

    http://psx-scene.com/forums/content...at-pesky-PS2-Sync-Issues-for-Semi-BC-Consoles
     
    mohsen57 likes this.
  8. 7
    0
    0
    mohsen57

    mohsen57 Loyal Member

    Joined:
    Mar 5, 2012
    this only saying about sync issue, i was mean ps2 menu when you play ps2 games on ps3 BC, i want to know the menu is visible or not,
    on that article it didn't mention about this at all, so that's why i asked here from team but no answer yet.
     
  9. 924
    439
    63
    Joonie86

    Joonie86 Developer for Team Rebug Developer

    Joined:
    Nov 11, 2012
    Occupation:
    System Admin
    Location:
    dev_blind
    Home Page:
    http://rebug.me
    If you look at video carefully, You won't see any glitching menu... that was the whole point of fix..

    BC/Semi Bc consoles have never had issues with sync since CFW 4.53
     
    mohsen57 likes this.
  10. 7
    0
    0
    mohsen57

    mohsen57 Loyal Member

    Joined:
    Mar 5, 2012
    Thank you Joonie86,

    actually i never watched that youtube video, because it is blocked on my country,
    so when you say look video, i tried to see that video ...
    and it was indeed great and there was no problem and bug, now i sure my ps3 BC will have latest firmware with all cool ps2 feature with no bug,

    Thanks again,

    BTW, when you gonna publish this firmware ?
    i am waiting.

    Regards,
     
  11. 128
    5
    18
    Nicolas

    Nicolas Loyal Member

    Joined:
    Mar 1, 2012
    Location:
    I.R.IRAN
    Hi @Joonie86 ,how are you?
    i got one questions,as you know,there is an awesome application that has been released by Rebug called Coldboot Installer and unfortunately has not been updated for new CFWs (4.XX) yet,do you have any comment about this?is there any way for adding that in Rebug Toolbox?
    Last year,evilsperm (i'm not sure who said that exactly) promised to me that Rebug team will release new version of this application but nothing have been released yet
    I hope it wont release when the hell freezes Over
    Thanks for your hard working
     
    Ganj3r and STLcardsWS like this.
  12. 11
    0
    0
    XxUnkn0wnxX

    XxUnkn0wnxX Loyal Member

    Joined:
    Oct 28, 2012
    does this version have support for Debugging games with Debug Self? or just eboot?

    and will rebug ever bring in support for debugging with self?
     
  13. 400
    5
    18
    windrider42

    windrider42 Loyal Member

    Joined:
    Apr 23, 2007
    Occupation:
    SE
    Location:
    Alberta
    .

    Using rebug toolbox v2.01.05, ftp and using ps3ita you can change the Coldboot.

    I haven't tested on latest 4.xx but it does work on earlier 4.xx firmwares

    @evilsperm.... been long time. Looking forward to your latest release.
     
    Ganj3r likes this.
  14. 168
    1
    0
    Peppsi

    Peppsi Loyal Member

    Joined:
    Nov 17, 2011
    Is there any actual news on if the new 4.65.2 is going to be released. Seeing Habib basically saying he's left it doesnt sound good. Can we just get an official word, I'm happy on my 4.55 but would still like the choice of a new 'official' rebug.
     
  15. 400
    5
    18
    windrider42

    windrider42 Loyal Member

    Joined:
    Apr 23, 2007
    Occupation:
    SE
    Location:
    Alberta
    Well knowing evilsperm and cyberskunk if they say "UPDATE INCOMING" It will happen

    seeing just like what happened with Rogero latest release, I am sure they will just keep quiet until an update is fully tested for release.
    Have patience is all I can say when it comes to good releases.
     
  16. 924
    439
    63
    Joonie86

    Joonie86 Developer for Team Rebug Developer

    Joined:
    Nov 11, 2012
    Occupation:
    System Admin
    Location:
    dev_blind
    Home Page:
    http://rebug.me
    Sorry for the late response, I have been quite busy with finalizing our pups, [REX/D-REX]

    evil had lost most of previous resources due to host changes, I do not have the source of that older version,

    Currently I have no plan to add function to install coldboot, it's quite easy to do manually with the method that @windrider42 explained,

    A long wait is finally over, We are now preparing the official release of 4.65.2 / Cobra 7.03 features.

    Cobra core is disabled by default, old users can use REBUG 4.65.2 without cobra payload if they wish,



    Unfortunately there is no plan to release Lite edition since there have been too many good 4.65 standard cfw pups. and also no plan to release cfw without cobra payload as cobra is disabled by default, users won't be able to notice any differences between Standard REX and REX with Cobra. I guess there is no point of releasing 4 different PUPs with the same feature can be provided by default setup.

    Built-in 4.66 spoof is included to support PSN/SEN access, this can be enabled by REBUG TOOLBOX.

    Simply set REBUG mode will swap the vsh that has version spoofed to 4.66 will allow you to use PSN/SEN access.



    Unfortunately, due to VSH patches for CEX mode, NPDRM Fself is impossible to launch while on DEX mode.
    This is a limitation of REX due to hybrid CFW between CEX and DEX, although there are two possible ways to support this NPDRM fself compatibility.

    1. By using Cobra core to disable vsh patches to support full Fself files
    2. Provide custom vsh file that supports NPDRM fself

    Previous REBUG REX CFW never supported this since 4.xx era, and currently no plan to work on this.

    I'll keep you guys updated. Thanks for those of whom waited for us. I hope our work could meet your expectation.

    Regards,
     
    windrider42, Nicolas, dsmalls and 2 others like this.
  17. 3
    1
    0
    Chnorzy

    Chnorzy Loyal Member

    Joined:
    Jan 7, 2015
    I'm so glad you took your time to finalize something really great.
    Good work needs time and the result will be amazing :)
     
  18. 388
    23
    18
    dsmalls

    dsmalls Loyal Member

    Joined:
    Dec 3, 2011
    Location:
    Nothern Hemisphere
    Looking forward to this. Patching eboots is a pain in the ass. :)
     
  19. 34
    35
    18
    Gamma Argon

    Gamma Argon Loyal Member

    Joined:
    Jul 11, 2013
    @patching eboots - if that is for error 8001003C and your custom firmware has the required key revision, you can use a lv2 patcher to patch the function that checks the sdk version.
    The lv2 function that checks the sdk version ends like this:
    li r3, 0
    extsw r3, r3
    blr

    here's a patch from 3.41 that pastes the end up to the beginning of the function (skipping checks):
    Code:
    location to patch for 3.41:
    at 002821FC:  80 03 02 6C 3D 60 00 34 3D 20 1B 43 2F 80 FF FF
    the patch:    38 60 00 00 7C 63 07 B4 4E 80 00 20
    poke:         38 60 00 00 7C 63 07 B4 4E 80 00 20 2F 80 FF FF
    
    here is the source code for a simple app applying that patch
    also added support for 355, 421, 446, 455, 460, 465
    Code:
    static FILE *fp_log;
    
    int lv2_patch(void)
    {
    	//	patch for error 8001003c
    	//	original values should be:
    	//uncomment the firmware version of the lv2 to be patched
    	//for 341 at 0x002821FC : 0x8003026C3D600034 , 0x00282204 : 0x3D201B432F80FFFF
    //	uint64_t default_value[]={0x8003026C3D600034ULL, 0x3D201B432F80FFFFULL};
    	//for 355 at 0x0028A404 : 0x8003026C3D600035 , 0x0028A40C : 0x3D201B432F80FFFF
    //	uint64_t default_value[]={0x8003026C3D600035ULL, 0x3D201B432F80FFFFULL};
    	//for 421 at 0x00296268 : 0x8003026C3D600042 , 0x00296270 : 0x3D201B432F80FFFF
    //	uint64_t default_value[]={0x8003026C3D600042ULL, 0x3D201B432F80FFFFULL};
    	//for 446 at 0x00297314 : 0x8003026C3D600044 , 0x0029731C : 0x3D201B432F80FFFF
    //	uint64_t default_value[]={0x8003026C3D600044ULL, 0x3D201B432F80FFFFULL};
    	//for 455 at 0x00271040 : 0x8003026C3D600045 , 0x00271048 : 0x3D201B432F80FFFF
    	uint64_t default_value[]={0x8003026C3D600045ULL, 0x3D201B432F80FFFFULL};
    	//for 460 at 0x0026FDD8 : 0x8003026C3D201B43 , 0x0026FDE0 : 0x3D201B432F80FFFF
    //	uint64_t default_value[]={0x8003026C3D201B43ULL, 0x3C6080012F80FFFFULL};
    	//for 465 at 0x0026FDE0 : 0x8003026C3D201B46 , 0x0026FDE8 : 0x3D201B432F80FFFF
    //	uint64_t default_value[]={0x8003026C3D600046ULL, 0x3D201B432F80FFFFULL};
    
    	//address for 341 for 8001003C error
    //	uint64_t address[] = {0x80000000002821FCULL, 0x8000000000282204ULL};
    	//address for 355 for 8001003C error
    //	uint64_t address[] = {0x800000000028A404ULL, 0x800000000028A40CULL};
    	//address for 421 for 8001003C error
    //	uint64_t address[] = {0x8000000000296268ULL, 0x8000000000296270ULL};
    	//address for 446 for 8001003C error
    //	uint64_t address[] = {0x8000000000297314ULL, 0x800000000029731CULL};
    	//address for 455 for 8001003C error
    	uint64_t address[] = {0x8000000000271040ULL, 0x8000000000271048ULL};
    	//address for 460 for 8001003C error
    //	uint64_t address[] = {0x800000000026FDD8ULL, 0x800000000026FDE0ULL};
    	//address for 465 for 8001003C error
    //	uint64_t address[] = {0x800000000026FDE0ULL, 0x800000000026FDE8ULL};
    	
    	//patch for 8001003C error
    	//	poke(0x00296268, 0x386000007C6307B4);
    	//	poke(0x00296270, 0x4E8000202F80FFFF);
    	uint64_t patch_value[] = {0x386000007C6307B4ULL, 0x4E8000202F80FFFFULL};
    	
    	//look first before patching to see if the current value in lv2 is correct
    	uint64_t current_value[2];	
    	//look to see that the patch was applied properly
    	uint64_t patched_value[2];
    
    	//peek at lv2 to see what's there
    	current_value[0] = peek(address[0]);
    	current_value[1] = peek(address[1]);
    	
    	if (fp_log) fprintf(fp_log, "\ncurrent value at address 0x%16llX is 0x%16llX", address[0], current_value[0]);
    	if (fp_log) fprintf(fp_log, "\ncurrent value at address 0x%16llX is 0x%16llX", address[1], current_value[1]);
    	
    	//check location to patch
    	if ((current_value[0] == default_value[0]) && (current_value[1] == default_value[1]))
    		{
    			if (fp_log) fprintf(fp_log, "\n\npatching lv2...");
    			poke(address[0], patch_value[0]);
    			poke(address[1], patch_value[1]);
    			
    			//check if patch written
    			if (fp_log) fprintf(fp_log, "\n\nchecking patch...");
    			patched_value[0] = peek(address[0]);
    			patched_value[1] = peek(address[1]);
    			if (fp_log) fprintf(fp_log, "\n\n1st patched value is 0x%16llX", patched_value[0]);
    			if (fp_log) fprintf(fp_log, "\n2nd patched value is 0x%16llX\n", patched_value[1]);
    		
    			if ((patched_value[0] == patch_value[0]) && (patched_value[1] == patch_value[1]))
    				{
    					lv2_sm_ring_buzzer(0x1004, 0xa, 0x1b6);
    					//lv2_sm_ring_buzzer(0x1004, 0xa, 0x1b6);
    					return 0;
    				}	
    			return 2;
    		}
    		return 1;
    }
    	
    
    int main(int argc, char **argv)
    {
    	//FILE *fp_log = NULL;
    	int return_value;
    	
    	
    //	if ((fp_log = fopen("/dev_usb000/patch_log.rtf", "w")) == NULL) return -1;
    
    	fp_log = fopen("/dev_usb000/patch_log.rtf", "w");		
    	
    	if (fp_log) {
    		fprintf(fp_log, "\nPatch for lv2 to Skip Error 8001003C Check\n\npreparing to patch lv2...\n");
    	}
    
    	return_value = lv2_patch();
    	
    	//return_value 0 == patch applied, return_value 1 == patch not attempted, return_value 2 == error applying patch
    	if(return_value == 0) {
    		if (fp_log) fprintf(fp_log, "\npatch applied...");
    	}	
    	else if(return_value == 1) {
    		if (fp_log) fprintf(fp_log, "\nincorrect values at patch location, patch not applied...\n");
    	}	
    	else if(return_value == 2) {
    		if (fp_log) fprintf(fp_log, "\nerror writing lv2, patching failed...\n");
    	}
    
    	if (fp_log) {
    		fprintf(fp_log, "\nfinished...");
    		fclose(fp_log);
    	}
    
    	return 0;
    }
    
    I tested it on 4.21. Someone else tested on 4.46. This is an old patch; I don't know where it comes from. It was labeled Rancid-0, so I guess he made it. Requires custom firmware with peek/poke and lv2 protection disabled or ps3 will shut down--use the rebug toolbox first or mM to disable memory protection.
     
    Last edited by a moderator: Jan 8, 2015
    dsmalls likes this.
  20. 18
    2
    3
    Qwee

    Qwee Loyal Member

    Joined:
    Jan 1, 2015
    Dude, do you even know how many consoles bricked because of these "good 4.65 standard CFWs"?
    Just a simple Lite version, without cobra... 3 PUP just like old times, not 4 as you said, that's all I ask for.
     
    mschumacher69 likes this.
Thread Status:
Not open for further replies.

Share This Page