Root attempt for itel A27
Root attempt for itel A27
fastboot flash vbmeta vbmeta_customb.img
Sending 'vbmeta_a' (1024 KB) OKAY [ 0.033s]
Writing 'vbmeta_a' OKAY [ 0.232s]
Finished. Total time: 0.272sfastboot flash boot itel\ A27/magisk_patched-25200_wAtyM.img
Sending 'boot_a' (65536 KB) OKAY [ 1.849s]
Writing 'boot_a' OKAY [ 0.959s]
Finished. Total time: 2.848s
(13-10-2022, 11:43 AM)flagpol Hello, I have an itel A27 that I've been trying to root.
Earlier I successfully unlocked the bootloader. Then I generated my own signing key for the custom vbmeta, got the boot.img from the stock ROM and patched it with Magisk.
I had earlier problems trying to flash the patched boot image (custom-signed with own signing key) in the bootloader, but then I discovered that flashing it in fastbootd worked.
Code:fastboot flash vbmeta vbmeta_customb.img
Sending 'vbmeta_a' (1024 KB) OKAY [ 0.033s]
Writing 'vbmeta_a' OKAY [ 0.232s]
Finished. Total time: 0.272s
Code:fastboot flash boot itel\ A27/magisk_patched-25200_wAtyM.img
Sending 'boot_a' (65536 KB) OKAY [ 1.849s]
Writing 'boot_a' OKAY [ 0.959s]
Finished. Total time: 2.848s
After these processes however, the phone got stuck in a bootloop and I had to use SoftwareDownload to reflash the stock rom
I've been looking at the forum posts, apparently the existence of a boot_a would mean an existence of a boot_b too? Should I also flash vbmeta_b and boot_b? How should I continue along with this process?
The device uses a Spreadtrum/Unisoc SC9832E for reference.
Hope an Android 11 version for the TWRP porter is available too
(14-10-2022, 02:58 PM)hovatek(13-10-2022, 11:43 AM)flagpol Hello, I have an itel A27 that I've been trying to root.
Earlier I successfully unlocked the bootloader. Then I generated my own signing key for the custom vbmeta, got the boot.img from the stock ROM and patched it with Magisk.
I had earlier problems trying to flash the patched boot image (custom-signed with own signing key) in the bootloader, but then I discovered that flashing it in fastbootd worked.
Code:fastboot flash vbmeta vbmeta_customb.img
Sending 'vbmeta_a' (1024 KB) OKAY [ 0.033s]
Writing 'vbmeta_a' OKAY [ 0.232s]
Finished. Total time: 0.272s
Code:fastboot flash boot itel\ A27/magisk_patched-25200_wAtyM.img
Sending 'boot_a' (65536 KB) OKAY [ 1.849s]
Writing 'boot_a' OKAY [ 0.959s]
Finished. Total time: 2.848s
After these processes however, the phone got stuck in a bootloop and I had to use SoftwareDownload to reflash the stock rom
I've been looking at the forum posts, apparently the existence of a boot_a would mean an existence of a boot_b too? Should I also flash vbmeta_b and boot_b? How should I continue along with this process?
The device uses a Spreadtrum/Unisoc SC9832E for reference.
Hope an Android 11 version for the TWRP porter is available too
What version of magisk manager did you use to patch?
(14-10-2022, 03:08 PM)flagpol(14-10-2022, 02:58 PM)hovatek(13-10-2022, 11:43 AM)flagpol Hello, I have an itel A27 that I've been trying to root.
Earlier I successfully unlocked the bootloader. Then I generated my own signing key for the custom vbmeta, got the boot.img from the stock ROM and patched it with Magisk.
I had earlier problems trying to flash the patched boot image (custom-signed with own signing key) in the bootloader, but then I discovered that flashing it in fastbootd worked.
Code:fastboot flash vbmeta vbmeta_customb.img
Sending 'vbmeta_a' (1024 KB) OKAY [ 0.033s]
Writing 'vbmeta_a' OKAY [ 0.232s]
Finished. Total time: 0.272s
Code:fastboot flash boot itel\ A27/magisk_patched-25200_wAtyM.img
Sending 'boot_a' (65536 KB) OKAY [ 1.849s]
Writing 'boot_a' OKAY [ 0.959s]
Finished. Total time: 2.848s
After these processes however, the phone got stuck in a bootloop and I had to use SoftwareDownload to reflash the stock rom
I've been looking at the forum posts, apparently the existence of a boot_a would mean an existence of a boot_b too? Should I also flash vbmeta_b and boot_b? How should I continue along with this process?
The device uses a Spreadtrum/Unisoc SC9832E for reference.
Hope an Android 11 version for the TWRP porter is available too
What version of magisk manager did you use to patch?
I used the latest release, Magisk 25.2 to generate the patch
