Meebook M7 Firmware Thread

[nsking]

Originally Posted by nsking

I have a Meebook M6A, and I have successfully rooted it.

Like many of you, this device does not have the "OEM Unlock" option in the Settings - Developer Options. However, when I checked using adb shell with the command "getprop | grep lock", I found that the value of "ro.oem_unlock_supported" is "1" on this device. Hence, I believe the OEM unlock is actually enabled. Following this, I used adb reboot bootloader and then entered the fastboot flashing unlock command to successfully unlock the device.

Next, I attempted to sideload a userdebug mode GSI (i use "andyyan-gsi") using the "dsu sideload" tool, but it didn't work as the device got stuck at the logo during boot. However, I noticed that the device was still accessible via adb. I discovered that the adb shell could switch to root using su -. This indicated that the GSI was successfully flashed, but some customizations from the manufacturer prevented it from taking control of the display.

Afterwards, I reinserted the TF card to get it recognized (on my device, its name is mmcblk0p1, and you need to manually mount it to an empty directory). Then, I used "dd if=/dev/block/mmcblk2 | gzip -c > /xxx/xxx/xxx.img.gz" to back up the entire eMMC to the memory card and "dd if=/dev/block/by-name/boot_a of=/xxx/xxx/xxx.img.gz" to back up the boot partition. The next steps were straightforward: use Magisk to patch the boot image and flash it (note the fastboot a/b slot). The first boot after flashing will be slow, so just wait patiently.
--------------
###I cant speak english very well,, so the above content was translated from Chinese by GPT. Thank you for your understanding.

[qtw]

delete

[qtw]

Originally Posted by nsking

I have a Meebook M6A, and I have successfully rooted it.

Like many of you, this device does not have the "OEM Unlock" option in the Settings - Developer Options. However, when I checked using adb shell with the command "getprop | grep lock", I found that the value of "ro.oem_unlock_supported" is "1" on this device. Hence, I believe the OEM unlock is actually enabled. Following this, I used adb reboot bootloader and then entered the fastboot flashing unlock command to successfully unlock the device.

Next, I attempted to sideload a userdebug mode GSI (i use "andyyan-gsi") using the "dsu sideload" tool, but it didn't work as the device got stuck at the logo during boot. However, I noticed that the device was still accessible via adb. I discovered that the adb shell could switch to root using su -. This indicated that the GSI was successfully flashed, but some customizations from the manufacturer prevented it from taking control of the display.

Afterwards, I reinserted the TF card to get it recognized (on my device, its name is mmcblk0p1, and you need to manually mount it to an empty directory). Then, I used "dd if=/dev/block/mmcblk2 | gzip -c > /xxx/xxx/xxx.img.gz" to back up the entire eMMC to the memory card and "dd if=/dev/block/by-name/boot_a of=/xxx/xxx/xxx.img.gz" to back up the boot partition. The next steps were straightforward: use Magisk to patch the boot image and flash it (note the fastboot a/b slot). The first boot after flashing will be slow, so just wait patiently.
--------------
###I cant speak english very well,, so the above content was translated from Chinese by GPT. Thank you for your understanding.

which gsi package you used? could you share you boot.img?

[qtw]

Confirmed, on the Meebook M6, the system image can be obtained by sideloading the GSI image on the DSU.
Package lineage-19.1-20250118-UNOFFICIAL-a64_bvS.img.gz from Andy Yan is available. Remember to back up the entire eMMC data first.
It should be noted that Meebook M6 does not support temporary boot using " fastboot boot <boot.img> " commands. also, adb on recovery is broken.

[master88]

Originally Posted by qtw

Confirmed, on the Meebook M6, the system image can be obtained by sideloading the GSI image on the DSU.
Package lineage-19.1-20250118-UNOFFICIAL-a64_bvS.img.gz from Andy Yan is available. Remember to back up the entire eMMC data first.
It should be noted that Meebook M6 does not support temporary boot using " fastboot boot <boot.img> " commands. also, adb on recovery is broken.

Hello ALL ls share full stock Meebook M6 firmaware dump file
my m6 rip / need help

[master88]

Originally Posted by musickid

OTA Update v1.5.4: https://drive.google.com/file/d/1Py9...ew?usp=sharing

Rename to .zip (or open with 7zip). However because this is an 'incremental' update, it cannot be extracted (properly) with any of the existing tools available.

I am very close to getting working firmware files (to restore bricked devices), and will update the thread as soon as I have them.

pls update link

[qtw]

Originally Posted by master88

Hello ALL ls share full stock Meebook M6 firmaware dump file
my m6 rip / need help

give me your email address

[master88]

Originally Posted by qtw

give me your email address

bigmasters1488 @ gmail.com

[fjay69]

Hi, everyone. I was following nsking's instruction to root my Meebook M6. I've successfully patched boot image by Magisk and flashed it back to my device. However my M6 started bootlooping until it switched to another slot. What went wrong?
(※ I have the original boot img. After flashing it my M6 fine now)

[fjay69]

As a last resort, I tried patching the boot on the same device I'd dumped it from. And this time, everything booted without errors, and I got root!