[Q] Not sure about updating from BLA-L09C432 B142 to B150 without bricking - Huawei Mate 10 Questions & Answers

Hi,
My BLA-L09C432 is rooted with Magisk.
I would want to update from B142 to B150 but unfortunately I'm a bit scared from all the brick posts on here.
From reading a lot of posts I'm still not sure what would be the best option to update without bricking my phone.
What would be the best/safest way to update without loosing root and my data? (I've got a valid funkyhuawei subscription if that helps)
Would this work (good) without bricking?:
- flash original recovery for B142
- funkyhuawei update via eRecovery to B150
- flash TWRP
- flash Magisk again
Thanks in Advance

---

HRUpdater is the best way to keep twrp and magisk i think
The best way for you I think is hrupdater via twrp, and put twrp in "recovery. img" in the same folder of the updates to keep twrp, then reflash magisk (or not) you have to install b150SP1 version which has 01xloader, but check it first!! I'm in that version with the same brand as you (mine is rebranded) and I have just update to this version but I didn't try magisk but I'm sure you can install with the 150SP1 version

---

durc12 said:
The best way for you I think is hrupdater via twrp, and put twrp in "recovery. img" in the same folder of the updates to keep twrp, then reflash magisk (or not) you have to install b150SP1 version which has 01xloader, but check it first!! I'm in that version with the same brand as you (mine is rebranded) and I have just update to this version but I didn't try magisk but I'm sure you can install with the 150SP1 version
Click to expand...
Click to collapse
Okay, but how do I check my current firmware for 01xloader or 02xloader?
The Xloader Check Programm just works for update.zip files.
Also I can't find a B150SP1 on http://pro-teammt.ru/firmware-database/
Any help is greatly appreciated

---

You have to extract the xloader from the mobile via terminal or twrp
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02
Or you can download in firmware finder your rom of tour cust and check with the xlosder tool (search in XDA please).
Please, tell me what specific rom do you have, your compilation number.
If you aren't in C432 or C636, maybe you have to rebrand first. In my case I used a guide from HTCMania who is easiest than xda which information is better but is difficult to find

---

durc12 said:
You have to extract the xloader from the mobile via terminal or twrp
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02
Or you can download in firmware finder your rom of tour cust and check with the xlosder tool (search in XDA please).
Please, tell me what specific rom do you have, your compilation number.
If you aren't in C432 or C636, maybe you have to rebrand first. In my case I used a guide from HTCMania who is easiest than xda which information is better but is difficult to find
Click to expand...
Click to collapse
Thank you very much for the reply.
Like I said I'm running C432B142 currently but I'm not sure how to see which exact compilation number (since I see more than one build B142 in the firmware finder).
The Update to B142 was received over OTA.
I've looked everything through but it just says BLA-L09 8.0.0.142(C432) everywhere.
The Kernel Version says 4.4.23+ [email protected] #1 Wed May 2 02:30:47 CST 2018 if that helps.
I've extracted the xloader.img like you said and with xxd -ps -s 0x1a8 -l 1 /path/to/xloader.img it shows a Offset of 01.
I've also checked both Full-OTA Images of B150 that I found which are v161846 and v161843 which seem to be Offset 02.
I couldn't find a Offset 01 Image of B150 tho.
So can I safely Upgrade from my B142 with Offset 01 to B150 with Offset 02 if I just use 02 in the future?
Should I use v161846 or v161843?

---

deusvult01 said:
Thank you very much for the reply.
Like I said I'm running C432B142 currently but I'm not sure how to see which exact compilation number (since I see more than one build B142 in the firmware finder).
The Update to B142 was received over OTA.
I've looked everything through but it just says BLA-L09 8.0.0.142(C432) everywhere.
The Kernel Version says 4.4.23+ [email protected] #1 Wed May 2 02:30:47 CST 2018 if that helps.
I've extracted the xloader.img like you said and with xxd -ps -s 0x1a8 -l 1 /path/to/xloader.img it shows a Offset of 01.
I've also checked both Full-OTA Images of B150 that I found which are v161846 and v161843 which seem to be Offset 02.
I couldn't find a Offset 01 Image of B150 tho.
So can I safely Upgrade from my B142 with Offset 01 to B150 with Offset 02 if I just use 02 in the future?
Should I use v161846 or v161843?
Click to expand...
Click to collapse
First of all, if you update to arom with 02 xloader, you will not have problem, your device will work, but NO MAGISk AND NO ROOT (and you can´t go back to xloader01).
Im looking now in firmware finder and It´s true that for your device (mine is ALP-l09 with C432B150SP1, magisk working right) there isn´t a "SP1" version. BUT IN FIRMWARE FINDER THERE ARE TWO 8.0.0.150 VERSIONS, so surely one of them is xloader01 and the other is xloader FIRST DOWNLOAD ONE AND CHECK WITH THE TOOL OF XDA, IF NOT, TRY THE OTHER

---

deusvult01 said:
Thank you very much for the reply.
Like I said I'm running C432B142 currently but I'm not sure how to see which exact compilation number (since I see more than one build B142 in the firmware finder).
The Update to B142 was received over OTA.
I've looked everything through but it just says BLA-L09 8.0.0.142(C432) everywhere.
The Kernel Version says 4.4.23+ [email protected] #1 Wed May 2 02:30:47 CST 2018 if that helps.
I've extracted the xloader.img like you said and with xxd -ps -s 0x1a8 -l 1 /path/to/xloader.img it shows a Offset of 01.
I've also checked both Full-OTA Images of B150 that I found which are v161846 and v161843 which seem to be Offset 02.
I couldn't find a Offset 01 Image of B150 tho.
So can I safely Upgrade from my B142 with Offset 01 to B150 with Offset 02 if I just use 02 in the future?
Should I use v161846 or v161843?
Click to expand...
Click to collapse
Yes, 01 to 02 is fine. 02 to 01 bricks.
But Im pretty sure 02 will stick.
If you haven't got your unlock code saved I would suggest getting it before updating as there is no way to get it when you are on B145+.

---

durc12 said:
First of all, if you update to arom with 02 xloader, you will not have problem, your device will work, but NO MAGISk AND NO ROOT (and you can´t go back to xloader01).
Im looking now in firmware finder and It´s true that for your device (mine is ALP-l09 with C432B150SP1, magisk working right) there isn´t a "SP1" version. BUT IN FIRMWARE FINDER THERE ARE TWO 8.0.0.150 VERSIONS, so surely one of them is xloader01 and the other is xloader FIRST DOWNLOAD ONE AND CHECK WITH THE TOOL OF XDA, IF NOT, TRY THE OTHER
Click to expand...
Click to collapse
I double checked now and both version, 161846 and 161843, have a 02 Offset (Downloaded the images via firmware finder).
Why will Magisk/Root not work anymore with 02 Offset?
ante0 said:
Yes, 01 to 02 is fine. 02 to 01 bricks.
But Im pretty sure 02 will stick.
If you haven't got your unlock code saved I would suggest getting it before updating as there is no way to get it when you are on B145+.
Click to expand...
Click to collapse
I have a backup of the code. Will Magisk still work over B145+?

---

deusvult01 said:
I double checked now and both version, 161846 and 161843, have a 02 Offset (Downloaded the images via firmware finder).
Why will Magisk/Root not work anymore with 02 Offset?
I have a backup of the code. Will Magisk still work over B145+?
Click to expand...
Click to collapse
Magisk/TWRP works fine on B150.
I was previously 01 with B142 as base, but flashed images for B150 (except xloader and fastboot). But I decided to try Pie which is 02, then downgraded to B150 because of no root in Pie (and it is buggy) so now I'm stuck on 02
Magisk V17.x is buggy, I suggest using 16.4.
There are Patch01 OTA which break Magisk, but can be flashed if you select Keep dmverity in Manager when patching ramdisk. (flashing in TWRP will remove verity, and thus giving you a bootloop).

---

ante0 said:
Magisk/TWRP works fine on B150.
I was previously 01 with B142 as base, but flashed images for B150 (except xloader and fastboot). But I decided to try Pie which is 02, then downgraded to B150 because of no root in Pie (and it is buggy) so now I'm stuck on 02
Magisk V17.x is buggy, I suggest using 16.4.
There are Patch01 OTA which break Magisk, but can be flashed if you select Keep dmverity in Manager when patching ramdisk. (flashing in TWRP will remove verity, and thus giving you a bootloop).
Click to expand...
Click to collapse
Yes or follow the guide here for the patch01 https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389

---

ante0 said:
Magisk/TWRP works fine on B150.
I was previously 01 with B142 as base, but flashed images for B150 (except xloader and fastboot). But I decided to try Pie which is 02, then downgraded to B150 because of no root in Pie (and it is buggy) so now I'm stuck on 02
Magisk V17.x is buggy, I suggest using 16.4.
There are Patch01 OTA which break Magisk, but can be flashed if you select Keep dmverity in Manager when patching ramdisk. (flashing in TWRP will remove verity, and thus giving you a bootloop).
Click to expand...
Click to collapse
Ok so just to break it down, I've got to do the following:
- Flash B150 with HuRUpdater (161846 or 161843?) in TWRP (or should I do the FunkyHuawei eRecovery Method? which is safer?)
- When its finished flash TWRP again.
- Flash Magisk (16.4 not 17.x)
Lol is it really that simple?
Just another Question:
When i first flashed Magisk (in B131 i think) I'm damn sure i had forced encryption checked without me doing anything (I do want encryption enabled, thats even more important than root for me tbh). Now I took a look because you've mentioned dmverity and I see that both dmverity and encryption are unchecked.
After flashing like mentioned above, how can I make sure that encryption is enabled without bricking my phone ?
Thank you so much for the help!

---

deusvult01 said:
Ok so just to break it down, I've got to do the following:
- Flash B150 with HuRUpdater (161846 or 161843?) in TWRP (or should I do the FunkyHuawei eRecovery Method? which is safer?)
- When its finished flash TWRP again.
- Flash Magisk (16.4 not 17.x)
Lol is it really that simple?
Just another Question:
When i first flashed Magisk (in B131 i think) I'm damn sure i had forced encryption checked without me doing anything (I do want encryption enabled, thats even more important than root for me tbh). Now I took a look because you've mentioned dmverity and I see that both dmverity and encryption are unchecked.
After flashing like mentioned above, how can I make sure that encryption is enabled without bricking my phone ?
Thank you so much for the help!
Click to expand...
Click to collapse
Magisk detects encryption it in TWRP as it reads fstab.
You can make it even easier: place update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater.zip in the same folder. Take TWRP image (by Pretoriano80) and place in in that folder too and rename it to recovery.img. Now HuRUpdater will flash TWRP again for you.
If Magisk should, by some weird coincidence, disable encryption you would only need to re-add it to /vendor/etc/fstab.kirin970. It won't boot if your /data is encrypted but isn't told to decrypt it.

---

ante0 said:
Magisk detects encryption it in TWRP as it reads fstab.
You can make it even easier: place update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater.zip in the same folder. Take TWRP image (by Pretoriano80) and place in in that folder too and rename it to recovery.img. Now HuRUpdater will flash TWRP again for you.
If Magisk should, by some weird coincidence, disable encryption you would only need to re-add it to /vendor/etc/fstab.kirin970. It won't boot if your /data is encrypted but isn't told to decrypt it.
Click to expand...
Click to collapse
Ok so just to be sure:
I take the update.zip, update_full_BLA-L09_hw_eu.zip and update_data_full_public.zip from the B150 Firmware (Still I'm not sure which version to use since Firmware finder has 2, both with 02 Offset, v161846 and v161843).
Put that in the same Folder as HuRUpdater.zip, get the TWRP Version from Pretoriano80 that supports Decryption and rename it to recovery.img in the same folder.
Then go in TWRP and flash the HuRUpdater.zip.
Sorry for asking so much but I really want to be sure to make everything right before doing something stupid
Regarding Encryption and Magisk:
I now checked in TWRP and it seems encryption is really turned of, I currently have the official TWRP that does not support decryption and it shows all files etc. not like before where it was just random numbes and characters as file name. So it seems my /data is already decrpyted somehow.
What changes would I have to make (after or before flashing B150?) to re-enable encryption (if possible without loosing my data)?

---

deusvult01 said:
Ok so just to be sure:
I take the update.zip, update_full_BLA-L09_hw_eu.zip and update_data_full_public.zip from the B150 Firmware (Still I'm not sure which version to use since Firmware finder has 2, both with 02 Offset, v161846 and v161843).
Put that in the same Folder as HuRUpdater.zip, get the TWRP Version from Pretoriano80 that supports Decryption and rename it to recovery.img in the same folder.
Then go in TWRP and flash the HuRUpdater.zip.
Sorry for asking so much but I really want to be sure to make everything right before doing something stupid
Regarding Encryption and Magisk:
I now checked in TWRP and it seems encryption is really turned of, I currently have the official TWRP that does not support decryption and it shows all files etc. not like before where it was just random numbes and characters as file name. So it seems my /data is already decrpyted somehow.
What changes would I have to make (after or before flashing B150?) to re-enable encryption (if possible without loosing my data)?
Click to expand...
Click to collapse
Can you do this in TWRP, and post the output here.
Open Advanced-Terminal
mount /vendor
cat /vendor/etc/fstab.kirin970 | grep fileencrypt
and post output here?
As for B150, it doesn't matter which. They are the same, just different update "channels".

---

ante0 said:
Can you do this in TWRP, and post the output here.
Open Advanced-Terminal
mount /vendor
cat /vendor/etc/fstab.kirin970 | grep fileencrypt
and post output here?
As for B150, it doesn't matter which. They are the same, just different update "channels".
Click to expand...
Click to collapse
Thank you so much for your support!
Of course,
# mount /vendor
# cat /vendor/etc/fstab.kirin970 | grep fileencrypt
/dev/block/bootdevice/by-name/userdata /data
f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,filencryption=aes-256-xts:aes-256-cts
#
On the HuRUpdater Page it says the files have to be called update.zip, update_all_hw.zip and update_data_public.zip like you wrote, when I download the firmware I got update.zip, update_full_BLA-L09_hw_eu.zip and update_data_full_public.zip. Should I just rename them?

---

deusvult01 said:
Thank you so much for your support!
Of course,
# mount /vendor
# cat /vendor/etc/fstab.kirin970 | grep fileencrypt
/dev/block/bootdevice/by-name/userdata /data
f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,filencryption=aes-256-xts:aes-256-cts
#
On the HuRUpdater Page it says the files have to be called update.zip, update_all_hw.zip and update_data_public.zip like you wrote, when I download the firmware I got update.zip, update_full_BLA-L09_hw_eu.zip and update_data_full_public.zip. Should I just rename them?
Click to expand...
Click to collapse
Then you are encrypted... Hmmm!
I had the same "bug" on Mate 9 where I'm using TWRP which can decrypt.
BUT, I have pin set so it's supposed to ask for that when you start TWRP, but it doesn't and decrypts automatically. This is probably because it's using vold to decrypt somehow... Not sure how it does it, as it's not supposed to be able to decrypt without a password/pin.
You can do this from TWRP terminal before flashing Magisk:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
This will make sure it keeps both.
Rename update_full_BLA-L09_hw_eu.zip to update_all_hw.zip and update_data_full_public.zip to update_data_public.zip

---

ante0 said:
Then you are encrypted... Hmmm!
I had the same "bug" on Mate 9 where I'm using TWRP which can decrypt.
BUT, I have pin set so it's supposed to ask for that when you start TWRP, but it doesn't and decrypts automatically. This is probably because it's using vold to decrypt somehow... Not sure how it does it, as it's not supposed to be able to decrypt without a password/pin.
You can do this from TWRP terminal before flashing Magisk:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
This will make sure it keeps both.
Rename update_full_BLA-L09_hw_eu.zip to update_all_hw.zip and update_data_full_public.zip to update_data_public.zip
Click to expand...
Click to collapse
Ok so just to sum up everything for the last time
- Rename all files for HuRUpdate.zip including TWRP and put them in the same folder
- Copy the folder to the Root of my phone
- Reboot to recovery, flash HuRUpdate.zip copied before (or is this done via adb sideload?)
- Follow instructions to finish the stock update
- When the stock update is finished boot into TWRP
- decrypt data if needed
- open advanced>terminal and echo KEEPVERITY and KEEPFORCEENCRYPTION to the magisk file
- flash magisk (16.4)
- reboot & everything is finished?

---

deusvult01 said:
Ok so just to sum up everything for the last time
- Rename all files for HuRUpdate.zip including TWRP and put them in the same folder
- Copy the folder to the Root of my phone
- Reboot to recovery, flash HuRUpdate.zip copied before (or is this done via adb sideload?)
- Follow instructions to finish the stock update
- When the stock update is finished boot into TWRP
- decrypt data if needed
- open advanced>terminal and echo KEEPVERITY and KEEPFORCEENCRYPTION to the magisk file
- flash magisk (16.4)
- reboot & everything is finished?
Click to expand...
Click to collapse
It will update inside TWRP so you will stay on the same screen until it finishes.
After it has finished, echo commands and flash Magisk.
After this reboot into B150