PS3 Can't install HFW (No Applicable update data was found)

[NiQ]

Hi everyone, i know i'm few years late on this thread, but i have similar problem.
My PS3 slim CECH-2500 can't install firmware also. Same message appears. Firmware version is 3.40. The difference is, i don't know if it was jailbroken or not, i bought it like that cheap ( someone tried to install firmware and gave up). I didn't try installing CFW, only OFW and HFW, because i don't know what firmware was installed before. When you power console it asks for firmware because someone already did hdd format.

I forgot to mention i tried:
- Different versions of OFW and HFW firmware
- formatting USB drive to FAT16 instead of FAT32
- trying different USB drive, and different port on console
- trying to unplug controller while searching for update file on USB drive
- swapping different HDD drives and formatting them to FAT32 ( all were healthy, only the one that came with console had 34% health so i swapped it for 500gb and later 80 and 40 for testing)

My question is, do i need to do flashing in order to install CFW on 3.40 firmware?

If you're currently on a version <= 3.55 there's no need for any hacks. Just get a CFW and install it like you would install any update.
You will eventually want to install the latest and greatest Evilnat 4.90 but some people have reported issues installing it directly on very old firmware. If that's the case then you can try gradually updating. Just make sure that any firmware version >3.55 you install is a CFW. If you accidently install OFW (or HFW) >3.55 you'll have to use jailbreak tools to get it to CFW.

Also - I find it a bit weird that you have 3.40, unless you got new old stock or something. 3.40 is the minimum version for the earliest 25xx units. If you're currently on 3.40 it means your console has never been updated since purchase.

Regarding your issue -
Don't bother with HFW. It's only needed to install HEN on firmware versions >=4.83. You don't need HEN if your console supports full CFW (which it does).

Regarding the USB disk issue - Is the USB disk recognized by the console? If it's formatted properly then it should appear in XMB under the photos / music / videos tabs. If you don't see it then you're probably not formatting it properly. Make sure it's MBR-FAT32. If the drive is using GPT then Windows will keep it GPT even if you reformat it to FAT32. You can use a tool called Rufus to format to MBR if needed.
If the USB disk is recognized then something's wrong with the update file.

• Make sure the directory hierarchy is correct. There should be a directory named PS3 in the root directory. Inside the PS3 directory there should be a subdirectory named UPDATE and inside that there should be the update file itself, named PS3UPDAT.PUP.
• Make sure both the directory names and the update file name are in all caps. File names are case-sensitive in the PS3, contrary to Windows.
• Make sure the file name is PS3UPDAT.PUP and not PS3UPDATE.PUP.
• Check that the firmware file is valid and complete. The best way would be to just compare its MD5 with the one written in the place you've downloaded it from.
• Do not install CFW tagged DEX / D-REX / D-PEX / DECR, as these are intended for debug units.
• Make sure the firmware you're trying to install is not too old - When installing CFW for the first time it cannot be older than the OFW you're currently on. After installing CFW you can use the QA flag to downgrade if you wish, however you can never downgrade to versions lower than the one your PS3 originally shipped with (3.40 in your case).
• If that does not solve the problem, try installing the firmware from recovery mode.

 

[Snake_Plissken92]

If you're currently on a version <= 3.55 there's no need for any hacks. Just get a CFW and install it like you would install any update.
You will eventually want to install the latest and greatest Evilnat 4.90 but some people have reported issues installing it directly on very old firmware. If that's the case then you can try gradually updating. Just make sure that any firmware version >3.55 you install is a CFW. If you accidently install OFW (or HFW) >3.55 you'll have to use jailbreak tools to get it to CFW.

Also - I find it a bit weird that you have 3.40, unless you got new old stock or something. 3.40 is the minimum version for the earliest 25xx units. If you're currently on 3.40 it means your console has never been updated since purchase.

Regarding your issue -
Don't bother with HFW. It's only needed to install HEN on firmware versions >=4.83. You don't need HEN if your console supports full CFW (which it does).

