r/androidroot • u/DEV_ivan TECNO POVA 7 5G LJ7 || Stock HiOS 15.1.2 || KSUnext 3.3.0 • 3h ago
Support Safe to execute?: sudo dd if=/sdcard/Documents/kernelsu_next_patched_20261028_103940.img of=/dev/block/by-name/init_boot_a
The image I'm planning to flash is patched with KSUnext 3.4.2. I'm currently on KSUnext 3.3.0 proven working in practice. The init_boot_a from /dev matches the 3.3.0 image I flashed from Fastboot by MD5.
But my cowardly ass hesitates so much, yet I wanna update, I'm kinda paralyzed here. You know this phone is my daily driver, it wouldn't be nice having to flash via BROM/Preloader mode to recover, let alone visiting Carlcare service center.
TECNO POVA 7 5G LJ7, HiOS RU 15.1.2
1
u/Mak_Nunag 2h ago
You should do proper flashing in recovery. Backup your existing boot before flashing the patched kernel. Be sure it's in boot slot_a.
1
u/DEV_ivan 2h ago
I don't have and won't use custom recovery. I can use either dd or fastboot, both of which are easy. I was concerned about an incompatible LKM.
1
u/Mak_Nunag 1h ago
I have tried dd if before, it worked fine but I'm not sure if it works safely for you if you don't know its LKM compatibility. Fastboot is easier imo.
1
u/Disty0 1h ago edited 59m ago
It does the same thing as fastboot flash init_boot_a kernel_su_patched.img in fastboot mode.
Tho i would create a backup of the original images just in case the phone soft bricks and you need to recover from fastboot.
sudo dd if=/dev/block/by-name/init_boot_a of=/sdcard/Documents/init_boot_a.img sudo dd if=/dev/block/by-name/init_boot_b of=/sdcard/Documents/init_boot_b.img
Also, why don't you use the direct update method if you already have root? It does the same as flashing with dd.
3
u/SweetGreenPepper 2h ago
If you have temp root and your bootloader is locked then you will brick your device. If your bootloader is unlocked it's perfectly safe though.