Power On/ Off Loop

mable · October 9, 2025, 7:20pm

Hey ho!

I have tried to install /e/ on a OnePlus Nord - “avicii” following the official guide. This was my first install of a custom rom using “someones” script. I do not mean that negatively!

However the script was not able to send all needed files to the device:

Script Summary

INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)…
INFO: One OnePlus Nord in fastboot mode found (serial number: ).
INFO: Switching device to fastbootd mode…
Rebooting into fastboot OKAY [ 0.002s]
< waiting for >
Finished. Total time: 11.744s
INFO: Device is now in fastbootd mode.
Info: Your phone is in fastbootD mode.
Sending ‘abl_a’ (220 KB) OKAY [ 0.012s]
Writing ‘abl_a’ OKAY [ 0.008s]
Finished. Total time: 0.029s
Sending ‘abl_b’ (220 KB) OKAY [ 0.011s]
Writing ‘abl_b’ OKAY [ 0.008s]
Finished. Total time: 0.024s
Sending ‘aop_a’ (192 KB) OKAY [ 0.009s]
Writing ‘aop_a’ OKAY [ 0.007s]
Finished. Total time: 0.022s
Sending ‘aop_b’ (192 KB) OKAY [ 0.010s]
Writing ‘aop_b’ OKAY [ 0.008s]
Finished. Total time: 0.022s
Sending ‘bluetooth_a’ (236 KB) OKAY [ 0.012s]
Writing ‘bluetooth_a’ OKAY [ 0.008s]
Finished. Total time: 0.025s
Sending ‘bluetooth_b’ (236 KB) OKAY [ 0.010s]
Writing ‘bluetooth_b’ OKAY [ 0.008s]
Finished. Total time: 0.023s
Sending ‘devcfg_a’ (48 KB) OKAY [ 0.003s]
Writing ‘devcfg_a’ OKAY [ 0.006s]
Finished. Total time: 0.014s
Sending ‘devcfg_b’ (48 KB) OKAY [ 0.002s]
Writing ‘devcfg_b’ OKAY [ 0.006s]
Finished. Total time: 0.013s
Sending ‘dsp_a’ (65536 KB) FAILED (Write to device failed in SendBuffer() (Protocol error))
fastboot: error: Command failed

ERROR: Could not flash the dsp_a partition on device .

ERROR: Please unplug the phone, take the battery out, boot the device into
ERROR: fastboot mode, and start this script again.
ERROR: (To get to fastboot mode, press Volume-Down and plug in the USB-C)
ERROR: (cable until the fastboot menu appears.)

ERROR: Aborting now (press Enter to terminate).

At the moment it is stuck at a weird Power On/ Off loop. the device turns on and off rapidly. i am not able to break out of this loop.

Video

From my point of view, the next possible approach is to wait until the battery is fully discharged - as mentioned by the script also. I am still hoping that the device is not fully bricket.

Did someone else encountered this behavior also?

Cheers and best regards
mable

Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online services phone

Jets · October 10, 2025, 3:13am

Who is “someones” where did you get the script from? I installed eOS 14 on my nord with the script on the page provided by eOS here:

https://doc.e.foundation/devices/avicii/install

With no issues at all. Was one of the easiest install I ever did I really like this method. Did you use the link I posted?

I looked at the video. Press the power and volume down and see if you can turn it off. If you can plug in a charger and tell us the charge level.

aibd · October 10, 2025, 7:25am

This has been reported as connected to the USB cable. So one should check the whole USB chain, good capacity data cable, avoid USB hubs and connect to the USB port soldered to the PC motherboard.

The required tx could be hard work for some home PCs, perhaps avoid running anything other than the terminal. The usual /e/ script runs sequential flash_partition_or_abort – your log seems to reflect one partition failure.

A forum search of your error.

As said above the aim right now is just to return to Fastboot mode via power off.

If it helps the loop is doing: try to start system on fail, try to boot recovery, on fail start again, from your log of script failure this is “expected” … thus the error advice.

mable · October 10, 2025, 8:21pm

Thank you for your response.

You 're right. I made use of the script provided by eOS and i downloaded it from the same link/ source you mentioned.

Maybe i had to write more clearly … i can’t intercept the ongoing process at all. The device does not stuck in a boot loop. it is turning on and off very, very rapidly. because of this behavior i would rather call it a “power on/ off loop”. i am not able to turn it off also.

While forcing the device to boot up into fastboot again, the same behaviour occurs.
(Volume up& down + Power)

Jets · October 11, 2025, 2:18am

You need to turn the phone off then charge it to be sure. The try the script again. What OS are you using on the PC or laptop?

In my case I was running Windows 11 (forgive me LOL).

mable · October 12, 2025, 7:38pm

You are forgiven. It is not to late to switch over!

I keep an old Laptop around, because of its “true” USB 2.0 interfaces. The OS is the latest Debian stable.

There are no additional HUBs between the phone and the laptop and the cable can be considered as solid. I have flashed all my other devices with this combo.

At the moment the battery is mostly discharged. the phone can’t be turned on if its only on battery. Sadly the same behaviour starts to occur, if i put it on external power again.

aibd · October 12, 2025, 7:46pm

So far

Clearly. Is not in line with the error message.

New user troll alert ??

mable · October 14, 2025, 7:32pm

Blockquote
Clearly. Is not in line with the error message.

This might be true. But that’s the current status as far as I can tell.

Blockquote
New user troll alert ??

Bad day? At the moment, you are the only troll in here.

Thanks for your feedback anyway.

aibd · October 15, 2025, 9:54am

Did I misread your comment, then?

Once the battery is actually discharged, one would aim to

Recharge the battery – initially 20 mins charging would be ok (just to test, not to proceed, one would hope to recharge completely once problem cycle has stopped ofc, one must replicate battery disconnect).
achieve Fastboot mode by

With the device powered off - hold Volume Up + Volume Down + Power.