Alert, Alert. Stuck in reboot loop after update. I suspect, that it's same problem, as reported earlier by other user - updating of system-services package (I haven't tried to update it manually - as fix for lacking dependency was coming, anyway).

It seems, that some people doesn't have problems, but some are stuck in dead loop. I have access to shell console (backupmenu's one), and I would like to help investigating cause. Any ideas, where to start?

I've also tried looking into framebuffer's output, but it looks normal to the point, when framebuffer disappear (and five dots should appear). Hoever, no five dots, and after a while, framebuffer appear again, with shitdown-related messages (nothing interesting about what might went wrong).

It's a pity, that we don't have any possibility to redirect framebuffer output to a log file - it would be both more convenient (file instead of screen-hunting) and useful (would include things obscured from screen).

/Estel

// Edit

As I've tried it on 2 devices - just to be sure, that report is valid (on my main device, I always use fapman for updates, so I always compare results by installing HAM-way, on 2nd device) - I would like to keep one in this state for debugging help, but I would also like to bring at least one (presumably, my main one) to working state.

Any hints? I'm aware of theory, but I never had need for doing it in practice. I'm right, that taking older version of system-services (that worked), unpacking it, and - from recovery shell - manually replacing files, should bring device to runable state? Any caveats?