Need help: Strike Pro SE module black screen after update (Internal SD image re

[Dmitryd]

Hi everyone!
I'm in trouble with my Alesis Strike Pro SE module. After a firmware update, the screen stays black. I discovered that the internal MicroSD card is empty and was previously replaced with a 16 GB one, which is obviously wrong.
I've already updated the firmware via USB (it shows success), but the module won't boot without the system files on the SD card.
Could anyone please share a link to a full working v1.5 internal SD card image (.img file)? I have a new 32GB Class 10 card ready to flash.
Thanks in advance for your help!

[Chaser]

Welcome to the Forum !

Believe it or Not..the 1st thing to check for when having a Black Screen... is make sure the Knob for the LCD Contrast isn't turned all the way down....It is a common mistake..

When installing the Updates or Reinstalling Firmware using the Updater...pay attention to the  prompts to re-Boot.
Make sure the STRIKE Module is selected in the Updater...

https://www.alesisdrummer.com/index.php?topic=8674.msg54869#msg54869

Typically on SD Card Failure you could still copy the content over to computer , then copy on a New Formatted SD Card.

as far as everything else....

The STRIKE PRO SE was released with the Final Version (V1.5) of the Firmware and All Content.
There has never been a Firmware Update or additional Content since the STRIKE PRO SE was released (2019)

There are No System Files on either of the SD Cards.
The SD Cards are Content..Kits(.skt)..Instruments(.sin) Loops and Samples (wav).
The OS and Trigger Firmware are/were separate Updates for early STRIKE Modules (Pre-SE) and the Module will Power On/Boot without any SD Cards , there will just be No Kits/Instruments/Samples to Load.
The Internal SD Card is "Write Protected"..All Edits are saved to the external SD Card as "User".
There is No Need to use large SD Cards for the Internal SD Card.
The larger the external SD Card and the more samples... the longer it takes to scan on Module startup or for the STRIKE Editor after Edits/Saving.The largest SD Card I tested is/was 128GB and loaded with over 50K samples.. the Editor would take forever to scan after you created a kit etc...the smaller the SD Card the better .If you use the STRIKE for gigging etc just change cards if you use different kits/sets for different gigs etc

There isn't a V1.5 Image File with All Kits/Instruments/Wav samples...Never has been....the updates are/were Bin files and .syx installed with the updater.
The Original STRIKE Module was Updated over the years and early updates were (2) part...using the updater for the Main OS and Trigger OS then the STRIKE Editor for Installing Content..Later the Updater handled ALL and the Updater would prompt for a Re-Boot inbetween Processes.

Starting with v1.3 additional Content was installed to the original Factory/Default Sample Base.
If you skipped an update..for example jumped out of order from v1.2 to v1.5 (which happened quite often with "Closet Modules") you will be missing a lot of Content and Kits would load without Instruments/Samples.
Alesis has not and never will release the Factory Samples (wav) to the General Public.
You will Not find Public Forums (Including this Forum) Hosting the Wav Samples.
Distribution of the wav files owned by InMusic/Alesis etc.may be considered Piracy by InMusic as it is considered Piracy when distributing wav samples from other Sample Developers...

If you are missing ALL the Content..(STRIKE PRO SE Module came with ALL installed) Contact Alesis Support or the STRIKE Group on Facebook (Private Group).
Since it is Private one of the Members may be Hosting the Content which is Not recommended.

The same question has been posted numerous times in this Forum and there was never  a follow up from the original poster about availability of the wav files from either..

[Dmitryd]

Hello, Thank you very much for your detailed answer to my question. Then I'll have to look into the cause of my module's behavior. What's interesting is that when I activate the "Record + Power On" update mode, the display turns on and displays the firmware modes, except for the last part, which is updated in normal operating mode. The firmware developer doesn't see the module.