I locked bootloader after installing /e/ Os. on my GS290. Now the phone is like dead anche i can’t unlock the bootloader again. I tried to restore android stock firmware with flashtool but i need a signed image (md1img-berified.img)
So what you did was completely reasonable, Edit, but this is our recommended install method.
I would be very wary of reflashing as there is no “factory” image. There is an image, linked in our docs, but l suggest you delay that approach.
The error (seems) my guess, to me to be in your flashtool and its relationship with Lubuntu. I am not at a PC to double check this but in Debian I required a very recent kernel, which I did not try very hard to acquire.
Perhaps you could link your source for flashtool? On reflection, let’s avoid that.
Edit. Do you have access to Bootloader?
Reading the link above, are you able to complete all the prerequisites? Please don’t rush!
Then perhaps the fastboot unlock method will work.
What I think has happened is beyond my experience and I cannot find it documented here for a GS290. I think it quite possible that the lock has happened “on the wrong slot”. You could consider searching for fastboot oem unlock + Slots or Partitions. I would be very careful to try only to collect evidence of what is wrong.
I would seriously avoid spamming the phone with different unlock techniques.
When you search this forum for GS290 you may recognise some recurring issues.
Edit, back to your OP, there is a link on the Install page (which I linked above) to this:
I have the same problem. I locked bootloader after successful /e/ OS installation using Easy Installer, because it is required by banking apps. No fastboot, no bootloader, only preloader and SP Flash Tool. But SP Flash Tool returns an error on downloading md1img.img from this ROM - STATUS_SEC_INSUFFICIENT_BUFFER. You can see screenshot of the same situation from other Gigaset thread - GS290 - is there a way to get back to factory Android?
I’ve tried a bunch of versions of SP Flash Tool - without success.
Looks like only official verified firmware will save our devices. Is there any chance that the /e/ OS developers will contact with Gigaset developers for verified images and help us?
Of course. I wrote about this in the two comments above.
There is no problem with the preloader img here. Problem with some other images, as I remember, there are about five of them. Of course I tried skipping them, but this doesn’t help.
Sorry, I’m not a native speaker and may speak a little unclear. On the screenshot exactly what you wrote in the quote, and almost what is written in the flash instruction (except OS, but I don’t think it affects the error). I tried different combinations of the checkboxes from the image list, including downloading without preloader image or all except those causing the error and many others. But it didn’t help. Looks like affected images those causing the error are critical for the fastboot loading.
It all looks like the error is caused by the phone hardware, that checks the lock/unlock bootloader flag, that can be changed only in non bricked device (as far as I know). So, looks like we need help from the developers.