What is "Kernel source code LHD20 for CN SKU"? - Asus ZenWatch 2

On the Asus Zenwatch download page is a new kernel from 18. May:
https://www.asus.com/ZenWatch/ASUS_ZenWatch_2_WI501Q/HelpDesk_Download/
ASUS ZenWatch2 (WI501Q) Kernel source code LHD20 for CN SKU
What is that?

CN SKU to me sounds like the Chinese model of the device.

Related

[Q] Compiling drivers for stock android

Hi all,
I would like to know how to go about compiling drivers for the stock android OS, specifically, usb-serial driver for cp210x. The kernel version in the development tablet is 3.0.8+ and I have compiled an "example" module. When I "insmod" the module in the tab dmesg says
example : disagrees about version of symbol module_layout
I have checked module_layout in the "stock" module and compiled module and equated them using hex editor, but it failed with the same error.
Can anyone suggest me how to go remove this error?

[Q] HELP I can no longer update Mediapad X1 7D 501U /SOLVED/

SOLVED!
I used the dload.zip in this thread http://forum.xda-developers.com/showpost.php?p=56384204&postcount=1
to force installation of my previous rom.
Big thanks to potatohead
I had B008 installed and did an online update to B009 , now I'm getting this error when I try to flash another rom and my device is a 7d-501u.
=========================================
E:check_software_version_rule begin
E:
==========sofeware version rule check==============
E:New software version=7D-501uV100R001C233B021
E:Get software version from vrcb success.
E:Current software version=7D-503LV100R002C208B009
E:Current software version product type=7D-503L
E:New software version product type=7D-501u
E:Error:line:326 :match_product_type not match
Eroduct type mismatch.
E:FAILroduct type check.
E:[huawei_sd_update] time:30.0 s
E:cxt->action: 0
W:finish_recovery, clearset_bootloader_status:flag == null
E:Can't open /tmp/recovery_modem.log

[ROM] PACEfied AmazFit | Huami AmazFit / Xiaomi AmazFit PACE | rel 39 | 1.2.51

