PS3 4.70 HABIB COBRA v7.10 (CEX) CFW v1.01

Custom Firmware developer HABIB is back again with a new update to his 4.70 HABIB COBRA v7.10 (CEX) CFW with the release of v1.01. The developer has provided a few fixes that were causing issues with applications such as PS3 Manager API (PS3M_API) and webMAN MOD, plus a fix to firmware dectection in PS3M_API was also fixed with this latest version of COBRA CFW from Habib [break]ss[/break] Also checkout this custom Habib coldboot by pinky via this link in our forums.

​

4.70 HABIB (CEX) + COBRA v7.10

FEATURES

UPDATE v1.01

FIXED PS3MAPI IDPS SET AND ASSOCIATE APPS CREATING BUGS(E.G WEBMAN)

FIXED PS3MAPI FW DETECTION

MADE OUT OF 4.70 OFW

COBRA v7.10 ADDED (see below)

HAVE INSTALL PACKAGE FILES AND APP_HOME

HAVE REACTPSN COMPATIBILITY

IT CAN RUN GAMES SIGNED WITH KEYS UP TO 4.70

CAN BE UPDATED OVER ANY CFW.

CAN BE UPDATED OVER 3.55 OFW

SPECIAL PAYLOAD FOR COBRA TOGGLE IN LV2

RSOD BYPASS

REMOVED CINAVIA DRM FOR HDD CONTENT

REMOVED CINAVIA FOR BDMV

REMOVED CINAVIA FOR BDVD

QA FLAG ENABLED BY DEFAULT IF PS3 WAS QA ON 3.55

PATCHES

PATCHED LV0 TO DISABLE ECDSA CHECKS

PATCHED LV2 TO ADD PEEK/POKE SUPPORT

PATCHED LV1 TO DISABLE LV2 PROTECTION

PATCHED LV1 TO ADD PEEK/ POKE SUPPORT

REACTPSN OFFLINE PATCH ADDED

COBRA v7.10

Changes in Cobra 7.03 -7.10

Additional PSX ISO Types supported

PS2 ISO controller sync issues on non-BC improved by great margin (100% fine for me)

Updated NzV ps3mapi to v1.2.0

Polished a bit overall

Issue with new ODE Patches while COBRA is disabled has been fixed (games with updates refuse to run)

Video

[video=youtube;uiY1e2t2oqE]https://www.youtube.com/watch?v=uiY1e2t2oqE[/video] Donation to HABIB can be made via: PayPal

USE ANY CFW AT YOUR OWN RISK View ---> LINK <--- for CFW installation Tips & Info

DOWNLOAD & MIRRORS

4.70 HABIB COBRA (v7.10) v1.01 MD5: 30BD5DDAD254FF8CD2336A7E4DEF43CC (MIRRORS Welcomed) SRC CODE

Source: youtube.com / psx-place.com (via HABIB)

---

Via this link you can view Additional CFW / Tools / Homebrew Updates for 4.70
​

 

Don't twist my words. I didn't say one way or the other. if a record of peoples bans was kept then we might be able to see.

Well In order to build REX, at least 500files in dev_flash, need to be modified, mostly sprx modules and a few xml and rco, and every single file in CoreOS has to be compressed due to not enough space in CoreOS caused by dual kernels. There are two many things can be detected considering your perspective, and Please don't forget the fact that using CFW put you guys at risk of ban always. Use CFW at your own risk, and enjoy while you can, SONY usually supports consoles up to ten years like they did to psx/ps2 and psp. What would be the point if all of sudden SONY shut down their PSN for ps3 one day, it would be as the same as being banned. Finally, We are not going to take any responsibilities for ban issues.

From my perspective REX is a way far from being stealth, however I have no intention to change something that hasn't changed since the beginning of the history. It's one of those REBUG traditions, and if this makes you feel unsafe, then please stay away from it.


Sent from my iPhone using Tapatalk

 

I don't go on-line. I'm just curious about what sony etc. are detecting and if there has been any different rates of bans for different cfw and homebrews/backup managers.

 

I don't go on-line. I'm just curious about what sony etc. are detecting and if there has been any different rates of bans for different cfw and homebrews/backup managers.

I don't know what exactly they detecting. But i know that looking for file names or folder names is ussless for sony. You can always change name to some not used files. And then they have nothing.

 

Is multiman and official webman working with this? thanks a lot Habib man your cfw is allways the best

 

Multiman is working in cobra mode. For compatibile official webman read this: http://www.psx-place.com/forum/home...ent-request-webman-4-70-compatibile-1504.html

 

Well In order to build REX, at least 500files in dev_flash, need to be modified, mostly sprx modules and a few xml and rco, and every single file in CoreOS has to be compressed due to not enough space in CoreOS caused by dual kernels. There are two many things can be detected considering your perspective, and Please don't forget the fact that using CFW put you guys at risk of ban always. Use CFW at your own risk, and enjoy while you can, SONY usually supports consoles up to ten years like they did to psx/ps2 and psp. What would be the point if all of sudden SONY shut down their PSN for ps3 one day, it would be as the same as being banned. Finally, We are not going to take any responsibilities for ban issues.

From my perspective REX is a way far from being stealth, however I have no intention to change something that hasn't changed since the beginning of the history. It's one of those REBUG traditions, and if this makes you feel unsafe, then please stay away from it.


Sent from my iPhone using Tapatalk

