PS3Xploit Temporary Mirror [ps3xploit.me]

Status
Not open for further replies.
While that is true, the biggest reason its simply dangerous to use.




CFW is not piracy. Its rather a Jailbreak.
We have no double standards we have simple to follow rules,
We are a Homebrew & Hacking website, There are MANY things you can do on a jailbroken device that does not involve piracy.
Its those things that this forum has been about, Which is what most of the developer's in the scene are about.
Usually its the fly by night posters like yourself, Whom to seem to think they know what the "scene " is about.
However the scene is about progressing user idea;s... Not about some kid or overgrown adult sitting in his underwear to mass pirate games. Sorry not us,, no double standard, Rather just common sense in an adult world.

There is no a SINGLE problem with sharing bgtoolset.
WHY WOULD WE NOT WANT TO SHARE IT? the creator is @bguerville He happens to be one of those mods you speak of. .. The problem is THAT IS NOT BGTOOLSET. ANYONE CAN MAKE IT LOOK LIKE IT.. .

Rather its someone who reversed PARTIALLY some of the toolset functions in a rather sloppy way and is incomplete. But that person did not do it to disturbe it because they understood the danger's and explained it was incomplete. So someone else who has very little knoweldge put it up on their website and distributed.. The creator bguerville has warned of the dangers and incompleteness..

They choose to act like they know more then the guy who created it as you are doing as well.. So knowing what we do about the situation that is why we do not allow the INCOMPLETE Imposter version of the toolset to be linked here.. Mods are not butthurt, but rather being respectable to the community and protecting user's



Does not seem like he has a problem, but seems like you have a problem.
Good Luck with that

