Rebrand and lock bootloader again? - Huawei Mate 10 Questions & Answers

Hello, premising I have the bootloader code, I wonder what is the safest method to rebrand from bla-l09(c55) to bla-l09(c432) or bla-29(c432). The problem is the updates slowness. I need a reversible method..furthermore there are any way to lock (not relock) bootloader again if I need warranty? Thanks for your help, I'm new in huawei modding and I didn't think that it is so dramatic!
Inviato dal mio BLA-L09 utilizzando Tapatalk

---

funkyhuawey. i've debranded my l09-c55 to l29-c432 and BL is showned as LOCKED
I was in need to use dual sim and it works flawlessly

---

BoORDeL said:
funkyhuawey. i've debranded my l09-c55 to l29-c432 and BL is showned as LOCKED
I was in need to use dual sim and it works flawlessly
Click to expand...
Click to collapse
One problem with FH is that you can't use your unlock code anymore after rebranding with it, as it changes your own unlock code.
And if you then update to a "new bootloader" firmware on C432 (B146+) you can not get a new unlock code at all.
To get technical: FH can rebrand to dual sim because it has an dual sim oeminfo included, this one has its own imei/imei2/sn which is used when calculating a valid unlock code. When you flash it the unlock code you had will be invalid because of the changed imei/imei2/sn (in fastboot, in system its shown as your own). So I would suggest to not use this to rebrand if you still want to unlock in the future.
@L3onX use HWOTA to rebrand. https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g
And instructions:
ante0 said:
Download and extract HWOTA8 zip, download update.zip public and hw zips for the cust you want to go to from Firmware Finder or http://pro-teammt.ru/firmware-database/
Rename hw zip to update_all_hw.zip, rename public zip to update_data_public.zip.
Place all 3 in the repack folder in HWOTA8.
And here a tutorial I found:
"run rebrand.bat from the HWOTA8_Mate10 / rebrand folder.
*
Follow the instructions carefully and select the region in which you want to rebrand. For example you are in a firmware with region C636 (Hong Kong, Australia, Philippines, Singapore ...) and you want to rebrand in a European version, and choose a version C432. Always be careful when choosing a region that corresponds to your model of Mate 10 Pro (BLA-L29, ALP-L09).
*
Download a firmware corresponding to your new region and flash it using ota/ota.bat" -You should have them in the repack folder already.
"At the end of the installation, an error message will appear "software install failed". This is normal at this point, do not worry.
*
Enter recovery mode and perform a factory reset or let the phone restart until you see the message "Low-level format data partition" appear. Perform the operation.
*
Start again ota.bat and this time, the update will be done successfully"
Click to expand...
Click to collapse
Also note: if you currently are on "xloader 02" you can not rebrand to a firmware with "xloader 01", this will result in a brick that can't be recovered. Check here for more info:
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241

---

ante0 said:
One problem with FH is that you can't use your unlock code anymore after rebranding with it, as it changes your own unlock code.
And if you then update to a "new bootloader" firmware on C432 (B146+) you can not get a new unlock code at all.
To get technical: FH can rebrand to dual sim because it has an dual sim oeminfo included, this one has its own imei/imei2/sn which is used when calculating a valid unlock code. When you flash it the unlock code you had will be invalid because of the changed imei/imei2/sn (in fastboot, in system its shown as your own). So I would suggest to not use this to rebrand if you still want to unlock in the future.
@L3onX use HWOTA to rebrand. https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g
And instructions:
Also note: if you currently are on "xloader 02" you can not rebrand to a firmware with "xloader 01", this will result in a brick that can't be recovered. Check here for more info:
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
Click to expand...
Click to collapse
with FH is that you can't use your unlock code anymore: True but you can use DCUNLOCKER
if you currently are on "xloader 02": i've checked my xloader before debranding the phone (anyway all current firmware on c55 use xl01)

---

BoORDeL said:
with FH is that you can't use your unlock code anymore: True but you can use DCUNLOCKER
if you currently are on "xloader 02": i've checked my xloader before debranding the phone (anyway all current firmware on c55 use xl01)
Click to expand...
Click to collapse
You can't use DC unlocker if you rebrand to, for example, C432B146 or higher. B146 has new bootloader and you can't downgrade to B142 from that, which is the last build where DC worked.

---

