PS3HEN [Support Thread] PS3HEN Bugs, Problems, and Other Issues

[Fucking]

Just download it in a USB device formated in FAT32 MBR

The file must be named PS3UPDAT.PUP and in the following path X:/PS3/UPDATE

Note that X:/ = your drive letter, in other words create a folder named PS3 in the root of your USB device and inside this folder another one named UPDATE and then put the update file inside of it.

Can you explain to me the method too
I want to do anything that is important for the device to work, please

 

[bguerville]

Does it work from wmm? When I tried, it didn't mount from wmm, but did from multiman. Also reloadxmb wasn't working for me with wmm.

@aldostools
Can you also confirm this?

 

[aldostools]

@aldostools
Can you also confirm this?

I'm on CFW Evilnat 4.90 Cobra 8.4. I confirm that app_home (★ PlayStation®3) works after mounting a PS3 game (ISO or folder) through webMAN MOD.

However it looks like there are some games that doesn't work from app_home (cause a black screen) but they play fine from dev_bdvd. For instance CoD: Black Ops doesn't work from app_home, but CoD: Black Ops III works.

Also tested with Mamba 8.4 with the same results. Reload XMB is giving me error 80010009 on Mamba, but not in Cobra. It should be a missing patch in the last port to 4.90.

 

[Fredy66]

@aldostools
Can you also confirm this?

I sent you a debug log via pm yesterday

 

[bguerville]

I sent you a debug log via pm yesterday

I know, thanks but there's no need for me to debug the new HEN mapping code if it never introduced any problem with app_home in the first place, which is why I am asking people to confirm what LuanTeles posted ie multiman can mount games to app_home with HEN 3.2.2 whereas wMM cannot.
Can more people test this and report?

 

[Fucking]

Why so much hate every time I ask no one replies
I installed ccapi on ps3hen I know I didn't have to install it. The important thing is that even when I download hfw nothing happens and the screen stays black. Please, whoever has the solution, don't skimp on us.

 

[esc0rtd3w]

Why so much hate every time I ask no one replies
I installed ccapi on ps3hen I know I didn't have to install it. The important thing is that even when I download hfw nothing happens and the screen stays black. Please, whoever has the solution, don't skimp on us.

What model do you have?

When we originally released HEN, we gave the warnings about ccapi and FSM potentially causing bricks. None of us at the time were able to test installing ccapi on the emmc model, to confirm if it was a soft brick or a hard brick.

It seems for NOR and older NAND consoles this can be solved by replacing/formatting the hard drive, but eMMC consoles, with mtldr.2 may not be able to recover without hardware flashing.

We are currently working on a way to block ccapi from launching on HEN.

In the same regard, FSM was never tested on these consoles, but that will also cause the console to be in a currently unrecoverable state.

 

[Fucking]

[QUOTE = "esc0rtd3w ، post: 363956 ، عضو: 28568"] ما هو الموديل الذي لديك؟

عندما أطلقنا في الأصل HEN ، قدمنا التحذيرات بشأن ccapi و FSM التي يحتمل أن تسبب الطوب. لم يكن أي منا في ذلك الوقت قادرًا على اختبار تثبيت ccapi على طراز emmc ، للتأكد مما إذا كان لبنة ناعمة أو لبنة صلبة.

يبدو أنه بالنسبة لوحدات التحكم NOR و NAND الأقدم ، يمكن حل ذلك عن طريق استبدال / تهيئة محرك الأقراص الثابتة ، ولكن قد لا تتمكن وحدات تحكم eMMC ، باستخدام mtldr.2 ، من الاسترداد بدون وميض الأجهزة.

نحن نعمل حاليًا على طريقة لمنع ccapi من الانطلاق على HEN.

في نفس السياق ، لم يتم اختبار FSM مطلقًا على وحدات التحكم هذه ، ولكن هذا سيؤدي أيضًا إلى أن تكون وحدة التحكم في حالة غير قابلة للاسترداد حاليًا. [/ QUOTE]
Sorry but I didn't understand what you said what am I going to do now
On the idea I have a proper

 

[esc0rtd3w]

[QUOTE = "esc0rtd3w ، post: 363956 ، عضو: 28568"] ما هو الموديل الذي لديك؟

عندما أطلقنا في الأصل HEN ، قدمنا التحذيرات بشأن ccapi و FSM التي يحتمل أن تسبب الطوب. لم يكن أي منا في ذلك الوقت قادرًا على اختبار تثبيت ccapi على طراز emmc ، للتأكد مما إذا كان لبنة ناعمة أو لبنة صلبة.

يبدو أنه بالنسبة لوحدات التحكم NOR و NAND الأقدم ، يمكن حل ذلك عن طريق استبدال / تهيئة محرك الأقراص الثابتة ، ولكن قد لا تتمكن وحدات تحكم eMMC ، باستخدام mtldr.2 ، من الاسترداد بدون وميض الأجهزة.

نحن نعمل حاليًا على طريقة لمنع ccapi من الانطلاق على HEN.

في نفس السياق ، لم يتم اختبار FSM مطلقًا على وحدات التحكم هذه ، ولكن هذا سيؤدي أيضًا إلى أن تكون وحدة التحكم في حالة غير قابلة للاسترداد حاليًا. [/ QUOTE]
Sorry but I didn't understand what you said what am I going to do now
On the idea I have a proper

Try google translate. I have no other suggestions.

 

[Fucking]

Try google translate. I have no other suggestions.

Already translated but did not understand I beg you if you have a solution do not skimp on us

 

[aldostools]

Already translated but did not understand I beg you if you have a solution do not skimp on us

What console model do you have? CECH-3xxx? CECH-4xxx? SuperSlim? Slim? Phat?

If your console is SuperSlim it's bricked permanently. Otherwise try formatting the internal HDD.
That generally fixes the semi-bricks.

 

[Fucking]

[QUOTE = "aldostools، post: 363966، member: 89"] ما هو طراز وحدة التحكم لديك؟ CECH-3xxx؟ CECH-4xxx؟ نحيف جدا؟ معتدل البنيه؟ فات؟

إذا كانت وحدة التحكم الخاصة بك SuperSlim ، فسيتم معالجتها بشكل دائم. وإلا فحاول تهيئة محرك الأقراص الثابتة الداخلي.
هذا بشكل عام يصلح أنصاف الطوب. [/ QUOTE]
I have a slim CECH-2504B can you fix it

 

[DonKeballs]

[QUOTE = "aldostools، post: 363966، member: 89"] ما هو طراز وحدة التحكم لديك؟ CECH-3xxx؟ CECH-4xxx؟ نحيف جدا؟ معتدل البنيه؟ فات؟

إذا كانت وحدة التحكم الخاصة بك SuperSlim ، فسيتم معالجتها بشكل دائم. وإلا فحاول تهيئة محرك الأقراص الثابتة الداخلي.
هذا بشكل عام يصلح أنصاف الطوب. [/ QUOTE]
I have a slim CECH-2504B can you fix it

Otherwise try formatting the internal HDD.
That generally fixes the semi-bricks.

 

[KaTwenty]

Hi, im pretty new on hen and thinks like that, and im having some issue right now.
The Hen enabler doesnt work, it just stays on a infinite loop loading. The only way i can enable it is going manually on the browser and installing/enabling hen.
Yesterday was working fine
Hen 3.2.2. HFW 4.90.1

 

[esc0rtd3w]

Hi, im pretty new on hen and thinks like that, and im having some issue right now.
The Hen enabler doesnt work, it just stays on a infinite loop loading. The only way i can enable it is going manually on the browser and installing/enabling hen.
Yesterday was working fine
Hen 3.2.2. HFW 4.90.1

Please try using the Uninstall HEN option under HFW Tools Maintenance. After it reboots, install HEN again using auto installer on ps3xploit.me and see if it works fine

I must ask, even though I thought this problem was solved. Do you have other devices plugged into ps3 while enabling? You can also try using the HFW Tools option under Maintenance to Disable USB Polling and see if same, but I would try Uninstall HEN option first

 

[KaTwenty]

Please try using the Uninstall HEN option under HFW Tools Maintenance. After it reboots, install HEN again using auto installer on ps3xploit.me and see if it works fine