The only problem with bgtoolset is that it's offline and nobody knows when it's coming back if at all. bguerville after all owes us nothing (maybe except for the donors who helped pay for hosting, but I don't remember him promising anything). Meanwhile people are getting desperate and impatient, making them use dangerous alternatives which may or may not work and may or may not brick the console.

I have to agree that keeping an up-to-date offline solution is important. Even if bgtoolset comes back eventually, even if it's a lot more user friendly and even if most people prefer it, you can't base the entire CFW community around a single person's website which probably will not stay online forever, seeing that eventually most people have family and kids and can't keep supporting hobby projects forever. The community needs some sort of backup.
 
First post for me here, my goal is to downgrade to an old enough OFW, so that I can install Linux using the original OtherOS mechanism.
Reading all the threads I could find, I am left with a single question: it's not clear to me IF the developer of BG toolset will make his excellent project publicly available again, rather than when.
I am perfectly happy waiting, and while I fully understand and respect that he does not owe the community anything at all, it would be great if at least he could clarify that point...
 
The only problem with bgtoolset is that it's offline and nobody knows when it's coming back if at all. bguerville after all owes us nothing (maybe except for the donors who helped pay for hosting, but I don't remember him promising anything). Meanwhile people are getting desperate and impatient, making them use dangerous alternatives which may or may not work and may or may not brick the console.

I have to agree that keeping an up-to-date offline solution is important. Even if bgtoolset comes back eventually, even if it's a lot more user friendly and even if most people prefer it, you can't base the entire CFW community around a single person's website which probably will not stay online forever, seeing that eventually most people have family and kids and can't keep supporting hobby projects forever. The community needs some sort of backup.

But we do know all we have to do is look at @bguerville most recent post and it explains the situations.
His timetable might be off but doing it RIGHT does take some time and when you have a personal life,
It will be back but for it to be right it might take some time.
Him and @esc0rtd3w have already mentioned HEN is much easier to merge to the new domain where as the toolset will take more time. So that is all we are seeing.

NO ONE IS MAKING THEM USE DANGER ALTERNATIVE"s, that be the individual user who has made that choice and not listen to the proper people or were patient to wait.



.
 
I've been waiting rather [im]patiently for the toolset, checking the site every few days. I come check this post to see if BG has made any progress and it seems I missed some drama. I know we're all anxious to get back to our PS3s but some folks really need to keep in mind - this is not a paid service. I think it's best to let the people who created the proper work update said work accordingly. And who knows? Maybe buying them a cup of coffee might help with the grueling hours of testing.
:oie mgkkvf2kykyi:
 
Bad Scene advice on Social Media....

LoL Never....

Seen mentions of it myself a few times, unfortunately. I've seen someone here report a bricked console from using an unofficial mirror. I've also seen someone in my comments section mention they patched their NAND model console and it just hung at 90% of the patching process for 30+ minutes.

Someone can correct me if I'm wrong, but I'm pretty sure the amount of true bricks we've seen from the official PS3 Toolset is zero.
 
Someone can correct me if I'm wrong, but I'm pretty sure the amount of true bricks we've seen from the official PS3 Toolset is zero.

If I recall correctly, there have been a couple of cases but not because of Bgtoolset but from issues happening during the patching process (which is the most critical part as it is writing into the flash memory) as the toolset patched one ROS region at a time, or maybe because of the so called "Layer 8 Error" (human error).
 
Last edited:
Seen mentions of it myself a few times, unfortunately. I've seen someone here report a bricked console from using an unofficial mirror. I've also seen someone in my comments section mention they patched their NAND model console and it just hung at 90% of the patching process for 30+ minutes.

Someone can correct me if I'm wrong, but I'm pretty sure the amount of true bricks we've seen from the official PS3 Toolset is zero.

The official contains many checks and has various Safety features that are not present in the Imitation.

That is why @bguerville was warning about its usage. The way it was "reversed" (which was not done by the russian site but someone else, they just cloned his work WITHOUT his warnings) and the way just certain functions were "patched"
was done in a sloppy problematic way. While it can work, it also has a huge brick risk .

This is to anyone, Have to ask yourself why did bguerville put those checks in the first place?
Because they were needed after discoveries in testing and development.

but to answer your question the way the toolset was designed (OFFICIALLY) you could not brick your console.
There was alot of CARE that went to its development.

That why its sad to see the project hijack on apperance and has No where the quality or safety.,
 
If I recall correctly, there have been a couple of cases but not because of Bgtoolset but from issues happening during the patching process (which is the most critial part as it is writing into the flash memory) as the toolset patched one ROS region at a time, or maybe because of the so called "Layer 8 Error" (human error).

There was checks to prevent a bad flash,
Would have to be something like a power outage to have an issue from my understanding
 
There was checks to prevent a bad flash,
Would have to be something like a power outage to have an issue from my understanding

Doing some quick search on the forums, there were reports on bad flash with NAND consoles but it wasn't a full or semi brick situation because of the multiple checks mentioned before. Eventually, that NAND bug got patched and no major cases arised.

Sources:
 
Doing some quick search on the forums, there were reports on bad flash with NAND consoles but it wasn't a full or semi brick situation because of the multiple checks mentioned before. Eventually, that NAND bug got patched and no major cases arised.

Sources:
anybody who came back to this forum after one of those bad flashes was able to get their console fixed a few days later. (the problem was that no pup would install.) has the russian team even offered to fix any recent brick?
 
UPDATE: The original domains **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new)/net/org have been unlawfully seized and resold. They should be considered unofficial and potentially dangerous to use. There will be community hosting at some point soon, which will be the new home of PS3Xploit and other projects. PS3HEN and BG Toolset will be updated to use the new domain, once a name is settled on, and we have everything setup.

For the time being, mostly everything should be working from the .me domain. There was a post by @Coro with a working copy of the Alternate HEN Installer on GitHub, here is the link (https://ps3addict.github.io/alternate/). This link is also on mirror page for now.


The situation is complicated, so i wont bother you with the details.

The BG Toolset is more complex than just moving files, and will most likely be unavailable for a time.

The **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) contents have been mirrored to ps3xploit.me, with a few caveats.
  • The site HTML and JS have been modified with the new domain extension. Any release files are untouched, as this only applies to the site installation web files.
  • The current PS3HEN releases will not be touched, however, the p3t installer files will be rebuilt (saving old ones) to accommodate the .me extension only. This does not affect HEN in any way, but is the file that is used to download the HEN PKG, and will fail if the server domain is not edited.
  • The HEN version check and auto update will fail.
  • Anything that uses **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) as a host will fail, for obvious reasons. This cannot currently be avoided.
**Dangerous Site**
Private server confirmed working.
Just loaded Evilnat 4.89 from this
 
Have seen yet another person using an unofficial Toolset report they did all the steps, but now when they boot up their console it just has a black screen then turns off.

Don't have any other details aside from what they described, but across multiple sites I've been seeing more bricks pop up from using these unofficial Toolsets.
 
I think we are still waiting to hear back about SSL cert issue. There is also another issue with the new domain being flagged as spam, which is so ridiculous that it caught Ben and I by surprise. There is a temp workaround being done right now. I haven't talked to @bguerville in a few days now, but he has been in contact with the hosting and others to get these issues resolved.

Hopefully, the toolset will be available soon.
 
Status
Not open for further replies.
Back
Top