ShellyMini1PMG3 revert failed

[tom666-max]

I did a revert with the Shelly HomeKit 2.13 web interface. The revert stopped at 97%. Since then the Shelly has been dead. A factory reset with the s button 10s after restart is no longer possible, nor is 5x on off after the restart. The LED no longer lights up either. Does anyone have an idea?

[markirb]

Hi,

If a revert does not go through then the device boots up in original FW. Are you sure that it does not come up with an AP?

[tom666-max]

Yes, I am

Show:

Mein.Film.mp4

[markirb]

Strange thing.
Would be interesting to see what failed there.
I have the devices here and can go back and forth without problems.

Surely you can flash it via USB Serial, but you need soldering skills: https://devices.esphome.io/devices/Shelly-1-Mini-Gen3

[tom666-max]

Thank you for the feedback. As far as I can tell, I need to solder on a serial interface and then somehow run the attached config file. Is that correct and how do I do it exactly? Is there an easier way?

[tom666-max]

would it have been safer if I had done a reset first so that it was already in AP mode and then reverted for future actions?

[markirb]

Yes solder an interface. Then you can run the mos flash tool.

If you do that it would be most interesting for me what the boot console has to say before you flash.

Factory reset before reverting would be the only tip I can give yes.

[tom666-max]

Thank you very much for the information
Unfortunately I can't find the interface anymore. I used it for firescript a long time ago. And it's not worth ordering one separately as I would probably only use it once, so I might as well buy a new shelly. In future I will always do a factory reset before reverting. If you are in Switzerland, I could send you the shelly so you can see what the problem is.

[markirb]

I'm in Germany, so if you want to then yes I would look at what the problem is.

[tom666-max]

OK, next time I'm in Germany I can send it to you. What's your address?

[markirb]

Can you please send an email to the address in my GitHub profile? Then I will write you my address.

[petealves]

The exact same thing hapenned to me with a Shelly 1 Mini Gen3. I flashed mongoose firmware, all ok, then when i tried to revert, it started and supposedly everything was ok, but when i tried to connect it to Shelly App it was not working.
The relay is not even actuating whenever the shelly is connected to the power, as it should.

[markirb]

@petealves do you mean it has no wifi or do you just mean the relay does not work? it is not clear from your description. if only the relay is not working as it sounds then a hard power cut should be enough.

[petealves]

@markirb i am sorry for not explaining it correctly.
It has no wifi at all. Mini 1 Gen 3 also has a status LED, which also won't turn on. What i meant to say about the relay is that when you have the shelly ready to pair and you feed power to it, a little "click" of the relay can be heard. That click is not heard.
I have already tried to reset through the button (10 secs), nothing, tried with a switch and flipping it, also won't work. It won't show in bluetooth nor AP is showing

[markirb]

I see. I will look at the other hardware as soon as I have it to know the reason.

But I fear that something breaks the revert currently.

Only way to know is the serial interface.

[markirb]

Which stock firmware version did you use to flash originally? This might be of interest

[petealves]

I tried the revert via the WebUI of the Mongoose. I didn't pay attention to be honest. I have 20+ Shellys with Mongoose all working correctly and they always reverted OK when i needed via the Web UI, so, i just didn't pay attention to the version :/

[markirb]

So, thanks @tom666-max I got the Shelly in the mail today and looked at the serial output.

The revert to stock was successful however the Stock-Fw boots and looks for the partition table where there is none. It follows a boot/crash loop that is non recoverable.

I have to look much deeper but the preliminary conclusion is:
As the bootloader does not seem to revert even after several unsuccessful boots (it should to my understanding), this will not be recoverable without soldering an interface and flashing via this interface.

Shelly seems to keep moving the partition table around in recent versions. As precaution their partition table contains redundant data, which HomeKit firmware currently does not have. So I have to look deeper but it should definitely be possible in future to avoid this situation.

[tom666-max]

Hello Markus, what exactly happens when you revert? Is the FW that was there before loaded or is a new version loaded? Is the partition table repartitioned? And is the bootloader also replaced?
Regards, Thomas

[markirb]

Bootloader is not flashed.
Partition table normally also not according to my knowledge, at least in previous versions. however it seems to do it in recent ones.

Did you happen to have 1.5beta installed before?

[tom666-max]

no, it was 1.3.x or 1.4.x.

[damianfryc]

Same here. Shelly 1 Gen 3 revert to stock fw from gui and device is dead. Any solution?

[markirb]

As said above:

As the bootloader does not seem to revert even after several unsuccessful boots (it should to my understanding), this will not be recoverable without soldering an interface and flashing via this interface.

Investigation of why this happens (it does not happen on mine) and how we avoid this will follow...

[damianfryc]

As said above:

As the bootloader does not seem to revert even after several unsuccessful boots (it should to my understanding), this will not be recoverable without soldering an interface and flashing via this interface.

Investigation of why this happens (it does not happen on mine) and how we avoid this will follow...

Thank you. I see post above with pinout on Shelly but do I need any additional device or just I have to soldier this to DB-9(RS232) connector?

[markirb]

Check here for what you need.

https://tasmota.github.io/docs/Getting-Started/

I was playing around with this today:
Upgrade and Downgrade Pathes work smoothly with 1.4.4 and even 1.5b.
Maybe there was some version before that made an error here...

I do understand the problem but I do not know why this happened.
Newest Shelly-OS can and do upgrade bootloader as well as partition tables. mongoose does not have/do that.