Oneplus Nord CE 5 root

2025年10月6日

https://xdaforums.com/t/stockrom-oneplus-nord-5-stock-firmware-boot-img-for-rooting-request-for-custom-recovery.4757591/

# boot into normal
fastboot reboot

# boot to bootloader
adb reboot bootloader

$ fastboot flash recovery ..\twrp-3.7.1_12-0-avicii.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 47124480).
Sending ‘recovery’ (46020 KB) OKAY [ 1.135s]
Writing ‘recovery’ FAILED (remote: ‘partition does not exist’)
fastboot: error: Command failed

fastboot boot ..\twrp-3.7.1_12-0-avicii.img
Sending ‘boot.img’ (46020 KB) OKAY [ 1.146s]
Booting FAILED (remote: ‘unknown command’)

fastboot: error: Command failed

remote: ‘partition does not exist’

Install LineageOS on OnePlus 12R

fastboot flash boot ..\boot.img
Sending sparse ‘boot_a’ 1/1 (45860 KB) OKAY [ 1.144s]
Writing ‘boot_a’ FAILED (remote: ‘sparse image size span overflow.’)
fastboot: error: Command failed

$ adb shell
$ ls -al /dev/block/by-name/
total 0
...
lrwxrwxrwx 1 root root   16 2025-10-09 21:28 boot_a -> /dev/block/sdc38
lrwxrwxrwx 1 root root   16 2025-10-09 21:28 boot_b -> /dev/block/sdc71

$ blockdev --getsize64 /dev/block/sdc38
67108864
$ blockdev --getsize64 /dev/block/sdc71
67108864

This means my boot_a partition is 67108864 bytes, ie. 64MB.

If you want to flash a boot.img, whether so-called stock or LineageOS, it must be less than 64MB.

$ fastboot getvar partition-size:boot_a
partition-size:boot_a: 4000000
Finished. Total time: 0.002s
$ fastboot getvar partition-size:boot_b
partition-size:boot_b: 4000000
Finished. Total time: 0.001s

According to fastboot.cpp, the return value is uint64, rather than HEX.

https://github.com/aosp-mirror/platform_system_core/blob/a3b721a32242006b59cb12bd62c9133632af3a2d/fastboot/fastboot.cpp#L1182-L1200

root後可以裝什麼？

universal-android-debloater-next-generation不利用root。

https://github.com/sunilpaulmathew/De-Bloater knows to use root.

# CPU architecture: arm64-v8a or armeabi-v7a?
adb shell getprop ro.product.cpu.abi

From /proc/mounts you can find /dev/block/dm-0 / erofs ro,seclabel,relatime,user_xattr,acl,cache_strategy=readaround 0 0, which means the root directory is not only readonly, but also the file system type erofs is readonly by design. Therefore, one can’t remount this partition as writable.

Accordingly, Magisk use an overlay (overlayfs) approach to modify system tools.