Couldn't detect partition: boot

[JXRNO]

Hello,

I am trying to root my Nokia 2.3 with Chipset MT6761, I have unlocked the bootloader but when I try to follow the root tutorial for Windows (python mtk r boot,vbmeta boot.img,vbmeta.img)

I keep getting these errors:

DA_handler - Requesting available partitions ....
DA_handler
DA_handler - [LIB]: Error: Couldn't detect partition: boot
Available partitions:
DA_handler - boot_para
DA_handler - para
DA_handler - expdb
DA_handler - frp
DA_handler - nvcfg
DA_handler - nvdata
DA_handler - metadata
DA_handler - spare1
DA_handler - protect1
DA_handler - protect2
DA_handler - seccfg
DA_handler - spare2
DA_handler - persist
DA_handler - sec1
DA_handler - proinfo
DA_handler - efuse
DA_handler - nvram
DA_handler - logo_a
DA_handler - spare3
DA_handler - md1img_a
DA_handler - spmfw_a
DA_handler - scp_a
DA_handler - sspm_a
DA_handler - gz_a
DA_handler - lk_a
DA_handler - boot_a
DA_handler - dtbo_a
DA_handler - tee_a
DA_handler - spare4
DA_handler - vendor_a
DA_handler - system_a
DA_handler - vbmeta_a
DA_handler - picture_a
DA_handler - wt_custom_a
DA_handler - logo_b
DA_handler - md1img_b
DA_handler - spmfw_b
DA_handler - scp_b
DA_handler - sspm_b
DA_handler - gz_b
DA_handler - lk_b
DA_handler - boot_b
DA_handler - dtbo_b
DA_handler - tee_b
DA_handler - spare5
DA_handler - vendor_b
DA_handler - system_b
DA_handler - vbmeta_b
DA_handler - picture_b
DA_handler - wt_custom_b
DA_handler - oem
DA_handler - logdump
DA_handler - wt_log
DA_handler - elabel
DA_handler - spare6
DA_handler - userdata
DA_handler - otp
DA_handler - flashinfo
DA_handler

Is there any solution to fix this?

[ferouzkassim]

It should be boot_a to root the device

On Fri, 20 Sept 2024, 21:31 JXRNO, @.***> wrote:

Hello,

I am trying to root my Nokia 2.3 with Chipset MT6761, I have unlocked the bootloader but when I try to follow the root tutorial for Windows (python mtk r boot,vbmeta boot.img,vbmeta.img)

I keep getting these errors:

DA_handler - Requesting available partitions .... DA_handler DA_handler - [LIB]: �[31mError: Couldn't detect partition: boot Available partitions:�[0m DA_handler - boot_para DA_handler - para DA_handler - expdb DA_handler - frp DA_handler - nvcfg DA_handler - nvdata DA_handler - metadata DA_handler - spare1 DA_handler - protect1 DA_handler - protect2 DA_handler - seccfg DA_handler - spare2 DA_handler - persist DA_handler - sec1 DA_handler - proinfo DA_handler - efuse DA_handler - nvram DA_handler - logo_a DA_handler - spare3 DA_handler - md1img_a DA_handler - spmfw_a DA_handler - scp_a DA_handler - sspm_a DA_handler - gz_a DA_handler - lk_a DA_handler - boot_a DA_handler - dtbo_a DA_handler - tee_a DA_handler - spare4 DA_handler - vendor_a DA_handler - system_a DA_handler - vbmeta_a DA_handler - picture_a DA_handler - wt_custom_a DA_handler - logo_b DA_handler - md1img_b DA_handler - spmfw_b DA_handler - scp_b DA_handler - sspm_b DA_handler - gz_b DA_handler - lk_b DA_handler - boot_b DA_handler - dtbo_b DA_handler - tee_b DA_handler - spare5 DA_handler - vendor_b DA_handler - system_b DA_handler - vbmeta_b DA_handler - picture_b DA_handler - wt_custom_b DA_handler - oem DA_handler - logdump DA_handler - wt_log DA_handler - elabel DA_handler - spare6 DA_handler - userdata DA_handler - otp DA_handler - flashinfo DA_handler

Is there any solution to fix this?

— Reply to this email directly, view it on GitHub https://github.com/bkerler/mtkclient/issues/1216, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFRDI3HKDIQ3X2EUPDZMDOLZXRSXZAVCNFSM6AAAAABOST2I5SVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUZTSNBSGE3TGNQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[JXRNO]

I'm guessing I have to use vbmeta_a and not vbmeta_b?

[JXRNO]

I've now ran python mtk r boot_a,vbmeta_a boot.img,vbmeta.img to extract the boot.img, sent the file to my phone and patched it with the Magisk tool. Transferred it back onto my pc and ran python mtk w boot_a boot.patched python mtk da meta 3.

After 3 minutes it was done flashing, but I still get the 'bootloader unlocked' warning and Magisk wasn't properly flashed as it still says "installed: no"

[ferouzkassim]

You have to patch vbmeta_a and boot_a for devices with ab structures then flash the patched vbmeta_a and boot_a to have root access

On Fri, 20 Sept 2024, 23:00 JXRNO, @.***> wrote:

I've now ran python mtk r boot_a,vbmeta_a boot.img,vbmeta.img to extract the boot.img, sent the file to my phone and patched it with the Magisk tool. Transferred it back onto my pc and ran python mtk w boot_a boot.patched python mtk da meta 3.

After 3 minutes it was done flashing, but I still get the 'bootloader unlocked' warning and Magisk wasn't properly flashed as it still says "installed: no"

— Reply to this email directly, view it on GitHub https://github.com/bkerler/mtkclient/issues/1216#issuecomment-2364530745, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFRDI3G4V47TOAEVVUOGDZDZXR5GHAVCNFSM6AAAAABOST2I5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGUZTANZUGU . You are receiving this because you commented.Message ID: @.***>

[JXRNO]

Hey,

I patched boot_b and now it's working fine.

Thanks!

[dynamicsamurai816]

I've bumped into the same problem with the Xiaomi Redmi A1 also MT6761.

So the solution is to use boot_b partition? python mtk r boot_b,vbmeta_a boot.img,vbmeta.img? Or also use vbmeta_b partition?

[JXRNO]

I flashed both boot_a and boot_b. You can always back the 2 files up

[dynamicsamurai816]

Just want to ensure I am getting this right. You flashed both boot partitions, so

python mtk.py r boot_a,vbmeta_a boot_a.img,vbmeta_a.img
python mtk.py r boot_b,vbmeta_b boot_b.img,vbmeta_b.img

for both boot_a, boot_b and vmeta_a and vmeta_b. Then patch both boot images with Magisk and extract, and then

python mtk.py da vbmeta_a 3
python mtk.py w boot_a boot_a.patched
python mtk.py da vbmeta_b 3
python mtk.py w boot_b boot_b.patched

Like that? Thank you for your quick response. I'm trying hard to get through this process.

Edit: solved it by flashing both boot_a and boot_b, with just vbmeta.