ante0 said:
You can't use DC unlocker if you rebrand to, for example, C432B146 or higher. B146 has new bootloader and you can't downgrade to B142 from that, which is the last build where DC worked.
Click to expand...
Click to collapse
didn't know... thanks

---

Thanks for the answers.
ante0 said:
One problem with FH is that you can't use your unlock code anymore after rebranding with it, as it changes your own unlock code.
And if you then update to a "new bootloader" firmware on C432 (B146+) you can not get a new unlock code at all.
To get technical: FH can rebrand to dual sim because it has an dual sim oeminfo included, this one has its own imei/imei2/sn which is used when calculating a valid unlock code. When you flash it the unlock code you had will be invalid because of the changed imei/imei2/sn (in fastboot, in system its shown as your own). So I would suggest to not use this to rebrand if you still want to unlock in the future.
@L3onX use HWOTA to rebrand. https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g
And instructions:
Also note: if you currently are on "xloader 02" you can not rebrand to a firmware with "xloader 01", this will result in a brick that can't be recovered. Check here for more info:
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
Click to expand...
Click to collapse
I prefer to use hwota because fh costs a lot and it will change my bootloader code. Unfortunately Firmware Finder has problem with their servers now. However, hoping they will solve the problem, I'm on b139 (c55) that I suppose is "xloader 01", can I chose any build I want of c432? In addiction to unlocking bootloader, do I need to do anything else before to follow the instruction?
After that can I lock bootloader again or only relock?
Inviato dal mio BLA-L09 utilizzando Tapatalk

---