Regarding the USB disk issue - Is the USB disk recognized by the console? If it's formatted properly then it should appear in XMB under the photos / music / videos tabs. If you don't see it then you're probably not formatting it properly. Make sure it's MBR-FAT32. If the drive is using GPT then Windows will keep it GPT even if you reformat it to FAT32. You can use a tool called Rufus to format to MBR if needed.
If the USB disk is recognized then something's wrong with the update file.

• Make sure the directory hierarchy is correct. There should be a directory named PS3 in the root directory. Inside the PS3 directory there should be a subdirectory named UPDATE and inside that there should be the update file itself, named PS3UPDAT.PUP.
• Make sure both the directory names and the update file name are in all caps. File names are case-sensitive in the PS3, contrary to Windows.
• Make sure the file name is PS3UPDAT.PUP and not PS3UPDATE.PUP.
• Check that the firmware file is valid and complete. The best way would be to just compare its MD5 with the one written in the place you've downloaded it from.
• Do not install CFW tagged DEX / D-REX / D-PEX / DECR, as these are intended for debug units.
• Make sure the firmware you're trying to install is not too old - When installing CFW for the first time it cannot be older than the OFW you're currently on. After installing CFW you can use the QA flag to downgrade if you wish, however you can never downgrade to versions lower than the one your PS3 originally shipped with (3.40 in your case).
• If that does not solve the problem, try installing the firmware from recovery mode.

Thank you so much for the reply. I just want to install firmware on this console because the console is asking for it, and i can't boot to XMB without it. I have already jailbroken several consoles but they all had at least 4.84 OFW on them already, i never had console with 3.40. That's when i read somewhere that you could actually install CFW on 3.40 withouth flashing, but i needed more information. I suppose the person i bought this console from tried to install OFW as well, or tried some stuff on it because warranty sticker is missing. I was just affraid i would brick the console if i were to install CFW on it without flashing.

Thank you again for help, i will try your suggestions and hopefully fix this.


UPDATE:

I have downloaded all the files of "final release of REBUG REX CFW" 4.84.2 and first i tried to install REX 4.84.2 version but console did not recognized it, after that i put D-REX 4.84.2 and the console finally moved to formatting screen, and now as i'am typing this, console has finished installing firmware and setup, it booted to XMB without any problems. So i guess the console is on DEX version? Because every firmware i tried to install up until now was CEX. Anyway, this has solved problem for me, if anyone has the same problem this could fix it.

 

[NiQ]

Thank you so much for the reply. I just want to install firmware on this console because the console is asking for it, and i can't boot to XMB without it. I have already jailbroken several consoles but they all had at least 4.84 OFW on them already, i never had console with 3.40. That's when i read somewhere that you could actually install CFW on 3.40 withouth flashing, but i needed more information. I suppose the person i bought this console from tried to install OFW as well, or tried some stuff on it because warranty sticker is missing. I was just affraid i would brick the console if i were to install CFW on it without flashing.

Thank you again for help, i will try your suggestions and hopefully fix this.


UPDATE:

I have downloaded all the files of "final release of REBUG REX CFW" 4.84.2 and first i tried to install REX 4.84.2 version but console did not recognized it, after that i put D-REX 4.84.2 and the console finally moved to formatting screen, and now as i'am typing this, console has finished installing firmware and setup, it booted to XMB without any problems. So i guess the console is on DEX version? Because every firmware i tried to install up until now was CEX. Anyway, this has solved problem for me, if anyone has the same problem this could fix it.

Rebug REX and Evilnat PEX firmware can convert consoles between CEX and DEX*, so it's very likely that the previous owner had CFW on it and used that to convert it to DEX. If you see the console's IP address on the bottom-right corner in XMB, that's a dead giveaway that it's DEX. It's also likely that they used the QA flag to downgrade it to its minimum supported version, which explains why it was on 3.40 when you got it.

