No access to bootloader or recovery after a custom ROM install attempt

[avilqu]

Hi everyone,

So yeah, I probably shouldn't have played around with recovery, bootloaders and custom OS, but my XZ2 Compact was rendered nearly useless by the last Android update, so I tried to install the new official Lineage OS on it. But I failed. Hard.

Symptoms

• The phone now only reacts to the power button. When I press it, it displays a battery charge icon for a minute or two, then the screen turns off.
  
• None of the other physical buttons do anything, and the button combinations don't work. As a result, I can't boot to recovery, or even access to fastboot.
  
• The light indicator is on and red.
  
• I let the phone drain its battery, see what happens, and well, nothing. Eventually the screen stops turning on. When I replug the phone, even if I don't touch anything, it will end up showing me the battery icon again, and is stuck in the same loop.
  
• 'adb devices' still sees my phone, but with no permissions. 'fastboot devices' doesn't see anything.
  
• On Windows, Emma (Sony's flashing tool) doesn't see the device.

Causes

I was following this tutorial. I went up to "temporarily booting a custom recovery using fastboot". I used the latest LineageOS recovery for my phone, and the flashing worked fine according to the output of the fastboot command. But that's all. Impossible to do anything after that.

Do I now own a glorified paper weight? Or can I save this?

Thanks!

SOLVED! I managed to stop the charging loop with a key combination I discovered: volume up + volume down + power for about 10s. Then was able to load the bootloader and re-flash a recovery, custom ROM etc. Thank you all for your help.

 

[old.splatterhand]

Have you tried to hold vol+, vol- and power button all together for (at minimum) a minute?
I would then try to restore stock firmware with newflasher (you'll find it using Google search or here on xda).

 

[avilqu]

Great, thanks a lot I didn't know this key combination and it allowed me to get out of that charging loop and start the bootloader. Problem solved!

 

[old.splatterhand]

Nice, glad to hear!