I'm honestly surprised that any of u continue to make cfw considering how ignorant most of the ps3 scene is. half can't update, and the other half don't understand anything beyond "install pkg." I suppose it's understandable that, based on what I've heard, the ps4 scene will be closed circuit meaning most things will not be made public. my tutorials, which took a lot of time from someone who knows nothing about programming, r totally useless.

 

and, mind u, this is coming from a nondev who's actually helped devs with the ps3. it's very sad how little some "devs" actually know about the system.

 

and, mind u, this is coming from a nondev who's actually helped devs with the ps3. it's very sad how little some "devs" actually know about the system.

I am a bit confused here xD. Anyways,
please don't make fun of us about not reversing anything new since 4.21 cfw, zeco often says this to me a lot lol. At least we have been trying to squeeze juice out of cobra payload which was also originally developed back in late 2011. I am also getting tired of repeating the same stuff.


Sent from my iPhone using Tapatalk

 

I am a bit confused here xD. Anyways,
please don't make fun of us about not reversing anything new since 4.21 cfw, zeco often says this to me a lot lol. At least we have been trying to squeeze juice out of cobra payload which was also originally developed back in late 2011. I am also getting tired of repeating the same stuff.


Sent from my iPhone using Tapatalk

I think u may have misunderstood. u, Habib, Aldo do a tremendous amount of work for the scene (we all appreciate that), but I, as I'm sure is true with many others, don't want u to feel overly burdened by that. that's the main reason I tried to help in the scene. even though I don't have dev knowledge, I tried to help out wherever I could.

 

habib

Do you have to be jailbroken already to install habib 4.70?

 

Do you have to be jailbroken already to install habib 4.70?

None of us needs to "be" jailbroken (just our PS3).


Try reading the first topic !


Sent from a mobile device using Tapatalk

 

None of us needs to "be" jailbroken (just our PS3).


Try reading the first topic !


Sent from a mobile device using Tapatalk

LOL, so you would have to downgrade to 3.55, then jailbreak, then install habib, right?

 

Or could you just install 3.55 on a new hard drive, then jailbreak, then install habib?

 

habib 4.70= OFW 4.55?

Here's the trouble I'm running into:

Downloaded the new CFW from the link provided. Put the file on my external and went to update from the Habib 4.70 non cobra. Said it couldn't find an applicable update. Went into recovery and installed it that way, and when it was done, suddenly I'm back on 4.55 FW, with no package manager or other CFW parts evident.

Tried installing the CFW again the normal way, and it detects 4.70, so I think, alright, cool, now it should work, but when I try to update, it says my file is corrupted (error 8002F165). Deleted that file off my external, and tried to use the non cobra CFW again, and I get the same error.

Anyone know what just happened and what I can do about it?

Running on a CECHA01 (fat, BC), originally had 3.55 and hacked with rebug 3.55, QA flagged, then used Habib CFWs ever since.

 

Here's the trouble I'm running into:

Downloaded the new CFW from the link provided. Put the file on my external and went to update from the Habib 4.70 non cobra. Said it couldn't find an applicable update. Went into recovery and installed it that way, and when it was done, suddenly I'm back on 4.55 FW, with no package manager or other CFW parts evident.

Tried installing the CFW again the normal way, and it detects 4.70, so I think, alright, cool, now it should work, but when I try to update, it says my file is corrupted (error 8002F165). Deleted that file off my external, and tried to use the non cobra CFW again, and I get the same error.

Anyone know what just happened and what I can do about it?

Running on a CECHA01 (fat, BC), originally had 3.55 and hacked with rebug 3.55, QA flagged, then used Habib CFWs ever since.

If you are back to 4.55 without package manager, you just had update your ps3 with official fw... now you have to downgrade (or find someone with E3 flasher) to do it...

 

Here's the trouble I'm running into:

Downloaded the new CFW from the link provided. Put the file on my external and went to update from the Habib 4.70 non cobra. Said it couldn't find an applicable update. Went into recovery and installed it that way, and when it was done, suddenly I'm back on 4.55 FW, with no package manager or other CFW parts evident.

Tried installing the CFW again the normal way, and it detects 4.70, so I think, alright, cool, now it should work, but when I try to update, it says my file is corrupted (error 8002F165). Deleted that file off my external, and tried to use the non cobra CFW again, and I get the same error.

Anyone know what just happened and what I can do about it?

Running on a CECHA01 (fat, BC), originally had 3.55 and hacked with rebug 3.55, QA flagged, then used Habib CFWs ever since.

here's your problem, plain and simple, the disc that you have in your PS3 has OFW 4.55 on it, you have just updated to OFW!! You are no longer Jailbroken [MENTION=2908]kapa[/MENTION]'s advice is your only choice now

 

here's your problem, plain and simple, the disc that you have in your PS3 has OFW 4.55 on it, you have just updated to OFW!! You are no longer Jailbroken [MENTION=2908]kapa[/MENTION]'s advice is your only choice now

That's what I was afraid of. Thanks guys.

 

i have "data is corrupted" please help ;d

 

LOL, so you would have to downgrade to 3.55, then jailbreak, then install habib, right?

not necessarily. this is one bit of misinformation that goes around (mostly content sites). u have to be on 3.55 to install cfw from the xmb or directly. the signing bug is corrected in 3.60, so 3.56 base is actually hackable if u have a system with metldr and bootldr 1. also, if ur on say 4.70 fw, but have the aforementioned ldrs (i.e. 1 and 2k systems), u can install cfw directly to the flash without downgrading. 3.56 base is hackable in this instance as well, but it requires a flasher still.

 

how can i activate the cobra mode