Show us what are the problems, on the right you should see some green and red text. Which one is red? Also could you write in English?
How to convert dump_patched.hex to bkpps3.bin
- Thread starter Supermodz1
- Start date
sandungas
Developer
Hola juanma, please write in english
(or check your translator, is causing some problems in the QUOTEs and your texts)At this point your problem is not related with the byteswapping, you need to do a more detailed check to the dump to find where are that 2 errors
I suggest you to use the "pyps3checker" tool, it does a lot of checks, and generates a log file with info about the errors
You can paste that errors here in the forum (or better in pastebin.com because are very long) for other people to try to explain what the errors means
*You need python v2.7 installed (not the python 3 versions) to run the pyps3checker
[QUOTE = "sautzer, post: 234215, member: 53210"] Muéstranos cuáles son los problemas, a la derecha deberías ver un texto verde y rojo. ¿Cuál es rojo? ¿También podrías escribir en inglés? [/ QUOTE]
73/5000
esos son los dos errores que obtengo, además de parcheado previamente dice "no"
73/5000
esos son los dos errores que obtengo, además de parcheado previamente dice "no"
[QUOTE = "sandungas, publicación: 234216, miembro: 872"] Hola juanma, escriba en inglés (o consulte a su traductor, está causando algunos problemas en las CITAS y sus textos)
En este punto, su problema no está relacionado con el intercambio de bytes, debe hacer una verificación más detallada del volcado para encontrar dónde están esos 2 errores
Le sugiero que use la herramienta "pyps3checker", realiza muchas comprobaciones y genera un archivo de registro con información sobre los errores.
Puede pegar esos errores aquí en el foro (o mejor en pastebin.com porque son muy largos) para que otras personas intenten explicar qué significan los errores
* Necesita python v2.7 instalado (no las versiones de python 3) para ejecutar pyps3checker [/ QUOTE]
59/5000
Ok, disculpe, no sabía que tenía que escribir en inglés.
(o consulte a su traductor, está causando algunos problemas en las CITAS y sus textos)En este punto, su problema no está relacionado con el intercambio de bytes, debe hacer una verificación más detallada del volcado para encontrar dónde están esos 2 errores
Le sugiero que use la herramienta "pyps3checker", realiza muchas comprobaciones y genera un archivo de registro con información sobre los errores.
Puede pegar esos errores aquí en el foro (o mejor en pastebin.com porque son muy largos) para que otras personas intenten explicar qué significan los errores
* Necesita python v2.7 instalado (no las versiones de python 3) para ejecutar pyps3checker [/ QUOTE]
59/5000
Ok, disculpe, no sabía que tenía que escribir en inglés.
sandungas
Developer
Your translator is swapping the text blocks, and is breaking the quotes because is adding an space before the closing "/"
See in your previous posts, the ending [/ QUOTE] are wrong (the forum software is processing it as normal text, not an special code)
Try to see if you can configure the translator (or use it in a different way) to prevent that problem
Im spanish, so i understand your posts, but is a forum rule, you are free to write in any language, but always add a translation to english, otherway most people is not going to understand you... so the probabilities for finding help are going to be very low when writing in non-english languages
sandungas
Developer
Btw, the ROS0 and ROS1 are 2 areas of the flash chip intended to store info about the "actual" installed firmware, and the "previous" installed firmware
That checks are based in the MD5 hash of that areas... and the tools have that MD5s hashes hardcoded inside them
In other words... the tools needs to be updated to add every MD5 hash of the official and custom firmwares that are published from time to time (the list is huge as you can imagine)
The problem is if at some point the tool becomes obsolete (in other words, your firmware is more modern than the tool) and you have a firmware installed (in ro0 or ros1 areas) that doesnt matches with any of the MD5 harcoded in the tool
As example... if you install a 4.86 firmware, you make a flash dump, and you check it with any tool all the tools are going to tell you that there are "unknown" data in the ros areas
This doesnt strictly means that the data is wrong... is just the tool doesnt knows wtf is that data so is going to show you a warning about it
In other words... your errors probably are not really errors (and everything is fine
)
For a better check you should use the "pyps3checker" tool because is the most updated
Is not going to be able to identify 4.86 though (it needs to be udated with the 4.86 ros hashes it will happen soon), but im guessing the firmwares you had installed (actual and previous) was older than 4.86 right ?. So pyps3checker should catch them
That checks are based in the MD5 hash of that areas... and the tools have that MD5s hashes hardcoded inside them
In other words... the tools needs to be updated to add every MD5 hash of the official and custom firmwares that are published from time to time (the list is huge as you can imagine)
The problem is if at some point the tool becomes obsolete (in other words, your firmware is more modern than the tool) and you have a firmware installed (in ro0 or ros1 areas) that doesnt matches with any of the MD5 harcoded in the tool
As example... if you install a 4.86 firmware, you make a flash dump, and you check it with any tool all the tools are going to tell you that there are "unknown" data in the ros areas
This doesnt strictly means that the data is wrong... is just the tool doesnt knows wtf is that data so is going to show you a warning about it
In other words... your errors probably are not really errors (and everything is fine
)For a better check you should use the "pyps3checker" tool because is the most updated
Is not going to be able to identify 4.86 though (it needs to be udated with the 4.86 ros hashes it will happen soon), but im guessing the firmwares you had installed (actual and previous) was older than 4.86 right ?. So pyps3checker should catch them
sandungas
Developer
Im not sure which firmwares you installed before or if you applyed some patch to the dump, but in the worst scenario (incase you have ros0 and ros1 completly corrupted and unrecoverable) is not a problem, because the patches intended to be applyed to the ros areas overwrites them completly
That patches are taken from a "donor" PS3.. so is generic data (not critical or unique)
sandungas
Developer
Do you have python v2.7 installed ? otherway the .py script is not going to work
https://www.python.org/downloads/release/python-2717/
The first thing you need to do with the .py file is to run it without arguments... in command line just type the name of the .py file and press enter... and is going to display some info (this means is working)
Btw, we need to know your PS3 model, i still dont know what you was trying to do when you bricked the PS3
https://www.python.org/downloads/release/python-2717/
The first thing you need to do with the .py file is to run it without arguments... in command line just type the name of the .py file and press enter... and is going to display some info (this means is working)
Btw, we need to know your PS3 model, i still dont know what you was trying to do when you bricked the PS3
Supermodz1
Member
I think you need to try PS3 Flash Tool v4.53 that will give you green Ok. I know such sometimes happen the validating tool so just google or find in this website PS3 Flash Tool v4.53
hotdogs_stuff
Member
Thank You! flow rebuilder worked great. I bricked my console burning an iso to my internal HDD, but still had my original nor dump from 2019 (thanks to mrmario2011), i tried everything to get python and pyps3patcher working but i couldn't do it. pyps3 checker (stand alone) said it was a good dump, and i was able to byte reverse it perfectly for the E# flasher with flow rebuilder. Thank You!
Similar threads
-
PS3 Bricked ps3 after flashing ofw dex on converted cex to dex ps3 slim cech-2104a.
- Started by cezar_iscru.jpg
- Replies: 2
-
PS3 Returning Long-Time Member & Evilnat Tester: Software/Flasher Support (No Soldering)- Started by SHAD0WBULLET707
- Replies: 0
-
PS3 [Tutorial] Update Frankenstein PS3 Firmware That is Too Low to Initialize RSX (< 3.41) (NAND Models)
- Started by byt3swap
- Replies: 0
-
PS3 [Tutorial] Update Frankenstein PS3 Firmware That is Too Low to Initialize RSX (< 3.41) (NAND Models)
- Started by byt3swap
- Replies: 0