L3onX said:
Thanks for the answers. I prefer to use hwota because fh costs a lot and it will change my bootloader code. Unfortunately Firmware Finder has problem with their servers now. However, hoping they will solve the problem, I'm on b139 (c55) that I suppose is "xloader 01", can I chose any build I want of c432? In addiction to unlocking bootloader, do I need to do anything else before to follow the instruction?
After that can I lock bootloader again or only relock?
Inviato dal mio BLA-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
Since FF is down due to them moving servers I can not check either... But if you are rooted or just have TWRP you can dump your current xloader and check.
just open a terminal (from running system or TWRP) and use this command:
dd if=/dev/block/sda of=/sdcard/xloader.img
then transfer xloader to computer and open in HxD, check what value offset 1A8 is.
going 01 to 02 is fine, but you can't go back to 01 when you are on 02. And HWOTA doesn't check this so you can flash 01 firmware when you have 02 xloader, this ends up in a brick (Only black screen and phone is recognized as USB_SER. It might be fixable with test-point but I haven't heard anyone that tried)
Other than that there's not much prep-work to do. You will just have to wait for FF get back online
Edit: As for locking. HWOTA can lock bootloader, but you will have to use the repack script which I know doesn't work with later firmware. Can't remember exactly when it stopped working...

---

ante0 said:
Since FF is down due to them moving servers I can not check either... But if you are rooted or just have TWRP you can dump your current xloader and check.
just open a terminal (from running system or TWRP) and use this command:
dd if=/dev/block/sda of=/sdcard/xloader.img
then transfer xloader to computer and open in HxD, check what value offset 1A8 is.
going 01 to 02 is fine, but you can't go back to 01 when you are on 02. And HWOTA doesn't check this so you can flash 01 firmware when you have 02 xloader, this ends up in a brick (Only black screen and phone is recognized as USB_SER. It might be fixable with test-point but I haven't heard anyone that tried)
Other than that there's not much prep-work to do. You will just have to wait for FF get back online
Edit: As for locking. HWOTA can lock bootloader, but you will have to use the repack script which I know doesn't work with later firmware. Can't remember exactly when it stopped working...
Click to expand...
Click to collapse
I have not twrp, so I can't check xloader... But I suppose that if I will chose "02 xloader" version of c432 I will not have problem but probably I will not able to lock bootloader again
Inviato dal mio BLA-L09 utilizzando Tapatalk

---

L3onX said:
I have not twrp, so I can't check xloader... But I suppose that if I will chose "02 xloader" version of c432 I will not have problem but probably I will not able to lock bootloader again
Inviato dal mio BLA-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
If I'm reading the script correctly it just adds "hw_fblock_init_func();" to META-INF/com/google/android/post-script to the hw zip.
So it should be possible to do it manually. You'd just have to open the hw zip in 7zip (or similar) and go to META-INF/com/google/android/ and rightlick on post-script and edit, then add that function and save.
Then flash the update. This would be best doing after you have rebranded and set stuff up though.

---

ante0 said:
If I'm reading the script correctly it just adds "hw_fblock_init_func();" to META-INF/com/google/android/post-script to the hw zip.
So it should be possible to do it manually. You'd just have to open the hw zip in 7zip (or similar) and go to META-INF/com/google/android/ and rightlick on post-script and edit, then add that function and save.
Then flash the update. This would be best doing after you have rebranded and set stuff up though.
Click to expand...
Click to collapse
Sorry for my ignorance, so can I lock bootloader flashing an update with this correction? It seems great!
Inviato dal mio BLA-L09 utilizzando Tapatalk

---

L3onX said:
Sorry for my ignorance, so can I lock bootloader flashing an update with this correction? It seems great!
Inviato dal mio BLA-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
Presumably... I haven't tested it.
But I can on my Mate 9

---

ante0 said:
Presumably... I haven't tested it.
But I can on my Mate 9
Click to expand...
Click to collapse
I should use this method if I need to use warranty, coming back from c432 x02 to c55 x02 (if it will exist)
Inviato dal mio BLA-L09 utilizzando Tapatalk

---

L3onX said:
I should use this method if I need to use warranty, coming back from c432 x02 to c55 x02 (if it will exist)
Inviato dal mio BLA-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
Just tested on my Mate 9. It's installing fine and all but doesn't lock. It might be because I have edited my NVME partition and it's refusing to lock because of it. NVME is not replaced using firmware update so it could be why... I will check logs and see if it says anything about it.

---

ante0 said:
Just tested on my Mate 9. It's installing fine and all but doesn't lock. It might be because I have edited my NVME partition and it's refusing to lock because of it. NVME is not replaced using firmware update so it could be why... I will check logs and see if it says anything about it.
Click to expand...
Click to collapse
Thanks for the test, I follow for any news
Inviato dal mio BLA-L09 utilizzando Tapatalk

---

L3onX said:
Thanks for the test, I follow for any news
Inviato dal mio BLA-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
"read or write nv file ok
modify the value of nv FBLOCK from 0 to 1.
read or write nv file ok
reset fastboot lock state to locked success.
reset fblock to locked successful.
erase check-root successful.
erase rdmode state successful."
That is all it says. My FBLOCK is already 1 due to NVME edit, so that might be why it "fails", though it says it's successful... So I'm not sure.
You could just try it when/if you need to.
I guess I could restore my NVME and try it after, but that'll have to wait until tomorrow

---

ante0 said:
"read or write nv file ok
modify the value of nv FBLOCK from 0 to 1.
read or write nv file ok
reset fastboot lock state to locked success.
reset fblock to locked successful.
erase check-root successful.
erase rdmode state successful."
That is all it says. My FBLOCK is already 1 due to NVME edit, so that might be why it "fails", though it says it's successful... So I'm not sure.
You could just try it when/if you need to.
I guess I could restore my NVME and try it after, but that'll have to wait until tomorrow
Click to expand...
Click to collapse
Great
Inviato dal mio BLA-L09 utilizzando Tapatalk

---

ante0 said:
One problem with FH is that you can't use your unlock code anymore after rebranding with it, as it changes your own unlock code.
And if you then update to a "new bootloader" firmware on C432 (B146+) you can not get a new unlock code at all.
To get technical: FH can rebrand to dual sim because it has an dual sim oeminfo included, this one has its own imei/imei2/sn which is used when calculating a valid unlock code. When you flash it the unlock code you had will be invalid because of the changed imei/imei2/sn (in fastboot, in system its shown as your own). So I would suggest to not use this to rebrand if you still want to unlock in the future.
@L3onX use HWOTA to rebrand. https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g
And instructions:
Also note: if you currently are on "xloader 02" you can not rebrand to a firmware with "xloader 01", this will result in a brick that can't be recovered. Check here for more info:
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
Click to expand...
Click to collapse
Hi, just found out this thread.
My Mate 10 Pro is currently on Android Pie (latest update Jan 2019), I wonder if this still works?
I unlocked my bootloader (no root) and would like to revert it back, is there any risks?
The model is BLA-L29, let me know if you need any other info to diagnose this..
I'm worried of bricking my phone in the process, just tryna be sure
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}