[GUIDE][TOOL] HiSuite Launcher - EMUI 10 Update

Search This thread

MagnoT

Senior Member
Jul 30, 2015
114
51
HiSuiteLauncher

EMUI 9 fix and EMUI 10 Instructions here: Post. JSON file UPDATED!!!

A Launcher for HiSuite which grabs its ssl calls and hooks them so you can update to EMUI 9.1.

What does it do?
It will launch an instance of HiSuite, Huawei Smartphone PC Manager, if installed. This instance will have a hook to ssl calls made by HiSuite to HiCloud. So we can now handle responses by editing a simple text file for a full ota update. It won't touch anything else. With an update response, HiSuite should now handle the update process including the rollback option if available and a proper imei authorization to HiCloud. This is a way to force an update to your Huawei/Honor smartphone with a standard tool.

Setup and General Info
You will need FirmwareFinder (TeamMT). If you've been around Huawei/Honor forums you should already know what it is. With FF we can track ota updates and even run an authorization test for an update. This is important because we're gonna be using the ota ID and its full link to pass to HiSuite. If you spot an update and your device is not yet authorized to install it your phone will most likely avoid it either.

!IMPORTANT!: I've been using this method since march/19 without any problems. No wipes, connectivity losses, call problems, weird behavior whatsoever. In fact, I'm running EMUI 9.1 now. I don't know how you can ensure the ID you picked is the right one for your device - considering you are using the search correctly: for my Honor 10 C636 I search for COL-L29C636. You might notice the name of the device seems a bit strange and here comes a massive confusion. Col-L29 is now COL-LGRP2-OVS (C636 is overseas) with a bunch of small step rom versions like .226 .227. 228 .229. I usually pick the very first version my phone is authorized for. So my last update was .227. After the update I tested my phone for others versions like .228 and .229 and my phone was authorized for those too. Go figure!

Since HiSuite 9+ the cust info is in the update request and I believe HiCloud suggests the right package for your phone. The reason behind this is because the ota file I get sometimes it's different in size and checksum from the one you get from FF even if it's the same ID. Total speculation here. The cust and preload info have their own json structure. Please revisit the json file below. You can find find cust and preload data in FF simply by searching <your phone model>-<cust/preload>. They both feature their own IDs and urls and they are separated by EMUI versions (Android version).

ALWAYS take note of the rollback ID suggested by HiCloud. It might look like it's just a regular version but it's not! An update and a rollback IDs are different, with different flash scripts. HiCloud will send rollback data with major updates like from EMUI 8.1 to EMUI 9; EMUI 9 to EMUI 9.1. You can spot both IDs in FF as well.

Instructions:
Just extract the zip folder to any suitable folder in your computer and run the Launcher.exe. A console window will popup and HiSuite will appear right after. You can monitor HiSuite calls in the console window.

Remove root and TWRP. You have to be full stock.

Backup data. Even HiSuite will ask you to do it.

Be prepared to download at least 4Gb of data while keeping your phone plugged to your pc.

You will need a very basic understanding of json data structure.

You have 2 files that should remain in the main folder of the launcher:

hisuite9_request_update.txt: you should add the ID to "versionID" and full link to the update ota in "url". Get those from FF.
Please notice that there is a pattern here. The "url" data doesn't include the actual file. UPDATED!!!
{
"status":"0",
"versionPackageCheckResults":[
{
"status":"0",
"autoPollingCycle":"1",
"components":[
{
"componentID":1,
"createTime":"2020-06-19T03:41:07+0000",
"description":"COL-LGRP2-OVS 10.0.0.177",
"name":"COL-LGRP2-OVS 10.0.0.177",
"pointVersion":"1",
"reserveUrl":"updatessl.dbankcdn.com",
"ruleAttr":"",
"url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<UPDATE ID GOES HERE>/f1/",
"version":"COL-LGRP2-OVS 10.0.0.177",
"versionID":"UPDATE ID GOES HERE"
}
],
"versionPackageType":2,
"checkEnd":"1"
},
{
"status":"0",
"autoPollingCycle":"1",
"components":[
{
"componentID":1,
"createTime":"2020-06-19T03:03:11+0000",
"description":"COL-L29-CUST 10.0.0.3(C636)",
"name":"COL-L29-CUST 10.0.0.3(C636)",
"pointVersion":"1",
"reserveUrl":"updatessl.dbankcdn.com",
"ruleAttr":"",
"url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<CUST ID>/f1/",
"version":"COL-L29-CUST 10.0.0.3(C636)",
"versionID":"CUST ID"
}
],
"versionPackageType":3,
"checkEnd":"1"
},
{
"status":"0",
"autoPollingCycle":"1",
"components":[
{
"componentID":1,
"createTime":"2020-06-19T03:03:11+0000",
"description":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
"name":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
"pointVersion":"1",
"reserveUrl":"updatessl.dbankcdn.com",
"ruleAttr":"",
"url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<PRELOAD ID>/f1/",
"version":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
"versionID":"PRELOAD ID"
}
],
"versionPackageType":4,
"checkEnd":"1"
}
]
}