I must ask, even though I thought this problem was solved. Do you have other devices plugged into ps3 while enabling? You can also try using the HFW Tools option under Maintenance to Disable USB Polling and see if same, but I would try Uninstall HEN option first

thanks for the answer, it works now! And no i didnt have anything plugged in

 

[FFF256]

I know, thanks but there's no need for me to debug the new HEN mapping code if it never introduced any problem with app_home in the first place, which is why I am asking people to confirm what LuanTeles posted ie multiman can mount games to app_home with HEN 3.2.2 whereas wMM cannot.
Can more people test this and report?

The problem is in hen and webman. I guess it's the new remap method. If you use an older version of hen (only PS3HEN.BIN was replaced on 4.89 hfw), then there is no such problem.

 

[bguerville]

The problem is in hen and webman. I guess it's the new remap method. If you use an older version of hen (only PS3HEN.BIN was replaced on 4.89 hfw), then there is no such problem.

I already read the various reports so far so l am aware of this, it doesn't answer the core question though.
Why would the new remap method be in the way of mounting app_home in wMM and not in multiman?

I wonder if it could be because multiman clears remaps at some point whereas wMM doesn't, which would mean that prior to mounting app_home, some remapping code is running with mm and not with wMM, it might explain the difference in behaviour and point to a small issue in the code.
@aldostools I seem to remember you mentioning something about mm clearing remaps some time ago?

I don't maintain HEN, I don't use HEN and I don't install HEN on my development console, I ONLY give a hand here and there SO if someone could confirm that app_home in wMM doesn't mount whereas in multiman it works ok and post HEN debug logs for both mm mounting success and wmm mounting failure, that would be very helpful.

 

[aldostools]

I wonder if it could be because multiman clears remaps at some point whereas wMM doesn't, which would mean that prior to mounting app_home, some remapping code is running with mm and not with wMM, it might explain the difference in behaviour and point to a small issue in the code.
@aldostools I seem to remember you mentioning something about mm clearing remaps some time ago?

Not only multiMAN clears the remaps. Also IRISMAN and the other forks.
Both backup managers used to compete for the control of the system.
Therefore they cleared whatever the other backup manager did in memory.

webMAN MOD is permanently running, so there is no need to clean the remaps that it created and manage

Your hypothesis could be true. However I think the issue could be related to the dynamic memory allocation (heap memory) used in mappath.c of PS3HEN.

Mamba and Cobra 8.4 preallocate the map_table in the stack memory. This ensures that the mapping always will be successful. While the malloc may fail and the exception requires to be managed.
https://github.com/Evilnat/Cobra-PS3/blob/master/8.4/4.90/EVILNAT/PEX/SRC/stage2/mappath.c#L31

Additionally, map_path is more use today than its original purpose:
It was originally intended to remap GAMES folder and maybe 2 or 3 other paths.
Nowadays the payloads, webMAN and modders use many remaps, which could make the original dynamic malloc infective.

 

[bguerville]

Not only multiMAN clears the remaps. Also IRISMAN and the other forks.
Both backup managers used to compete for the control of the system.
Therefore they cleared whatever the other backup manager did in memory.

webMAN MOD is permanently running, so there is no need to clean the remaps that it created and manage

Your hypothesis could be true. However I think the issue could be related to the dynamic memory allocation (heap memory) used in mappath.c of PS3HEN.

Mamba and Cobra 8.4 preallocate the map_table in the stack memory. This ensures that the mapping always will be successful. While the malloc may fail and the exception requires to be managed.
https://github.com/Evilnat/Cobra-PS3/blob/master/8.4/4.90/EVILNAT/PEX/SRC/stage2/mappath.c#L31

Additionally, map_path is more use today than its original purpose:
It was originally intended to remap GAMES folder and maybe 2 or 3 other paths.
Nowadays the payloads, webMAN and modders use many remaps, which could make the original dynamic malloc infective.

If the issue was caused by memory allocation we would get debug logs as I remember adding DPRINTFs for this situation or at worst maybe a crash as I might have missed a check for null pointer somewhere.
I see no logs in the sample that was sent to me by pm, nor crash. However I see app_home mapping added and deleted more than once...

Regarding newer usage, I am aware, I mean I made the remapping changes with dynamic allocation because people asked for better support than just a handful of remaps for games.