* Retail (CEX) and Debug (DEX) units are almost identical in hardware. The only difference is the HDMI encoder, so real DECH units have the bonus of being able to disable HDCP, but otherwise converted units have all DEX options and can be used for homebrew development. Once the unit is converted to DEX it will only accept DEX CFW unless it's converted back to retail, so that's the reason you had that problem - however never install DEX OFW on a converted unit, as you will brick it. Evilnat is currently working on a solution for that but it's not out yet.

 

[Snake_Plissken92]

Rebug REX and Evilnat PEX firmware can convert consoles between CEX and DEX*, so it's very likely that the previous owner had CFW on it and used that to convert it to DEX. If you see the console's IP address on the bottom-right corner in XMB, that's a dead giveaway that it's DEX. It's also likely that they used the QA flag to downgrade it to its minimum supported version, which explains why it was on 3.40 when you got it.

* Retail (CEX) and Debug (DEX) units are almost identical in hardware. The only difference is the HDMI encoder, so real DECH units have the bonus of being able to disable HDCP, but otherwise converted units have all DEX options and can be used for homebrew development. Once the unit is converted to DEX it will only accept DEX CFW unless it's converted back to retail, so that's the reason you had that problem - however never install DEX OFW on a converted unit, as you will brick it. Evilnat is currently working on a solution for that but it's not out yet.

Thanks for clarifying that i guess every day you learn something new haha. I do see ip address and i saw somewhere that DEX consoles have some extra options in software update menu. I will try to convert it to retail version as i don't really have any use from developer options, but it is nice to know we have all those options available.

 

[Coro]

Thanks for clarifying that i guess every day you learn something new haha. I do see ip address and i saw somewhere that DEX consoles have some extra options in software update menu. I will try to convert it to retail version as i don't really have any use from developer options, but it is nice to know we have all those options available.

when updating a dex, it does not ask for current version or above, but rather the lowest it can use or above. so 3.40 is your ps3's lowest installable firmware version.

 

[Snake_Plissken92]

when updating a dex, it does not ask for current version or above, but rather the lowest it can use or above. so 3.40 is your ps3's lowest installable firmware version.