NOTE: I am currently extremely busy with work. Therefore, I can only irregularly participate here and updates will currently not be on a weekly basis. I will be looking for some support to see, if others can help with preparing new releases.
Dear all
This is a custom ROM for the Huami AmazFit Smartwatch (A1602) and the Xiaomi AmazFit PACE (A1612).
The ROM is fully functional, but may contain bugs.
FEATURES:
Based on Chinese firmware huanghe-1.2.51 stable firmware
additional translations:
- Italian (thanks to Nicola and @N3OMOD)
- Slovak (thanks to @jasterica and @rbt07(rbarat))
- Polish (thanks to @Kaudii)
- Czech (thanks to @zbani and @rbt07(rbarat))
- Spanish (thanks to @Alain and @saratoga)
- Russian (thanks to @silver-alx)
- French (Thanks to ericmo and Cyril)
- German (Thanks to Klaus H. and others)
- Hungarian (Thanks to gidano)
- Brazilian
- Basque (thanks to @iker)
- Hebrew (thanks to Uri and @1immortal)
additional fonts added
- Hebrew font (thanks to @itsay)
- Arabic fonts (thanks to @1immortal) -> re-added
- Tamil fonts (thanks to @madtech360)
- Thai fonts
- Khmer fonts (thanks to Piseth)
- updated fonts for Bidirectional language support with enable/disable function (see FAQ #14)
English voices in Sports app (thanks to @Fabien)
Updated tzdata (thanks to Alvaro)
command to change Bluetooth max volume to maximum (btVolBoost)
initd system to run customer script upon boot
new boot animation (thanks to @1immortal)
BETA (only for testing, maybe not working correctly):
- first Dutch translation (thanks to Ronny Gyles)
- Turkish (Thanks to ygecesefa )
- rootable with su pre-installed (call "root_amazfit" to enable or disable)
This release is based on the development firmware. We will need to see if it makes sense to follow the development series, as Huami seems to only target the Chinese market with this,
PERMANENT INSTALL:
Please find all information here: https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/permanent-install
ATTENTION: You need to have an unlocked bootloader or run on a rooted ROM (such as PACEfied) for installing this ROM.
Community Project code:
The source code used to build the translated apps is available on the following GitLab repo:
https://gitlab.com/Neuer_User/PACEfied_AmazFit
If people want to contribute, log in, have a look around, download the files you want to translate, and send me the translated files, so I can include them.
Downloads:
Rel 39: Full install Version 1.2.51: (pulled because of problems, please use the below Update version)
Update from Rel 38 to Rel 39 (1.2.51): https://mega.nz/#!wc0DHTrI!08jLXgcDLqDkDF2GIPfQxD2uTJIefRG1WGdDgZQgrIA
Older versions:
Rel 38: Full install Version 1.2.50h: https://mega.nz/#!wUlwnLYR!4NhS_tTpakzCpSHDXKiVY34rqFR_slwXpK99QKo-OP8
Update from Rel 37 (1.2.49k) to Rel 38 (1.2.50h): https://mega.nz/#!oYESkbSQ!iLUGiqiTXKWYF6NVbtp8Y3pgrQT94Taz0keSZhwwGo8
Rel 37: Full install Version 1.2.49k: https://mega.nz/#!ZBEGWDxB!yKrjzI9EBzyiRPCZNgzP0q-kDLbQHC81iFTCw0sD-4w
Rel 36: Full install Version 1.2.49k: https://mega.nz/#!9ItxSITT!qGW2fY-fuv_RYVj77NXfyzjx7AOSl83K8y_zrde1ghE
Update from Rel 35 (1.2.48h) to Rel 36 (1.2.49k): https://mega.nz/#!wUcGFLLJ!Pv1Y4BPR1S4HCGfFXzVVunGRnGWcpNTYUYOC2WgGxlo
Rel 35: Full install Version 1.2.48h: https://mega.nz/#!YR8HwbxZ!DK3wV1lT...K!ouUYcONeynyqSzQe7Xx_2gdkXNEPEyN8HbrgTDyTgbE
Rel 33: Full install Version 1.2.47: https://mega.nz/#!hJUw3RpB!6LSm34TNyWPyW_jtxbCZzeGJQD4igwanC_t-sXFA_e4 (unreleased)
Rel 32: Full install Version 1.2.45: https://mega.nz/#!1dEnGDJS!Uv7hD-BThdaDNh2qEdwyQhTzyMRMjsCJ-UsyfVbQwa4
Rel 31: Full install Version 1.2.44: https://mega.nz/#!lQF0DDhb!VwVztDyJdYfxPZC7DmpGVAieDzErANK5aO4St1fuYtw (NOTE: sogoumap not translated in this release!)Rel 30: Full install Version 1.2.41: https://mega.nz/#!lM1ghCwZ!mKHbjGZSSisfETimtT2o9SYOx0Qa_LF9tae--mfUOQI
Rel 29: Full install Version 1.2.39: https://mega.nz/#!FNsyQIhZ!4jbbtfLfv4ZX8qBAtNcB0NPTrxr0ly7pgag8WnqJJs4
Rel 28: Full install Version 1.2.39: https://mega.nz/#!IAs2jAhJ!ngyMtxq_fcPnShNPsfILhra8vbeu4p4-Ut0MO3Fd4GE
Rel 27: Full install Version 1.2.37: https://mega.nz/#!cNUiQJDb!h2qPrfpU9sxGfu2P0JJNtbbpAblJS_FzR2aHp9Lvk44
Update from Rel 26 (1.2.35) to Rel 27 (1.2.37): https://mega.nz/#!5dciWITK!J3MMeYICcKJEYj2qw6KPOzEL9BjdIU9gattN6OVy17g
Rel 26: Full install Version 1.2.35: https://mega.nz/#!UdViVaBS!Fr3B9ECEm8muxQGv9lkOgGh6u40_LblPPaqiWgcE_Nc
Rel 25: Full install Version 1.2.32: https://mega.nz/#!IE8VVTiY!X82gsHbG988z8Kk22raqj_0Vy_tlgUe4or0CjU5SuE4
Rel 24: Full install Version 1.2.29: https://mega.nz/#!ZMcQya4T!9Cl6HU1WNThUONk4QsH8zBAaQizncqiHiPLZsTZ6Kvc
Update from Rel 22 (1.2.26a) to Rel 23 (1.2.27): https://mega.nz/#!AdcxhCiK!GtzvM5zcnxuNFW01Pr8R_DUafPDIR1EkASElnlb8KT8
Rel 23: Full install Version 1.2.27: https://mega.nz/#!dAsFQKhS!Z8Z9L0h9TW_EPy6SbqxUS3c8qNrhefg5rtzG2vSUjf0
Update from Rel 21 (1.2.25) to Rel 22 (1.2.26a): https://mega.nz/#!UJNEHRzA!tC9c3-Mi3xOdAZmgq34kzrqYBb5a5g7krh5ALWdazbc
Rel 22: Full install Version 1.2.26a: https://mega.nz/#!hUVGDQRT!g5SbkBeVPrgX-3DfUzecXA-NAnWYMsYhuWIwpoFHk6w
Update from Rel 20 (1.2.24) to Rel 21 (1.2.25): https://mega.nz/#!RFsBBL7Q!B3xov7FOMKjAi9jkR-UvfINOG_mwEv9-LwjAK4w0iFc
Rel 21: Full install Version 1.2.25: https://mega.nz/#!gIMC2LCC!8ZxFEe0dnCpqfbWwG5a2lC8_IT0wfEw4ccgOV4tiwkM
Rel 20: Full install Version 1.2.24: https://mega.nz/#!YMEA3bZB!76lg9PlvtRAsqBiAOec8ppAJ9xTtMQsTBJLsm0E_icU
Update from Rel 17 (1.2.21c) to Rel 18 (1.2.22): https://mega.nz/#!0ZlgkQ6R!SCx-XCte4sxSA3ws6G3PFyl-XRu63n3xmI7pBDFInVc
Rel 18: Full install Version 1.2.22: https://mega.nz/#!tE1jHSwY!88C4HgJwMLU3kX9pqDgQ2VA8QuVCyisLRvkxba0_57A
Update from Rel 16 (1.2.20) to Rel 17 (1.2.21c): https://mega.nz/#!oJciQTZa!7HjCTlavT8qvKzOCn6D9cX7U_wkFQYONFj2FKS17sUA
Rel 17: Full install Version 1.2.21c: https://mega.nz/#!hIEj2BCL!nEaosNn5VcQLs_7qMQAXAW566Ab5emv5HiJxwsa6tBg
Update from Rel 15 (1.2.19) to Rel 16 (1.2.20): https://mega.nz/#!9VNUXAbL!NtE2yh3nZfd486LGX-ulAv-APmMAwYY98EvLPgDRSSI
Rel 16: Full install Version 1.2.20: https://mega.nz/#!NA1lmajL!CI-R-o5zngN6vxcR20WpXa8vYGq-uk7T974mySmYvTA
Update from Rel 14 (1.2.18) to Rel 15 (1.2.19): https://mega.nz/#!JA8EXahK!mTJNaIHzSPAWKhk1pmCWGoaxbmv__OGiTdhtRKwAt-I
Rel 15: Full install Version 1.2.19: https://mega.nz/#!NV0xTBAY!fNj40JkFBpS-vE7L_EKcou9JS7wPS7WG_rHkKyOaaSk
Update from Rel 13 (1.2.17) to Rel 14 (1.2.18), permanent install: https://mega.nz/#!MNMUXLDT!Y1tpmG_IslYBR-VdvoQjKUJlHNGaJwFcMxix55FjigY
Rel 14: Full install Version 1.2.18, permanent install: https://mega.nz/#!wIUUXYAY!5rjrMiDMC8kV2JapHsaBR6EXJq7HInfR44IVk8HkZjYUpdate from Rel 12 (1.2.16) to Rel 13 (1.2.17), permanent install: https://mega.nz/#!VZcSGAqK!etek35aNnqKDa_h8ze5g2F3TAaVPr05Y0y4gy6uWm7M
Rel 13: Full install Version 1.2.17, permanent install: https://mega.nz/#!xB0FSTqY!SxB5PVtMB0rRLz7Jo46L9Ulj2LYHvu4F6T3P-NNvHmM
Update from Rel 11 (1.2.15d) to Rel 12 (1.2.16), permanent install: https://mega.nz/#!wR1yCCoa!rfg_DdCWz_z3F-V68XKjEbOiPgOoISIP8E7dYgts2Pk
Rel 12: Full install Version 1.2.16, permanent install: https://mega.nz/#!JNNh3Awb!_vMcgK8AGV6xm7Ns6Z8rkSd3te3T3OPCGXqp550mzcc
Update from Rel 10 (1.2.15a) to Rel 11 (1.2.15d), permanent install: https://mega.nz/#!9VVzEDJA!sZk7rFyrC9UDBG7pXpFTFSqL8Cx4lwc5vYtJ_FzxSbw
Rel 10: Full install Version 1.2.15a, permanent install: https://mega.nz/#!ZdMEiSzT!FYXbk_V4I5aigi2dSjL2UBOyBFMc3P4dRT4FkBXJHaw
Update from Rel 9 (1.2.14) to Rel 10 (1.2.15a), permanent install: https://mega.nz/#!cdVHTLAD!xguDxPPwp00K6VP_-So8Vgc9zCMw85doJgANdFbbwtM
Update from Rel 8 (1.2.13) to Rel 9 (1.2.14), permanent install: https://mega.nz/#!BE9DTJTb!h48h6kWAGRaY82-Xw_nMSPsHl4SUcQ9xJH-bhnbCfvs
Rel 9: Full install Version 1.2.14, permanent install: https://mega.nz/#!sMcSHbaY!fhsiKfeyK559328is4KoffNHpVaCX2PmQXuEYxnP32s
Update from Rel 7 (1.2.11c) to Rel 8 (1.2.13), permanent install: https://mega.nz/#!JZlgWDIB!il7-iekOIafLrQLPKZoMwbc0Yr8dT_NeAoukzAiME5Q
Rel 8: Full install Version 1.2.13, permanent install: https://mega.nz/#!IMUyRQxY!7ARUUNhA6UWhkzTEJAN9__P1dOqntZxC8UASf6wsU_Y
Update from Rel 6 (1.2.11) to Rel 7 (1.2.11c), permanent install: https://mega.nz/#!NYUHgbjL!jG0s6XynvtPW-w61UUBDCh0GY7EHyxNvvHCh3901KhU
Update from Rel 5 (1.2.10) to Rel 6 (1.2.11), permanent install: https://mega.nz/#!FB01gIJL!fRIvUALFjCaC7YGB_cxa3XFXF1DS5yZ-Q1iMZI_L5Og
Rel 6: Full install Version 1.2.11, permanent install: https://mega.nz/#!EZt1gTjK!znlhwdsS40N1DrbshWjM7floyiLlScjF3QFwRtGitxo
Rel 5: Full install Version 1.2.10, permanent install: https://www.google.com/url?q=https:...sntz=1&usg=AFQjCNG4Km1GaXmW0iY3hAcm6OEc9Czz2Q
Rel 5: Full install Version 1.2.10, temporary install: https://mega.nz/#!VVlykaLS!WiOPDP-dFbB_o_r49Q7YO-iSUnrzs3L8POgLcJhDqFE
Update from Rel 4 (1.2.9) to Rel 5 (1.2.10), permanent install: https://www.google.com/url?q=https:...sntz=1&usg=AFQjCNHTnJrNQ39QSLqJ_d5zUfmugw3XUA
Update from Rel 3 (1.2.8) to Rel 4 (1.2.9), permanent install: https://mega.nz/#!BdMCAbTJ!59vxmcKqSEqvCIKMYvLHteVE03xLb-oZCbc5PE5loEY
Rel 4: Full install Version 1.2.9, permanent install: https://mega.nz/#!gY0FhRiL!DLTnnuyy36KK8497zZ6jxW1k5KA9skTxpnfCxdhBWUs
Rel 3: Version 1.2.8, permanent install: https://mega.nz/#!lMExkATK!4ZOqX5GKJg_-GpGdPlMP0Q8igkpTAoQ1UpkWcxQZ0N4
Rel 3: Version 1.2.8, temporary install: https://mega.nz/#!UJkTwAbJ!HV57w7-x4kI99ix8SVmdp5RAXHtJ4n-w0WND26y8IhQ
Rel 2: Version 1.2.7, permanent install: https://mega.nz/#!wM9l1BxT!zauHlRWWQn2uqqZ-vvLzvfGvpTl6BleJOzkrtONzq10
Rel 1: Version 1.2.6c, temporary install: https://mega.nz/#!RB0wXK7T!h3DxA5ptWqwnfZzAON212D4BClgxNi3jp6HFPMFZaAw
Rel 1: Version 1.2.6c, permanent install: https://mega.nz/#!lU0SGbAJ!gaKB-sKboy-UfmzcqyLwB9OSnuzYnd7Bb6zDZ_xVOu0
Version 1.2.6b, temporary install: https://mega.nz/#!IEU11CiB!wU11MkyoZ051e5jl367meDmIswVBHtZ2kix90OnKK5Q
Pre-release version 1.2.5a, temporary install: https://mega.nz/#!kZchDS7b!PF0GP5ML_jLYt3FiG3ydet5q8mPzN_-wOHihbjKKh1I
Changelog of PACEfied releases:
Please find the latest changelog at the community page here: https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/changelogs-for-pacefied-firmware-updates
Changelog of original Huami releases:
Please find the latest changelog at the community page here: https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/changelogs-for-official-firmware-updates
FAQ:
The current FAQ can be found on the PACEfied community webpage:
https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/home
If someone wants to help translate the new "TrainingPlan" app, have a look at the attached files, translate them and post the translation. I can then include this in the next releases.
How about already collected data on watch, will it be imported to the temporary rom and via verce?
Tomorrow will test
Inviato dal mio D6633 utilizzando Tapatalk
Neuer_User said:
If someone wants to help translate the new "TrainingPlan" app, have a look at the attached files, translate them and post the translation. I can then include this in the next releases.
Click to expand...
Click to collapse
I think in Facebook group that xml was already translated for Tomas's quests with translating the ROM!?
alexinc said:
How about already collected data on watch, will it be imported to the temporary rom and via verce?
Click to expand...
Click to collapse
If you come from the same firmware, then yes, for sure. If you are on another firmware (e.g. 1.2.3 or 1.3.0n) very likely (it did it always in my tests), but it is not guaranteed,
NOTE: This behaviour may change in the future. @silver-alx is using an approach to separate data partitions between the flashed FW on the watch and the temporary FW. This would be a requirement, if we start modding the code of the apps. So far, this is just FW 1.2.5a with english translation.
alexinc said:
I think in Facebook group that xml was already translated for Tomas's quests with translating the ROM!?
Click to expand...
Click to collapse
Great. If you can upload the translated xmls, I can include them in the next release.
Neuer_User said:
Great. If you can upload the translated xmls, I can include them in the next release.
Click to expand...
Click to collapse
I asked him to do so, as it's not my work and he should be the one to get the credits with Craig who did the translation!
A big thanks, great!!
The process "push the system image and the md5s onto the sdcard" about how many minutes will the process take?
I`m been waiting for 10 minutes.
I found out, about 350 seconds.
translated what i could with Google translate,bing and bab.la.
if someone knows Chinese, please complete the not-translated ones, or i'll update the files tomorrow, hopefully will have access to a person who knows Chinese.
1immortal said:
translated what i could with Google translate,bing and bab.la.
if someone knows Chinese, please complete the not-translated ones, or i'll update the files tomorrow, hopefully will have access to a person who knows Chinese.
Click to expand...
Click to collapse
We have with Craig helping out on Facebook group!
oh, ok, he'll probably do a better job than all of these machine translations
1immortal said:
translated what i could with Google translate,bing and bab.la.
if someone knows Chinese, please complete the not-translated ones, or i'll update the files tomorrow, hopefully will have access to a person who knows Chinese.
Click to expand...
Click to collapse
I don't speak chinese but i looked over the arrays.xml and it says "Difficulty" twice with different chinese words.
English translation gave me "Difficult" and "Difficulty".
I tried to translate to German where it says "schwierig" and "Kleine Schwierigkeit" which makes more sense as it means "Difficult" and "low Difficulty"
I think Difficult and Easy would be the correct translation.
"Cancellation" and "Its too much!" seem to be a bit odd, too but for further translation one should know what the function does on the watch. Unfortunately i am still waiting for mine....
Version2 as translated by Craig over at Facebook. Due to lack of account here he gave me permission to share. So it's not my work, just uploading...
Neuer_User said:
If someone wants to help translate the new "TrainingPlan" app, have a look at the attached files, translate them and post the translation. I can then include this in the next releases.
Click to expand...
Click to collapse
Hi my friend,
It is already done. You can find it in FB group (Xiaomi Huami Amazfit Pace Smartwach) in files train_plan_en.zip or I can send it to you in 2 hours.
There are few more files which you need to copy to assets directory and subdirecrories en and cn (en sub doesnt work so I copied to both).
EDIT: I see somebody already copy this file. There is also TraininPlanEn-v1.zip which including translated apk. You can maybe use it.
kkti said:
Hi my friend,
It is already done. You can find it in FB group (Xiaomi Huami Amazfit Pace Smartwach) in files train_plan_en.zip or I can send it to you in 2 hours.
There are few more files which you need to copy to assets directory and subdirecrories en and cn (en sub doesnt work so I copied to both).
EDIT: I see somebody already copy this file. There is also TraininPlanEn-v1.zip which including translated apk. You can maybe use it.
Click to expand...
Click to collapse
Thanks, guys. Very good.
Do you have all your work at an open central place, e.g. github, or gitlab? I'd like to have an open community project, where many people can help translate or mod the firmware. In case, you do not have that yet, I would like to create such a project.
Neuer_User said:
Thanks, guys. Very good.
Do you have all your work at an open central place, e.g. github, or gitlab? I'd like to have an open community project, where many people can help translate or mod the firmware. In case, you do not have that yet, I would like to create such a project.
Click to expand...
Click to collapse
It is great idea. There is not such a central place. So if you create one it would be great.
Another idea. After friday OTA update you need to prepare new version based on last version. I think we as community can help you with something if you want. I don't know how you check differences between version I mean apks? But we can just decrypt apk and check string.xml and array.xml for changes and than create new apk based on last version.
I already know the process I prepared english version for WearHealth.apk and TraningPlan.apk as well. Both are working very well.
But maybe you require your own process for modification.
Thanks for great work
kkti said:
It is great idea. There is not such a central place. So if you create one it would be great.
Another idea. After friday OTA update you need to prepare new version based on last version. I think we as community can help you with something if you want. I don't know how you check differences between version I mean apks? But we can just decrypt apk and check string.xml and array.xml for changes and than create new apk based on last version.
I already know the process I prepared english version for WearHealth.apk and TraningPlan.apk as well. Both are working very well.
But maybe you require your own process for modification.
Thanks for great work
Click to expand...
Click to collapse
Thanks, any help is greatly appreciated.
I will try to setup a good structure, so that people can easily participate and help. This will, however, take a little bit of time.
Btw. have you tried the PACEfied ROM yet? It has all applications translated to English (except TrainingPlan, which I will add in the next release.

Unlocking the bootloader of a Meizu Pro 5 Chinese

Ok, so this is a braindump of my process of unlocking my new Meizu Pro 5 Chinese, preventing me to forget everything I did until tomorrow, but I'll also try to highlight some gotchas and hopefully give some insights into how things work (the why, not the how).
Sorry for the mangled urls, it's one of my first posts here and I can't post links yet.
But first, some general considerations:
Meizu uses it's own fork of AOSP (Android Open Source Project) called Flyme: h**p://www.flymeos.com/
there are two types of firmwares for Meizu Pro 5, A and G - which is the suffix letter after the version, for example 6.1.0.0G or 5.1.3.0A
the A firmwares are for the Chinese models, and can be found at h**ps://reameizu.com/?s=PRO+5%E7%94%A8Flyme
the G firmwares are for the global models (hence the G), and can be found at h**p://www.flymeos.com/firmwarelist?modelId=10&type=1
the interesting note to make here is that the G firmware is smaller than the A one, because it contains less bloatware
there's no easy conclusive way to see which version you have, the rule of thumb is that if you have a few apps with a Chinese name, and especially if you have the Meizu App Store (h**p://bbsimg.res.flymeos.com/forum/201607/07/174749bi2d0i9bi0q5iia0.png) app, you have the Chinese model
another way is to look at Settings -> Account section, if you only have an "Other account" (and no "Flyme account") section, you have a global model; it's also possible to install the MzAccount apk, which will bring back that section and allow you to login into your Flyme account and root a phone with the G firmware (read below about "official" rooting)
the only conclusive way is to look at the ro.meizu.hardware.version prop from a shell
Code:
[email protected]:/ $ getprop | grep hardware.version
[ro.meizu.hardware.version]: [M576_intl_official]
M576_mobile_public is for Chinese, M576_intl_official is for global
(all shown commands are ran on a global model, unless specified otherwise)
this prop is stored in the /dev/block/platform/15570000.ufs/by-name/procinfo partition (which is a symlink to /dev/block/sda2), and you can dump it with dd from a root shell (note the #)
Code:
[email protected]:/ # dd if=/dev/block/sda2 bs=1 count=58
#! Meizu M86 product info
machine_type=M576_intl_official
58+0 records in
58+0 records out
58 bytes transferred in 0.006 secs (9666 bytes/sec)
there's a file inside the firmware update.zip, namely META-INF/firmware_type, which specifies the model the firmware is for; the updater compares the model from this file with the model from the procinfo partition, if they match it goes ahead with the update, if they're different, it shows the dreaded "Firmware corrupt" error (h**p://bbsimg.res.flymeos.com/forum/201710/03/194357r3mx162uxz7mquir.jpg), which is kind of misleading, if you ask me
To be continued...

P40 Pro+ Preload and CUST for EMUI 11 (C432)

Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Code:
ELS-N39-PRELOAD 11.0.0.3(C432R3)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464313/f1/full/changelog_preload_hw_eu_R3.xml
Code:
ELS-N39-CUST 11.0.0.3(C432)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464311/f1/full/changelog_cust_hw_eu.xml
How I find these:
I wrote a python scraper which goes through all urls like:
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v{version_number}/f1/full/changelog_preload_hw_eu_R3.xml
Click to expand...
Click to collapse
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Land on a OTA - updatable firmware
I used the following OS firmare:
Code:
ELS-LGRP6-OVS 11.0.0.151
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v492669/f1/full//update_full_base.zip
After which, I got an OTA update to 11.0.0.168
This can solve the problem many people are having: Not getting updates after downgrade.
This working.....juhuhu....thanks!
Usually when you can't get OTA is because oeminfo is broken (Broken as in it has the wrong strings in it). I had to manually edit mine to get OTA back.
But if it works it's good for you.
realseangao said:
I wrote a python scraper which goes through all urls like:
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Click to expand...
Click to collapse
Share script
oslo83 said:
Share script
Click to expand...
Click to collapse
This is in python3, I made use of aiohttp to boost the speed. You might want to pip install aiohttp before hand.
Python:
import asyncio
import aiohttp
from time import sleep
cust_template = "http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v{}/f1/full/changelog_cust_hw_eu.xml"
preload_template = "http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v{}/f1/full/changelog_preload_hw_eu_R3.xml"
async def get(i):
url = cust_template.format(i)
try:
async with aiohttp.ClientSession() as session:
async with session.get(url=url) as response:
if (response.status == 200):
print("Found: {}".format(i))
return i
else:
print('Checked: {}, Status Code: {}'.format(url, response.status))
except Exception as e:
print("Unable to get url {} due to {}.".format(url, e.__class__))
return None
async def main(start, end):
ret = await asyncio.gather(*[get(i) for i in range(start, end)])
filtered = list(filter(None, ret))
print("Finalized batch. ret is a list of: {}".format(filtered))
return filtered
res = []
for i in range(460000, 470000, 1000):
print("Start new round: {}".format(i))
res.extend(asyncio.run(main(i, i + 1000)))
print("Ending round: {}".format(res))
# The server has DDOS protection
sleep(5)
print('Final versions found: {}'.format(res))
ante0 said:
Usually when you can't get OTA is because oeminfo is broken (Broken as in it has the wrong strings in it). I had to manually edit mine to get OTA back.
But if it works it's good for you.
Click to expand...
Click to collapse
The reason my OTA was not working was that I landed on a version that has never been officially pushed out from Huawei onto P40 pro plus but shows up in Firmware Finder (I was on 10.1.0.182 before).
I am assuming when pushing updates Huawei server checks your OS version info to determine your next update:
As a made-up example:
If you are on 11.0.151, it will give you 11.0.168
If you are on 11.0.152, server does not know which version to give you since in Huawei's database, you should not land on 11.0.152.
Just as data points:
ELS-LGRP6-OVS 11.0.0.168 and 11.0.0.151 are both official versions for my ELS-N39 (C432)
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Click to expand...
Click to collapse
Hi,
Thanks for sharing this with us, I tried it and it worked flawless, I even got the OTA updates back and updated to 11.0.0.168
Excellent job mate
Really THANK YOU !
Now i'm back on EMUI 11 !
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Code:
ELS-N39-PRELOAD 11.0.0.3(C432R3)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464313/f1/full/changelog_preload_hw_eu_R3.xml
Code:
ELS-N39-CUST 11.0.0.3(C432)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464311/f1/full/changelog_cust_hw_eu.xml
How I find these:
I wrote a python scraper which goes through all urls like:
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Land on a OTA - updatable firmware
I used the following OS firmare:
Code:
ELS-LGRP6-OVS 11.0.0.151
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v492669/f1/full//update_full_base.zip
After which, I got an OTA update to 11.0.0.168
This can solve the problem many people are having: Not getting updates after downgrade.
Click to expand...
Click to collapse
I don't know that this is right.
And if you don't mind Please suggest me to relock bootloader.
hi all, i'm on 10.1.0.137(C636E3R1P1). I tried to find firmware package URL from Firmware Finder but found that 10.1.0.175 and the rest of the firmware are not available anymore. Error: The remote server returned an error: (404) Not Found.
Can anyone help to provide the package URL so that I can upgrade my firmware from 10.1.0.137 to 10.1.0.175 then to 11.0.0.151?
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Snip...
Click to expand...
Click to collapse
That's a really useful post and thank you for the Python script to help us do it for ourselves. I think I am a little late as it seems 'something has changed'
Following the links in my browser, I am receiving the not very useful page 'error' from any of the links posted for http://update.dbankcdn.com/
In addition, the Python script is returning (a lot of) 404's:
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460009/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460029/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460008/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
... snip ... etc.,
I'd be very grateful if someone can help find an OTA updateable EMUI 11 firmware please. I am currently (stuck) on 10.1.0.145 (C432E2R3P3). If it's something as straightforward as a tweak to the URL's in the script, then great and thanks in advance.
I am aware of available firmware here, but 11.0.0.5 looks pretty old in comparison to 11.0.0.168 - and it's not clear whether I'd be able to update with OTA after installing that firmware.
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Code:
ELS-N39-PRELOAD 11.0.0.3(C432R3)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464313/f1/full/changelog_preload_hw_eu_R3.xml
Code:
ELS-N39-CUST 11.0.0.3(C432)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464311/f1/full/changelog_cust_hw_eu.xml
How I find these:
I wrote a python scraper which goes through all urls like:
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Land on a OTA - updatable firmware
I used the following OS firmare:
Code:
ELS-LGRP6-OVS 11.0.0.151
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v492669/f1/full//update_full_base.zip
After which, I got an OTA update to 11.0.0.168
This can solve the problem many people are having: Not getting updates after downgrade.
Click to expand...
Click to collapse
AndroidKittyCat said:
That's a really useful post and thank you for the Python script to help us do it for ourselves. I think I am a little late as it seems 'something has changed'
Following the links in my browser, I am receiving the not very useful page 'error' from any of the links posted for http://update.dbankcdn.com/
In addition, the Python script is returning (a lot of) 404's:
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460009/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460029/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
Checked: http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v460008/f1/full/changelog_cust_hw_eu.xml, Status Code: 404
... snip ... etc.,
I'd be very grateful if someone can help find an OTA updateable EMUI 11 firmware please. I am currently (stuck) on 10.1.0.145 (C432E2R3P3). If it's something as straightforward as a tweak to the URL's in the script, then great and thanks in advance.
I am aware of available firmware here, but 11.0.0.5 looks pretty old in comparison to 11.0.0.168 - and it's not clear whether I'd be able to update with OTA after installing that firmware.
Click to expand...
Click to collapse
realseangao said:
Hi all,
Just would like to share some cust and preload files needed for updating to EMUI 11. I don't think these firmwares are available on Firmaware Finder.
Code:
ELS-N39-PRELOAD 11.0.0.3(C432R3)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464313/f1/full/changelog_preload_hw_eu_R3.xml
Code:
ELS-N39-CUST 11.0.0.3(C432)
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v464311/f1/full/changelog_cust_hw_eu.xml
How I find these:
I wrote a python scraper which goes through all urls like:
where version_number is from 400000, 510000
the file name part "/changelog_preload_hw_eu_R3.xml" makes sure all paths found are for C432(eu) and R3.
Land on a OTA - updatable firmware
I used the following OS firmare:
Code:
ELS-LGRP6-OVS 11.0.0.151
http://update.dbankcdn.com/TDS/data/files/p3/s15/G6613/g1755/v492669/f1/full//update_full_base.zip
After which, I got an OTA update to 11.0.0.168
This can solve the problem many people are having: Not getting updates after downgrade.
Click to expand...
Click to collapse
Hi. I'm having issues with my phone and I was searching for ways to sort it out. I came across this but seems like the links are unavailable. Do you perhaps have another download link? For the cust files, preload file and Ota?
Link geht leider nicht mehr.
could you help us with some links i do have the same problem
I received a lot of help in this thread, which enabled me to upgrade my P40 Pro + after getting GMS working.
I hope it helps.

Categories

Resources