Instead of shutdown, my N10 keeps rebooting

Dear All,

I just bought an N10. Everything is normal, except when it shut down, it keeps rebooting instead. I throw every available command, from GUI (Shutdown) and CLI (poweroff and shutdown -h). After +/- 5 seconds screen blank, it will reboot. It also automatically turned on when connected to power cable.

Both Debian and Ubuntu behave the same.
To turn off the board, I have to disconnect power chord within 5 seconds interval or push power button for about 5 seconds.

N10 version is B type powered by QC 3.0 12v x 2A charger

Any advise appreciated, and sorry for English

I have the same problem.

Does halt work the way you want it to?

Hi heitbaum and ynjiun.

Thanks for response

sudo shutdown -h and sudo poweroff don’t work.

It’s also turned on automatically when power chord is plugged

Tried fedora image and the result was same

@zoegyBrix It looks like a software issue and we will fix it as soon as possible.

Ideally post the solution here as a patch, so we do not need to completely reinstall. Thanks!


We have solved this issue of cannot shut down. Please update kernel to version 4.4.167-18-rockchip.

Thanx Stephen, it works

Hi Stephen:

I need 4.4.167-18 kernel source to modify sensor driver, where I can get this ? Thanks.

This is the ROCK Pi N10 kernel source code.

I found new kernel had a new problem. When I run " sudo reboot" command, System will not reboot properly , it will stop response in "reboot: Restarting system with command ‘bootloader’ " , uart log like below, need your help to solve this,thanks.
[ 1.765717] ALSA device list:
[ 1.765747] #0: rockchip,es8316-codec
[ 1.765755] #1: HDMI-CODEC
[ 1.766270] Freeing unused kernel memory: 768K
[ 1.769735] init: init first stage started!
[ 1.769990] init: Using Android DT directory /proc/device-tree/firmware/android/
[ 1.770102] init: First stage mount skipped (missing/incompatible fstab in device tree)
[ 1.770154] init: Skipped setting INIT_AVB_VERSION (not in recovery mode)
[ 1.770177] init: Loading SELinux policy
[ 1.770286] selinux: SELinux: Could not open /sepolicy: No such file or directory
[ 1.770286]
[ 1.770334] init: Failed to load monolithic SELinux policy: No such file or directory
[ 1.770353] init: panic: rebooting to bootloader
[ 1.770375] init: Reboot start, reason: reboot, rebootTarget: bootloader
[ 1.770419] init: android::WriteStringToFile open failed: No such file or directory
[ 1.770498] init: Shutdown timeout: 6000 ms
[ 1.770539] init: terminating init services
[ 1.770585] init: waitid failed: No child processes
[ 1.770614] init: Terminating running services took 0ms with remaining services:0
[ 1.770635] init: waitid failed: No child processes
[ 1.770652] init: vold not running, skipping vold shutdown
[ 1.787536] usb 4-1: new full-speed USB device number 2 using ohci-platform
[ 1.871562] init: powerctl_shutdown_time_ms:101:0
[ 1.871694] init: Reboot ending, jumping to kernel
[ 1.872363] rk808 0-0020: reboot: force RK817_RST_FUNC_REG ok!
[ 1.872429] cpu4 limit freq=816000 min=816000 max=816000
[ 1.872655] cpu0 limit freq=816000 min=816000 max=816000
[ 1.975369] usb 4-1: New USB device found, idVendor=062a, idProduct=4101
[ 1.975983] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.976633] usb 4-1: Product: 2.4G Keyboard Mouse
[ 1.977060] usb 4-1: Manufacturer: MOSART Semi.
[ 1.984812] input: MOSART Semi. 2.4G Keyboard Mouse as /devices/platform/fe3e0000.usb/usb4/4-1/4-1:1.0/0003:062A:4101.0001/input/input3
[ 2.038682] hid-generic 0003:062A:4101.0001: input,hidraw0: USB HID v1.10 Keyboard [MOSART Semi. 2.4G Keyboard Mouse] on usb-fe3e0000.usb-1/input0
[ 2.046297] input: MOSART Semi. 2.4G Keyboard Mouse as /devices/platform/fe3e0000.usb/usb4/4-1/4-1:1.1/0003:062A:4101.0002/input/input4
[ 2.101771] hid-generic 0003:062A:4101.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [MOSART Semi. 2.4G Keyboard Mouse] on usb-fe3e0000.usb-1/input1
[ 2.381902] rk-vcodec ff660000.rkvdec: shutdown
[ 2.382340] rk-vcodec ff650000.vpu_service: shutdown
[ 2.387593] reboot: Restarting system with command ‘bootloader’


This is my test.

Use this system image. and upgrade kernel to the latest version (4.4.167-19).

Executing ‘sudo reboot’ and the system reboot.

root@rockpin10bc:~# reboot
[  183.725470] dw_wdt: unexpected close, system will reboot soon
[  184.024529] reboot: Restarting system
DDR Version 1.20 20190314
soft reset

Can you lead me to reproduce the issue? What system image do you use?

I use system image file same like you.
I update my kernel version from 4.4.167-18 to 4.4.167-20 in today.
The saturation is the same. when I executing ‘sudo reboot’ command, system will reboot and pause in same place like before
[ 2.378718] rk-vcodec ff660000.rkvdec: shutdown
[ 2.379156] rk-vcodec ff650000.vpu_service: shutdown
[ 2.385116] reboot: Restarting system with command ‘bootloader’

I put my complete log in below, hope it can help you to figure out why it happen.
Thank you so much.

Your ROCK Pi N10 ran with Android image before, right?

I think you need to erase eMMC firstly before flashing Ubuntu image.

Try the following steps

1.Erase eMMC firstly.

dd if=/dev/zero of=/dev/mmcblk2 bs=4M count=100 status=progress

2.Flash ROCK Pi N10 Ubuntu.

3.Upgrade kernel to version 4.4.167-20.

I only use external SD card to flash debian 10 image and run system, and never touch eMMC storage so far.
I know the OS in eMMC storage is android, but I only use SD card now,so you think this problem will be solved if I erase eMMC data?

Yes I think. Can you try that?

How to erase eMMC data and flash image to eMMC safely? Do you have any tutorial to guide me to do this? Thank you.

Check this guide.

  1. Prepare your image and place it into your SD card.

Then sudo dd if=./yourimage.img of=/dev/mmcblkx (x=1 if you use debian and 2 if you use ubuntu).

If you would like to have swap partition, you can manage emmc with gparted shortly after dd session.

  1. Turn off your N10. Unplug your SD Card and boot it

Thanks for your help, after erase eMMC data 、 flash debian 10 image into eMMC and update kernel to 4.4.167-20, I can execute ‘sudo reboot’ command successfully,no matter it’s in SD card or in eMMC.
Thank you so much.

1 Like