Skip to content

Add 'M2' device assertion#79

Open
Ant95 wants to merge 1 commit intodivis1969:cm-12.1from
Ant95:cm-12.1
Open

Add 'M2' device assertion#79
Ant95 wants to merge 1 commit intodivis1969:cm-12.1from
Ant95:cm-12.1

Conversation

@Ant95
Copy link
Copy Markdown

@Ant95 Ant95 commented Aug 20, 2016

Just had this case problem to flash this rom on a Meizu M2 (mini). The device was identified as "M2" and not "m2".
Not sure if it's the right file to edit to fix the problem as I don't have the required env to build and test it.
Anyway to fix my problem I had to edit this file in the zip: "./META-INF/com/google/android/updater-script".

@divis1969
Copy link
Copy Markdown
Owner

Yeah, this is the right file.
Meantime the problem is that recovery (or maybe ROM) creators does not follow any convention and are inventing new identifiers.
I will include this patch into the next release, but this can be easily broken by new recovery...
BTW, which recovery was in use when you encounter the issue?

@Ant95
Copy link
Copy Markdown
Author

Ant95 commented Aug 22, 2016

Ok, I didn't know that the device identifier was defined by the recovery itself.
I was using a TWRP 3.0 recovery downloaded at: https://drive.google.com/open?id=0ByjTaBzI678NQTBZaTFkNlVYYU0
(Link source: http://www.theverdict.in/how-tos/updated-twrp-3-0-recovery-meizu-m2/)

BTW, I wanted to thank you for your work, everything works fine for now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants