FORUMS
Remove All Ads from XDA

Successfully rebranding Chinese COL-AL10 to European COL-L29: report

89 posts
Thanks Meter: 87
 
By mrspeccy, Member on 1st August 2018, 03:50 PM
Post Reply Email Thread
Dear community,

I recently bought a Honor 10 (AL-10 C00) with 6GB RAM and 128 GB flash memory from China. Since I did not want to use Chinese apps and some of these were really resistant to my attempts to remove them (like the voice search attached to the home button), I researched xda-developers quite extensively for ways to rebrand the phone to a European version (more precisely, L29 C432). In particular, I read the tutorials made for "related" models such as P10, P20, Mate 10, Honor 9, and HonorView 10.

In detail, my plan was to move from firmware COL-AL10 8.1.0.139 (C00GT) to firmware COL-L29 8.1.0.131 (C432), noting that the L29 firmware had a somewhat lower version number than the AL10 but was the most recent available at the time of trying the rebranding. My concern was therefore that the rebranding might brick the phone similarly to what was observed on the Mate 10 (https://forum.xda-developers.com/mat...infos-t3789044). Fortunately, the xloader-check tool from https://forum.xda-developers.com/mat...2b147-t3817241 displayed "02 XLOADER" for both firmwares, so I decided to proceed.

I obtained all firmware files using HuaweiFirmwareFinder (https://play.google.com/store/apps/d...firmwarefinder), paying attention to the fact that only full OTAs can be used for the branding. In the following description, I used 3 ZIP archives containing the L29 8.1.0.131 software, renamed to match the scheme "update.zip, update_data_public.zip and update_all_hw.zip".

My first attempt was to imitate the approach from the tutorial https://forum.xda-developers.com/hua...l-l09-t3779283 made for the P20. I followed the procedure with the following exceptions:

- Magisk and TWRP were already on the phone thanks to the tutorials from the Honor 10 section.

- I took the nocheck-recovery for the View 10 instead of the one for the P20, more precisely I installed "recovery_ramdisk_BKL-L04_nocheck.img" from https://forum.xda-developers.com/hon...flash-t3778085.

- In Step 17, I said ./oeminfo COL-L29 C432 hw/eu

(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)

After booting to nocheck-recovery, an EMUI update screen was shown and slowly counting up, but after a while an error message of the kind "Installation failed" popped up and forced me to make a factory reset. Still, the bootloader was unlocked afterwards and I could reflash TWRP. The state of the phone now was that it had rebranded oeminfo, an unlocked bootloader, a working TWRP but no real operating system.

The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/hon...overy-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.

I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.

This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.

I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.
Attached Thumbnails
Click image for larger version

Name:	rebrand-honor10.jpg
Views:	4028
Size:	250.2 KB
ID:	4562913  
The Following 13 Users Say Thank You to mrspeccy For This Useful Post: [ View ] Gift mrspeccy Ad-Free
 
 
1st August 2018, 07:17 PM |#2  
Honor Supporter
Recognized Contributor
Thanks Meter: 815
 
More
Quote:
Originally Posted by mrspeccy

Dear community,



- In Step 17, I said ./oeminfo COL-29 C432 hw/eu

(By the way, the oeminfo binary is a great tool that allows you to change only the relevant portions of your oeminfo partition related to model number etc. It keeps things such as IMEI intact, so that the bootloader unlock code does not change by the rebranding, contrary to FunkyHuawei's procedure, as it seems.)

.

Can you share me the link to OEM info binary tool ?
1st August 2018, 07:26 PM |#3  
Honor Supporter
OP Member
Copenhagen
Thanks Meter: 87
 
More
It's linked from the thread I used for the first attempt. Direct access: https://mega.nz/#!X0AjASKS!KvXMfbtd8...XlBi0SDZdzJwfo
The Following User Says Thank You to mrspeccy For This Useful Post: [ View ] Gift mrspeccy Ad-Free
1st August 2018, 07:47 PM |#4  
the problem its how to get the bootloader unlock code ?
1st August 2018, 07:52 PM |#5  
Honor Supporter
OP Member
Copenhagen
Thanks Meter: 87
 
More
Quote:
Originally Posted by sweetjuice

the problem its how to get the bootloader unlock code ?

Correct. I received the code from Huawei before they stopped handing out the unlock codes. At the moment, I do not know of any alternatives.
3rd August 2018, 03:27 PM |#6  
Honor Supporter
Junior Member
Thanks Meter: 8
 
More
Quote:
Originally Posted by mrspeccy

Dear community,

(...)

The second and final attempt was to use HuRUpdater (https://forum.xda-developers.com/hon...overy-t3769279). I rebooted to Recovery, placed the 3 ZIP files and the HuRUpdater ZIP in the top directory of the internal memory (accessed via USB), chose "Install" with respect to the HuRUpdater ZIP, waited some minutes and saw the phone rebooting to EMUI 8.1 with many preinstalled Google apps. Success.

I think it should have been possible to skip the step using nocheck-recovery that failed anyway, provided that the oeminfo binary is executed from TWRP before flashing via HuRUpdater. Any further information would be helpful.

This morning, the firmware update COL-L29 8.1.0.143 (C432) arrived. I downloaded the full OTA and installed it via HuRUpdater as described above. The phone runs very smoothly so far. A scrreenshot of the "About phone" page is attached. Note the 6GB RAM that comes from the Chinese version.

I am happy to answer questions and would like to read more about your experiences with rebranding the Honor 10.

Hey, thanks a lot for this thread!
Soo I am about to maybe do the same as you did – would you suggest/think that just doing the second Part will do the trick for me?
Can't really tell if the first part contained something that's relevant for the second/final part to work.

Furthermore – did you encounter any issues yet, now that you've used the eu rom for a bit?
(And does your device show up as certified within the Play Store?)

Oh and of what I understood, you'll have to do OTA Updates manually?

Thanks again for the effort!
3rd August 2018, 05:16 PM |#7  
Honor Supporter
OP Member
Copenhagen
Thanks Meter: 87
 
More
Hi,

if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:

1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:

mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu

3. You "install" the HuRUpdater zip from within TWRP.

If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.

Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.
The Following 5 Users Say Thank You to mrspeccy For This Useful Post: [ View ] Gift mrspeccy Ad-Free
3rd August 2018, 05:44 PM |#8  
Honor Enthusiast
Senior Member
Flag Helsinki
Thanks Meter: 174
 
More
Quote:
Originally Posted by mrspeccy

Hi,

if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:

1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:

mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu

3. You "install" the HuRUpdater zip from within TWRP.

If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.

Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.


Great. I can assure you that without magisk but stock recovery it passes safety net as well.
The Following User Says Thank You to vampirian For This Useful Post: [ View ] Gift vampirian Ad-Free
3rd August 2018, 07:57 PM |#9  
Senior Member
Thanks Meter: 23
 
More
Quote:
Originally Posted by mrspeccy

Hi,

if I were you, I would try only the "second part" involving HuRUpdater, but would make sure that the oeminfo partition is modified before HuRUpdater is called. What about the following:

1. You copy the zip files belonging to the update along with the oeminfo binary to the top of the sdcard
2. You boot into TWRP recovery and start a terminal. There you say:

mkdir /data/local/tmp
cp /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
./oeminfo COL-L29 C432 hw/eu

3. You "install" the HuRUpdater zip from within TWRP.

If it fails, maybe make a factory reset and try again. Re-flashing TWRP might become necessary.

Regarding your questions: I have not experienced any issues with the EU ROM yet. The device passes Safetynet and is shown as certified in PlayStore (possibly thanks to Magisk, which I installed from TWRP, did not test it without). Magisk and TWRP are also the reason why I have to update manually. Huawei ROMs seem to deny OTA updates when a custom recovery and/or root are detected.


I'm the same device and is annoying chinese stuff, but i have some fear to do that. I already have the unlock code, but did not unlocked yet.
4th August 2018, 08:38 AM |#10  
Honor Supporter
Senior Member
Flag Bangalore
Thanks Meter: 40
 
More
Same procedure for AL 10 c675?
4th August 2018, 08:43 AM |#11  
Junior Member
Thanks Meter: 0
 
More
Hi mine has this L29 Sp6c200 any chance changing roms?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes