BwE

Hey I have a shit load of old ps3 jailbreak usbs, they all run either amtel chips (similar if not the exact same as a teensy) or have an asic3 chip. Now, most (but not all) have a single button and even an sd card reader... How the fuck can I reprogram these things to do something interesting? The ones where I am confident of their model I can easily re-flash them with the tools amtel provide, but then ultimately I have no idea what to do -- maybe arduino stuff? I feel like burning these little USBS .... give me a reason not to!

Cool stuff! I am not sure about the name though! haha Does it have a cheat for divinity original sin?

?

Simply the BEST!

Hey I am on version 1.3.8 now! Enjoyyyyy! https://betterwayelectronics.com.au/downloads/BwE_PS4_NOR_Validator.rar I discovered weird results where an almost identical section in CID will be placed in UNK but only in slim consoles -- why slim? Ahh this is getting frustrating to validate! The issue is, I have written everything already - validated byte by byte. Then suddenly I get a new dump from a customer/user of my program and they have an error. Turns out the error is an entirely new block of data that only HIS flippin console has. I then get another dump a week later and that dump also has that block of data. Will people stop updating their consoles so the dumps can remain the same?! ANYWAYS I have a lot of dumps, but almost all were unlabeled by their donators and the ones I have, I kinda forgot to label them properly also. So most of my dumps are without version information. I have been told of ways to determine the fw version but I have found it unreliable. I think I have a solid way of doing it, but the issue is I cant CONFIRM it. So once again, if there are people out there with a collection of nicely LABELED dumps, please send them my way!!!

Lol wuss! ?

@OldBrain I do not have that motherboard on me at the moment, sorry! Only a SAB-001, which is framed. Haha!

Just doooo itttt

lmao this looks TERRIBLE! but its better than what I can make...

Hey! Come on guys, where's the harsh critique of my source code?!

bwe at betterwayelectronics.com.au

@Sylvain bonjour, envoyez-moi une copie de chaque NOR avec lequel vous rencontrez des problèmes. N'oubliez pas que certains problèmes sont en effet réparables! Veuillez étiqueter le NOR pour que je sache à quoi je traite. Est-ce que ça démarre? Cela produit-il une erreur? Qu'est-ce qu'un firmware, etc. N'oubliez pas de m'envoyer un email, je n'étais apparemment pas abonné à ce fil! Enfin, assurez-vous de disposer de la dernière version de mon programme. Qui est 1.3.5

YES. I AM THE EXPERT! Anyways, those warnings are totally normal and expected even. For some mystical reason some PS4's simply have gaps in that section. I don't know why so I classify it as a warning rather than OK. 99.9% of PS4's that have that warning are OK. But HEY! It fits the criteria of - something is missing - so a warning is a good response! TLDR; your PS4 is fine, you can upload a copy of the NOR to anonfile.com or mega etc and send me an email - or PM

What up gangsters, now its v1.3.5 But you should know this given my AUTOMATIC VERSION CHECKER! Version: 1.3.5 (30/1/19) Added CoreOS Reference Points (Additional CoreOS Per-Console Validation). File MD5: EFFC0962BDC304ABF059380B362CBD30 So it turns out there are actual static/dynamic fixed areas within the CoreOS - after which it becomes truly random. I am sure there is more I can find in the NOR. I think the next update will have better validation within the repetition spectrum.

Burek, bro. The best thing ever to eat with yogurt.