That would explain why the second time i tried to update D-REX 4.84.2 ( because you need to install it twice when it's CFW, right?) it was displaying still 3.40 instead of 4.84, i was confused, i thought it was bug or something.

 

[NiQ]

That would explain why the second time i tried to update D-REX 4.84.2 ( because you need to install it twice when it's CFW, right?) it was displaying still 3.40 instead of 4.84, i was confused, i thought it was bug or something.

No need to install twice. The only reason I could think of where you'd want to install twice is if you're reverting to OFW and want to remove every single trace of your PS3 ever having been modded (btw that still doesn't unban you if you've already been banned).

 

[Snake_Plissken92]

No need to install twice. The only reason I could think of where you'd want to install twice is if you're reverting to OFW and want to remove every single trace of your PS3 ever having been modded (btw that still doesn't unban you if you've already been banned).

I always install CFW twice, because i read it is to populate both ROS0 and ROS1 regions of the flash information with the same hash data, although someone here said that it is not necessary because bgtoolset already does that. I do it as precaution.

 

[bguerville]

I always install CFW twice, because i read it is to populate both ROS0 and ROS1 regions of the flash information with the same hash data, although someone here said that it is not necessary because bgtoolset already does that. I do it as precaution.

AFAIK there's absolutely no need for double fw installations UNLESS you use the old and fundamentally dodgy Flash Writer method that relies on partial ROS writes.

As long as you keep using the full 7Mb ROS patches, whether you apply them with a hardware flasher or a software flasher like the PS3 Toolset, there's no risk of alternate ROS corruption.

That's why IMHO it was a mistake to revive the Flash Writer as is, using its old style 3Mb patches, and even with newly added ROS writes verification, especially when it would have been simpler to move forward, make it apply the full 7Mb patches known to be safe and therefore remove all risks and confusion, no matter what tool people use.

 

[Snake_Plissken92]

AFAIK there's absolutely no need for double fw installations UNLESS you use the old and fundamentally dodgy Flash Writer method that relies on partial ROS writes.

As long as you keep using the full 7Mb ROS patches, whether you apply them with a hardware flasher or a software flasher like the PS3 Toolset, there's no risk of alternate ROS corruption.

That's why IMHO it was a mistake to revive the Flash Writer as is, using its old style 3Mb patches, and even with newly added ROS writes verification, especially when it would have been simpler to move forward, make it apply the full 7Mb patches known to be safe and therefore remove all risks and confusion, no matter what tool people use.

Thank you for explanation. I will stick to the toolset as i always did, and won't install firmware twice from now on. I sure have a lot to learn about that stuff, but i really enjoy jailbreaking PS and tinkering with hardware and software.

 

[Coro]

i also recommend double install for downgrading firmware. maybe it will never cause a problem, but "better safe than sorry".

 

[NiQ]

AFAIK there's absolutely no need for double fw installations UNLESS you use the old and fundamentally dodgy Flash Writer method that relies on partial ROS writes.

As long as you keep using the full 7Mb ROS patches, whether you apply them with a hardware flasher or a software flasher like the PS3 Toolset, there's no risk of alternate ROS corruption.

That's why IMHO it was a mistake to revive the Flash Writer as is, using its old style 3Mb patches, and even with newly added ROS writes verification, especially when it would have been simpler to move forward, make it apply the full 7Mb patches known to be safe and therefore remove all risks and confusion, no matter what tool people use.

Well, bgtoolset was down for about half a year iirc. I'm sure you had your circumstances and I don't mean to disrespect, but many (and I have to admit that includes me) thought it's gone for good. Worse yet, some people grew impatient and started using unofficial clones that would sometimes work and sometimes brick your PS3, so reviving Flash Writer, imho, was the lesser of evils.
Now that your toolset is back I doubt people would still prefer Flash Writer, but it's a nice fallback should anything happen. I hope that you'd consider releasing bgtoolset's source code should you ever decide to stop maintaining it though. It's obviously far superior.

 

[bguerville]

Well, bgtoolset was down for about half a year iirc. I'm sure you had your circumstances and I don't mean to disrespect, but many (and I have to admit that includes me) thought it's gone for good. Worse yet, some people grew impatient and started using unofficial clones that would sometimes work and sometimes brick your PS3, so reviving Flash Writer, imho, was the lesser of evils.
Now that your toolset is back I doubt people would still prefer Flash Writer, but it's a nice fallback should anything happen. I hope that you'd consider releasing bgtoolset's source code should you ever decide to stop maintaining it though. It's obviously far superior.

Am glad you mean no disrespect... [emoji23]
I meant no disrespect either to whoever contributed to the revival of the old Flash Writer, I was merely pointing out that keeping the 3Mb patches was not a good idea. If one is able to add features such as ROS writes hash checks, one should also EASILY be able to make the necessary changes to use full 7Mb patches.

The Toolset source will remain closed as long as I keep working on it, but if ever at some point I decided to give it all up, I would probably release it.

 

[Aquinate1]

Hello everyone.
I have lost some data from my ps3 including my games, multiman, webmanmod following a bad shutdown of my ps3 which crashed. I tried to reinstall the various lost programs with tutorials, but the system had to be updated to 4.90 Hen. During the update, I got a 52% error and the ps3 was stuck on update at startup. So I formatted the hard disk to resume the update from recovery mode, but it's still the same, the update doesn't succeed. I've tried recovery mode options 3 and 5, but it keeps asking me to update. I've tried different UPDATE files to no avail. For those who would like to know, I don't have the specifications of the system installed, whether it was a CEX or DEX or something like that. It's a PS3 ultra slim CEH-.