Meebook M7 Firmware Thread

[musickid]

For this nice device, I would like to see more support and an effort to root/twrp.

Here is what I have so far:

Firmware files from OTA Update v1.5.4: [Download]



Firmware Files Dumped using rkDumper: [Available upon request]


I have tried every utilty I could find and none are able to extract the boot.img nor system.img at this time - it appears.

[musickid]

I finally decided to look at the files in a hex editor and it turns out most (all) of them are empty or corrupt. I've had to delete the firmware linked above in case anyone tries to flash those files.

Here is a link to the captured OTA Update file: https://drive.google.com/file/d/15-w...ew?usp=sharing

I think the issue is this an incremental OTA update and I have yet to find a way to properly extract the contents.

[xiaoyuz]

did u captured OTA Update file by fiddler？ can u share link？

[xiaoyuz]

Originally Posted by musickid

For this nice device, I would like to see more support and an effort to root/twrp.

Here is what I have so far:

Firmware files from OTA Update v1.5.4: [Download]



Firmware Files Dumped using rkDumper: [Available upon request]


I have tried every utilty I could find and none are able to extract the boot.img nor system.img at this time - it appears.

Firmware files from OTA Update v1.5.4: [Download]

link not work ，pls share new links

[musickid]

Originally Posted by xiaoyuz

Firmware files from OTA Update v1.5.4: [Download]
link not work ，pls share new links

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.

[xiaoyuz]

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.

i have spy hyread（oem by boyue）， maybe can check it form ota server？

[xiaoyuz]

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.

Microsoft Windows [版本 10.0.19045.4291]
(c) Microsoft Corporation。保留所有权利。

C:\Users\guang>payload-dumper-go /path/to/payload.bin
2024/04/28 18:48:59 File does not exist: /path/to/payload.bin

C:\Users\guang>cd c:\temp

c:\temp>payload-dumper-go /path/to/payload.bin
2024/04/28 18:49:13 File does not exist: /path/to/payload.bin

c:\temp>payload-dumper-go payload.bin
payload.bin: payload.bin
Payload Version: 2
Payload Manifest Length: 138096
Payload Manifest Signature Length: 267
Found partitions:
boot (105 MB), system (1.2 GB), uboot (4.2 MB), vendor (147 MB), odm (5.3 MB), dtbo (4.1 kB), system_ext (114 MB), product (100 MB), logo (10 MB), waveform (704 kB)
Number of workers: 4
Unhandled operation type: BROTLI_BSDIFF
Unhandled operation type: SOURCE_COPY
vendor (147 MB) [================================================== ============================================] 100 %
uboot (4.2 MB) [================================================== ============================================] 100 %
vendor (147 MB) [================================================== ============================================] 100 %
vendor (147 MB) [================================================== ============================================] 100 %
uboot (4.2 MB) [================================================== ============================================] 100 %
boot (105 MB) [================================================== ============================================] 100 %
vendor (147 MB) [================================================== ========================================] 100 %
uboot (4.2 MB) [================================================== ========================================] 100 %
boot (105 MB) [================================================== ========================================] 100 %
system (1.2 GB) [================================================== ========================================] 100 %
odm (5.3 MB) [================================================== ========================================] 100 %
dtbo (4.1 kB) [================================================== ========================================] 100 %
system_ext (114 MB) [================================================== ========================================] 100 %
logo (10 MB) [================================================== ========================================] 100 %
product (100 MB) [=>------------------------------------------------------------------------------------------] 2 %
Unhandled operation type: SOURCE_COPY

c:\temp>
tyr this project maybe can unpack？
https://github.com/ssut/payload-dumper-go

[musickid]

Yes I tried otadump and all alternatives. payload_dumper requires a dump of (or stock) firmware files.

Note the last section:

[xiaoyuz]

Originally Posted by musickid

Yes I tried otadump and all alternatives. payload_dumper requires a dump of (or stock) firmware files.

Note the last section:

i have a ota firmware model is MEEBOOK Q103，it's have same as M7 cpu RK3566, did u want check it?

[musickid]

Originally Posted by xiaoyuz

i have a ota firmware model is MEEBOOK Q103，it's have same as M7 cpu RK3566, did u want check it?

Sure. I'll have a look. FYI, I found a compatible RK356X loader.bin that can allows flashing of firmware files via RKDevTool_v3.19. This file is needed if a bad .img is flashed.

[xiaoyuz]

any news from M7？

[musickid]

Originally Posted by xiaoyuz

any news from M7？

Unfortunately, I bricked my M7 pretty much completely. I'm currently trying to find a repair shop that can fix it. I would really like to buy another M7, but a big part of the reason for this thread and a rooting effort was to get more performance out of the device. Specifically, I wanted to use Piper TTS, and the factory configuration just wasn't powerful enough to run it without substantial delays.

[xiaoyuz]

Originally Posted by musickid

Unfortunately, I bricked my M7 pretty much completely. I'm currently trying to find a repair shop that can fix it. I would really like to buy another M7, but a big part of the reason for this thread and a rooting effort was to get more performance out of the device. Specifically, I wanted to use Piper TTS, and the factory configuration just wasn't powerful enough to run it without substantial delays.

OMG。。。。。。。。。。。 it‘s bad news

[Never_Sm1le]

After poking around the m7, apperently this device is not bootloader unlockable. No OEM unlock option, fastboot getvar all hang indefinitely, and sideload a gsi using dsu loader didn't work. Second complain from me after cpu scheduler is set to performance