Welcome to hacktribe Discussions! #22
Replies: 15 comments 12 replies
-
Thank you so much for this! It's amazing. I'm curious of the inner workings of the synth engine? Also have you found anything about the master compressor or master channel? I always hear compression? If this is coverd somewhere please direct me to further reading! Are you on Instagram? I'd love to pick your brain. |
Beta Was this translation helpful? Give feedback.
-
Hi good work, I used the get-filehash command to display the actual checksums, and they are very different , but then again they would be, wouldn't they, given the code has been modified? |
Beta Was this translation helpful? Give feedback.
-
Ah , I get it now . Thanks for that.
…Sent from my iPad
On 8 Jan 2022, at 11:56, bangcorrupt ***@***.***> wrote:
Before patching the firmware, sha256 hash of SYSTEM.VSB should match the hash in hash/SYSTEM.VSB.sha. This proves you have the correct version of the factory firmware.
After patching the firmware, sha256 hash of hacked-SYSTEM.VSB should match the hash in hash/hacked-SYSTEM.VSB. This proves you have the same modified firmware I have tested.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
That’s weird it doesn’t , I am using the get-filehash command that displays the actual checksum, and they don’t match.
…Sent from my iPad
On 8 Jan 2022, at 11:56, bangcorrupt ***@***.***> wrote:
Before patching the firmware, sha256 hash of SYSTEM.VSB should match the hash in hash/SYSTEM.VSB.sha. This proves you have the correct version of the factory firmware.
After patching the firmware, sha256 hash of hacked-SYSTEM.VSB should match the hash in hash/hacked-SYSTEM.VSB. This proves you have the same modified firmware I have tested.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
They are different file sizes too
…Sent from my iPad
On 8 Jan 2022, at 11:56, bangcorrupt ***@***.***> wrote:
Before patching the firmware, sha256 hash of SYSTEM.VSB should match the hash in hash/SYSTEM.VSB.sha. This proves you have the correct version of the factory firmware.
After patching the firmware, sha256 hash of hacked-SYSTEM.VSB should match the hash in hash/hacked-SYSTEM.VSB. This proves you have the same modified firmware I have tested.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
Can you paste the terminal output? |
Beta Was this translation helpful? Give feedback.
-
Attached picture
The two errors were caused by missing the .sha extension
Sent from my iPad
… On 8 Jan 2022, at 12:45, bangcorrupt ***@***.***> wrote:
Can you paste the terminal output?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
How do I see the hash of the hashed file?
Also I have compared the hash of the newly downloaded firmware and the same file which was download a couple of years ago , and they are different.
…Sent from my iPad
On 8 Jan 2022, at 13:14, bangcorrupt ***@***.***> wrote:
Ok, I see what happened. Your first command get-filehash hacked-SYSTEM.VSB is correct and shows the firmware has been modified correctly. The hash displayed matches the hash found in hash/hacked-SYSTEM.VSB.sha.
In the next command get-filehash hash\hacked-SYSTEM.VSB.sha you are computing a hash of the hash file. This is not necessary.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
Ah got it , notepad. Thanks for your help.
…Sent from my iPad
On 8 Jan 2022, at 13:14, bangcorrupt ***@***.***> wrote:
Ok, I see what happened. Your first command get-filehash hacked-SYSTEM.VSB is correct and shows the firmware has been modified correctly. The hash displayed matches the hash found in hash/hacked-SYSTEM.VSB.sha.
In the next command get-filehash hash\hacked-SYSTEM.VSB.sha you are computing a hash of the hash file. This is not necessary.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
Once again thanks for the work you've done and your help. |
Beta Was this translation helpful? Give feedback.
-
I’m sure I’ve got the original samples somewhere
…Sent from my iPad
On 8 Jan 2022, at 15:32, bangcorrupt ***@***.***> wrote:
No, the original samples are not loaded from the flash. If you have a factory sampler you can export the factory samples and load them into the user slots.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
Yes I’ve got them as a .all. From hippy at 19. To shaker at 335
…Sent from my iPad
On 8 Jan 2022, at 15:32, bangcorrupt ***@***.***> wrote:
No, the original samples are not loaded from the flash. If you have a factory sampler you can export the factory samples and load them into the user slots.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
Is posible to help with more exact information about the debrick procedure? |
Beta Was this translation helpful? Give feedback.
-
Just noticed the hacktribe is sampling at 48k, is that the normal sample rate for the unhacked sampler, or could that be the reason for the higher pitched sample bug? |
Beta Was this translation helpful? Give feedback.
-
👋 Welcome!
This is a place to ask questions, get help and discuss anything about hacktribe.
Please see the FAQ, read the Wiki and search discussions before posting a new thread, thank you.
Beta Was this translation helpful? Give feedback.
All reactions