IMEI.txt: add the first IMEI of your phone to the first line of this file.

Hit Update in HiSuite and you should see the red dot indicating an ota update (in fact, the update you added in the file above).

log.txt: this file holds the requests/responses during the current session.

Launcher.exe.config: here you can find a few setup options like hisuite folder.

Bugs
- Well, as far as I'm concerned you shouldn't face any bugs since it's pretty straight forward. BUT, please take my advice: if you're not sure about which update to go for avoid it altogether.

- It does not work with incremental updates. The recovery will reject it.

- In your phone, about phone page, it might not show the update changelog. Sometimes it does show, sometimes it doesn't.

- I cannot confirm this but since I always update my phone through this method I don't get incremental updates anymore. I don't know if it's because I'm always way ahead (updates usually take forever to reach my phone before and that's why I've been doing all of this) or anything else.

Notes:
- I have to thank Smaehtin (XDA) for kindly answering my request to support this tool for Honor 10 and for actually providing this method.
- Although I'm a professional developer (ERP stuff), I'm not used to C# so the code might look a bit messy and funky here and there. I'm sorry for that.
- The solution used is from a freeware compiler, SharDevelop (http://www.icsharpcode.net/OpenSource/SD/).
- Disclaimer here, I am not responsible for any damage you (your phone) might suffer from attempting this. I tested it myself several times in my phone, Honor 10 C636 (COL-L29C636). HiSuite will handle the whole update process but you still can provide wrong data as of wrong IDs or wrong url.
- We are using EasyHook (https://easyhook.github.io/) and Newtonsoft.Json (https://www.newtonsoft.com/json) libs.

Source:
https://github.com/magnot/HiSuiteLauncher
 

Attachments

  • HiSuiteLauncherDebug.zip
    503.7 KB · Views: 996
  • Screenshot_20190724_235729.jpg
    Screenshot_20190724_235729.jpg
    188.6 KB · Views: 2,735
  • Screenshot_20190727_153252_com.teammt.gmanrainy.huaweifirmwarefinder_LI.jpg
    Screenshot_20190727_153252_com.teammt.gmanrainy.huaweifirmwarefinder_LI.jpg
    100.4 KB · Views: 2,775
  • Screenshot_20190727_153308_com.teammt.gmanrainy.huaweifirmwarefinder_LI.jpg
    Screenshot_20190727_153308_com.teammt.gmanrainy.huaweifirmwarefinder_LI.jpg
    120.1 KB · Views: 2,718
  • Screenshot_20190727_175205_com.huawei.android.hwouc.jpg
    Screenshot_20190727_175205_com.huawei.android.hwouc.jpg
    131.4 KB · Views: 2,483
  • launcher_01.jpg
    launcher_01.jpg
    149.3 KB · Views: 2,712
  • launcher_02.jpg
    launcher_02.jpg
    146.1 KB · Views: 2,659
  • launcher_03.jpg
    launcher_03.jpg
    146.9 KB · Views: 2,616
Last edited:

MagnoT

Senior Member
Jul 30, 2015
114
51
Any idea how to spoof only IMEI.txt ?

-Giving us the mean with an early device 's imei to force install the right next update or check what is latest hicloud's OVS FullOTA-MF for a device's cust region and imei.

I wouldn't do that. There's no need to rush an update that way. And if you're not yet authorized for an update the recovery will just reject it.
 

MagnoT

Senior Member
Jul 30, 2015
114
51
@MagnoT Thanks for your work , new version available , I change only version ID and Url link its ok to update ?

Yep, if you have FF confirmation for your device!

.326 is available in FF for quite some time. It's the August EMUI 9.1 security patch update but my device is not authorized for it just yet. The ID is 297131. I'll wait.
 

oslo83

Senior Member
I wouldn't do that. There's no need to rush an update that way. And if you're not yet authorized for an update the recovery will just reject it.
I will do.
I m speaking about getting to know myself which is the latest approved OVS builds for a specified region. (determined by spoofed/original device region)
Late 9.1 OVS build are surely/maybe cust specific now...


By the way, I'm already with a bootloader unlocked on a LYA-L29 demo C652 device which is soft-rebranded to C432 via magisk ^^
So far, I'm getting C432 OTAs ! (when time finally comes for my imei) on in-built Emui updater.

Your tool seems great. -never had to use it for now. (I did with custom FF DNS for some times)

-But I like to use it just to know what is the latest/next right C432 OVS build which is approved and actually fetched for a specified imei.
-Maybe I should get further on my magisk module which is softrebranding to spoof imei for Emui Updater process..... (just though)
 
Last edited:

leap_ahead

Senior Member
Jul 2, 2009
3,223
618
Yep, if you have FF confirmation for your device!

.326 is available in FF for quite some time. It's the August EMUI 9.1 security patch update but my device is not authorized for it just yet. The ID is 297131. I'll wait.

You can check. 330! But still in july update
 

MagnoT

Senior Member
Jul 30, 2015
114
51
I will do.
I m speaking about getting to know myself which is the latest approved OVS builds for a specified region. (determined by spoofed/original device region)
Late 9.1 OVS build are surely/maybe cust specific now...


By the way, I'm already with a bootloader unlocked on a LYA-L29 demo C652 device which is soft-rebranded to C432 via magisk ^^
So far, I'm getting C432 OTAs ! (when time finally comes for my imei) on in-built Emui updater.

Your tool seems great. -never had to use it for now. (I did with custom FF DNS for some times)

-But I like to use it just to know what is the latest/next right C432 OVS build which is approved and actually fetched for a specified imei.
-Maybe I should get further on my magisk module which is softrebranding to spoof imei for Emui Updater process..... (just though)

I guess I get what you mean. In the source code there's an entry to spoof imei which I converted to read from file but that's for the authorization request. Still, I wouldn't go for it. As for knowing in advance the latest/next update roll out based on imei spoofing that would be kinda hard to accomplish imo because... well, it's random and the effort doesn't pay off. I'll have a look into it and update the tool.
 
  • Like
Reactions: oslo83

MagnoT

Senior Member
Jul 30, 2015
114
51
You can check. 330! But still in july update

.330 it's a july security patch for EMUI 9.1. I believe it's still an entry to EMUI 9.1 just like .325. That's the mess we get with this OVS thing... different versions of the same patch all approved. I'll wait for the august update.
 

leap_ahead

Senior Member
Jul 2, 2009
3,223
618
.330 it's a july security patch for EMUI 9.1. I believe it's still an entry to EMUI 9.1 just like .325. That's the mess we get with this OVS thing... different versions of the same patch all approved. I'll wait for the august update.

I flash 326 over 330 all ok !
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    HiSuiteLauncher

    EMUI 9 fix and EMUI 10 Instructions here: Post. JSON file UPDATED!!!

    A Launcher for HiSuite which grabs its ssl calls and hooks them so you can update to EMUI 9.1.

    What does it do?
    It will launch an instance of HiSuite, Huawei Smartphone PC Manager, if installed. This instance will have a hook to ssl calls made by HiSuite to HiCloud. So we can now handle responses by editing a simple text file for a full ota update. It won't touch anything else. With an update response, HiSuite should now handle the update process including the rollback option if available and a proper imei authorization to HiCloud. This is a way to force an update to your Huawei/Honor smartphone with a standard tool.

    Setup and General Info
    You will need FirmwareFinder (TeamMT). If you've been around Huawei/Honor forums you should already know what it is. With FF we can track ota updates and even run an authorization test for an update. This is important because we're gonna be using the ota ID and its full link to pass to HiSuite. If you spot an update and your device is not yet authorized to install it your phone will most likely avoid it either.

    !IMPORTANT!: I've been using this method since march/19 without any problems. No wipes, connectivity losses, call problems, weird behavior whatsoever. In fact, I'm running EMUI 9.1 now. I don't know how you can ensure the ID you picked is the right one for your device - considering you are using the search correctly: for my Honor 10 C636 I search for COL-L29C636. You might notice the name of the device seems a bit strange and here comes a massive confusion. Col-L29 is now COL-LGRP2-OVS (C636 is overseas) with a bunch of small step rom versions like .226 .227. 228 .229. I usually pick the very first version my phone is authorized for. So my last update was .227. After the update I tested my phone for others versions like .228 and .229 and my phone was authorized for those too. Go figure!

    Since HiSuite 9+ the cust info is in the update request and I believe HiCloud suggests the right package for your phone. The reason behind this is because the ota file I get sometimes it's different in size and checksum from the one you get from FF even if it's the same ID. Total speculation here. The cust and preload info have their own json structure. Please revisit the json file below. You can find find cust and preload data in FF simply by searching <your phone model>-<cust/preload>. They both feature their own IDs and urls and they are separated by EMUI versions (Android version).

    ALWAYS take note of the rollback ID suggested by HiCloud. It might look like it's just a regular version but it's not! An update and a rollback IDs are different, with different flash scripts. HiCloud will send rollback data with major updates like from EMUI 8.1 to EMUI 9; EMUI 9 to EMUI 9.1. You can spot both IDs in FF as well.

    Instructions:
    Just extract the zip folder to any suitable folder in your computer and run the Launcher.exe. A console window will popup and HiSuite will appear right after. You can monitor HiSuite calls in the console window.

    Remove root and TWRP. You have to be full stock.

    Backup data. Even HiSuite will ask you to do it.

    Be prepared to download at least 4Gb of data while keeping your phone plugged to your pc.

    You will need a very basic understanding of json data structure.

    You have 2 files that should remain in the main folder of the launcher:

    hisuite9_request_update.txt: you should add the ID to "versionID" and full link to the update ota in "url". Get those from FF.
    Please notice that there is a pattern here. The "url" data doesn't include the actual file. UPDATED!!!
    {
    "status":"0",
    "versionPackageCheckResults":[
    {
    "status":"0",
    "autoPollingCycle":"1",
    "components":[
    {
    "componentID":1,
    "createTime":"2020-06-19T03:41:07+0000",
    "description":"COL-LGRP2-OVS 10.0.0.177",
    "name":"COL-LGRP2-OVS 10.0.0.177",
    "pointVersion":"1",
    "reserveUrl":"updatessl.dbankcdn.com",
    "ruleAttr":"",
    "url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<UPDATE ID GOES HERE>/f1/",
    "version":"COL-LGRP2-OVS 10.0.0.177",
    "versionID":"UPDATE ID GOES HERE"
    }
    ],
    "versionPackageType":2,
    "checkEnd":"1"
    },
    {
    "status":"0",
    "autoPollingCycle":"1",
    "components":[
    {
    "componentID":1,
    "createTime":"2020-06-19T03:03:11+0000",
    "description":"COL-L29-CUST 10.0.0.3(C636)",
    "name":"COL-L29-CUST 10.0.0.3(C636)",
    "pointVersion":"1",
    "reserveUrl":"updatessl.dbankcdn.com",
    "ruleAttr":"",
    "url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<CUST ID>/f1/",
    "version":"COL-L29-CUST 10.0.0.3(C636)",
    "versionID":"CUST ID"
    }
    ],
    "versionPackageType":3,
    "checkEnd":"1"
    },
    {
    "status":"0",
    "autoPollingCycle":"1",
    "components":[
    {
    "componentID":1,
    "createTime":"2020-06-19T03:03:11+0000",
    "description":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
    "name":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
    "pointVersion":"1",
    "reserveUrl":"updatessl.dbankcdn.com",
    "ruleAttr":"",
    "url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<PRELOAD ID>/f1/",
    "version":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
    "versionID":"PRELOAD ID"
    }
    ],
    "versionPackageType":4,
    "checkEnd":"1"
    }
    ]
    }

    IMEI.txt: add the first IMEI of your phone to the first line of this file.

    Hit Update in HiSuite and you should see the red dot indicating an ota update (in fact, the update you added in the file above).

    log.txt: this file holds the requests/responses during the current session.

    Launcher.exe.config: here you can find a few setup options like hisuite folder.

    Bugs
    - Well, as far as I'm concerned you shouldn't face any bugs since it's pretty straight forward. BUT, please take my advice: if you're not sure about which update to go for avoid it altogether.

    - It does not work with incremental updates. The recovery will reject it.

    - In your phone, about phone page, it might not show the update changelog. Sometimes it does show, sometimes it doesn't.

    - I cannot confirm this but since I always update my phone through this method I don't get incremental updates anymore. I don't know if it's because I'm always way ahead (updates usually take forever to reach my phone before and that's why I've been doing all of this) or anything else.

    Notes:
    - I have to thank Smaehtin (XDA) for kindly answering my request to support this tool for Honor 10 and for actually providing this method.
    - Although I'm a professional developer (ERP stuff), I'm not used to C# so the code might look a bit messy and funky here and there. I'm sorry for that.
    - The solution used is from a freeware compiler, SharDevelop (http://www.icsharpcode.net/OpenSource/SD/).
    - Disclaimer here, I am not responsible for any damage you (your phone) might suffer from attempting this. I tested it myself several times in my phone, Honor 10 C636 (COL-L29C636). HiSuite will handle the whole update process but you still can provide wrong data as of wrong IDs or wrong url.
    - We are using EasyHook (https://easyhook.github.io/) and Newtonsoft.Json (https://www.newtonsoft.com/json) libs.

    Source:
    https://github.com/magnot/HiSuiteLauncher
    2
    EMUI 10

    INSTALL EMUI 10 NOW

    EMUI 10 is here. In order to get ready to EMUI 10 you might have to fix the CUST and PRELOAD versions because my old injection file only flashes the main update file. If your CUST and PRELOAD are wrong HiSuite will fail to pair the pregroup status of your device. You know your CUST and PRELOAD are wrong if in tag "versionPackageRules" the firmware versions reported don't match between all three main firmware data (9.1.0 main file and 9.0.0 CUST/PRELOAD). You can check it in the log file or even in the launcher window while using HiSuite. I am terribly sorry for that.

    Instructions:
    - Use FF to search for the right CUST and PRELOAD files for YOUR region. Example: C636, search COL-L29-PRELOAD and COL-L29-CUST with the C636 hint. They are all separated by EMUI versions. See attachments for a better idea;

    - Just follow the same instructions to replace the update IDs and url indicated in FF for both files in the HiSuite json injection file. Be extra careful here. DO NOT switch the order for these files;
    - versionPackageTypes: 2 = MAIN UPDATE FILE; 3 = CUST; 4 = PRELOAD

    - Run the launcher and wait the whole update process to finish;

    - If you need to fix your current CUST and PRELOAD do it for EMUI 9.1 first (you can even reflash your current version) and then repeat the update process for EMUI 10.

    The version I flashed is EMUI 10 10.0.0.177 ID 403647 for my C636. This version were reported as being the official EMUI 10 roll out for Honor by Huawei/Honor/Emui 10 cover sites. If you were not in beta program, don't venture yourself in older updates. FF dropped 6 different IDs. I just got the one with the EMUI 10 presentation description text. In my case, my data was not wiped.

    * These instructions might not apply to other phones, like Huawei.
    1
    Many thanks for the instructions ??
    1
    Success update to emui 9.1.0.325 with this guide.
    1
    I will do.
    I m speaking about getting to know myself which is the latest approved OVS builds for a specified region. (determined by spoofed/original device region)
    Late 9.1 OVS build are surely/maybe cust specific now...


    By the way, I'm already with a bootloader unlocked on a LYA-L29 demo C652 device which is soft-rebranded to C432 via magisk ^^
    So far, I'm getting C432 OTAs ! (when time finally comes for my imei) on in-built Emui updater.

    Your tool seems great. -never had to use it for now. (I did with custom FF DNS for some times)

    -But I like to use it just to know what is the latest/next right C432 OVS build which is approved and actually fetched for a specified imei.
    -Maybe I should get further on my magisk module which is softrebranding to spoof imei for Emui Updater process..... (just though)

    I guess I get what you mean. In the source code there's an entry to spoof imei which I converted to read from file but that's for the authorization request. Still, I wouldn't go for it. As for knowing in advance the latest/next update roll out based on imei spoofing that would be kinda hard to accomplish imo because... well, it's random and the effort doesn't pay off. I'll have a look into it and update the tool.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone