[GUIDE] OTA Update Rootet(Magisk) H6X (Honor 6X)

citizenserious · Oct 11, 2017

I had trouble updating my Honor 6X (BLN-L21) after I rooted it, so I searched the whole xda to gain some information. Finally I made it, so I thought I could share this information with you guys, hope it helps, but I do not take responsibility if not, as you may have already heard, the Honor 6X (like every Kirin device) is very easy to brick.

- If everything is gone alright you should keep all of your data, apps and settings.
- If there is a big update, like from MM to N you maybe should backup all your stuff and relock the bootloader to update (big updates can relock frp so you can't unlock your bootloader then a rollback is the only way.

Successfully tried from:
B360 to B365
B365 to B367

Short Version (for expert users):

1. uninstall busybox bynaries and the Xposed Framework
2. uninstall magisk (inside the app)
3. flash stock recovery.img (of your actual firmware)
4. flash stock boot.img (of your actual firmware)
5. make OTA update (Reminder: safe update file)
6. flash twrp again and root
7. you are all done

Detailed Version:
#cmd commands#

1. backup your system over TWRP #adb reboot recovery# and do a backup there (for safety reasons)
2. #fastboot reboot#
3. uninstall busybox bynaries and the Xposed Framework(not just the app) (if you have it)
4. uninstall magisk (in app over "complete Uninstall button")
5. restart to bootloader #adb reboot bootloader#
6. flash stock recovery #fastboot flash recovery recovery.img# [use the recovery out of your actual firmware, how to extract is explained in the Forum I added at the end
7. flash stock boot #fastboot flash boot boot.img# [also use the extracted version of your actual package]
8. #fastboot reboot#
9. download update over OTA Update app (System update) in stock system. -> If the "System updater" app does not provide a Full version of the update package, the update could get stopped at 8% saying it could not verify the update, if so, just take the step to the error and reboot, if you then search for an update again, the "System updater" should now show you a Full version of the update package. like "BLN-L21C432B365-FULL"
10. you should safe that update files out of the HwOUC folder, so you can extract the recovery.img and boot.img later before you restart your device to do the update, because the system deletes these files after successful update
11. update over OTA Update app (System update) in stock system
12. restart to bootloader (#adb restart bootloader#)
13. flash twrp again #fastboot flash recovery twrp-3.1.1-0-berlin.img# [use the OpenKirin twrp edition (the official leads to a bootloop] -> [url]https://forum.xda-developers.com/honor-6x/development/twrp-t3583413[/URL]
14. Important is not to boot to system after flashing TWRP, exactly like as you installed it the first time. So you do #fastboot reboot# and then Vol down + lock
15. backup your system over TWRP (for safety reasons)
16. #adb reboot recovery#
17. flash Magisk zip in TWRP again
18. reboot in twrp
19. you are ready to go with the latest stock rom

How to extract boot.img and recovery.img out of your actual firmware is explained here:
[url]https://forum.xda-developers.com/honor-6x/how-to/extract-stock-recovery-img-boot-img-img-t3676880[/URL] thanks @Khan ubaid

chrisleLP · Oct 7, 2017 at 3:53 AM

citizenserious said:
the Honor 6X is very easy to brick.

Not just the 6X but every Kirin device.

RedSkull23 · Oct 7, 2017 at 3:36 PM

This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?

citizenserious · Oct 9, 2017 at 10:37 PM

RedSkull23 said:
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?

I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help

RedSkull23 · Oct 10, 2017 at 8:00 AM

citizenserious said:
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help

What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today

citizenserious · Oct 10, 2017

RedSkull23 said:
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today

I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too

itisiryan · Oct 12, 2017 at 3:12 AM

Thank for this guide. I might use this when an update comes.

A7sas.507.sss@gmail.com · Sep 24, 2017 1 0 0

itisiryan · Oct 17, 2017 at 3:28 AM

[email protected] said:

What's the matter?

RedSkull23 · Oct 30, 2017 at 1:39 PM

citizenserious said:
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too

Finally i found some time to dedicate on updating my phone, and I'm happy to say that it worked. I made from B360 to B365 and from B365 to B367, both worked at first shot. The only thing that i just can't understand is why the OTA package downloaded yesterday worked immediately, while the same B365-FULL package downloaded a month ago, copied on PC before starting it and later started didn't. With stock recovery and boot images obviously. I tried to start it later but nothing, i tried dload method with the update.app but neither that worked. Probably the OTA downloaded creates a sort of signature that can't be recreated that easily, if the same package fails through dload method... But what matters most is that now I'm on B367, protected with the latest security patch. Sorry for the late answer, time is hard to find... Thanks

Archerous · Oct 31, 2017

Hi

Can someone upload the boot.img and and recovery.img from B367

Thanks in advance

shashank1320 · Oct 31, 2017 at 10:22 AM

Archerous said:
Hi

Can someone upload the boot.img and and recovery.img from B367

Thanks in advance

B367 of which model BLN-LXXCXXX?

Archerous · Oct 31, 2017 at 10:29 AM

shashank1320 said:
B367 of which model BLN-LXXCXXX?

I forgot sorry

BLN-L21C432B367

shashank1320 · Oct 31, 2017 at 10:38 AM

Archerous said:
I forgot sorry

BLN-L21C432B367

Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature

Archerous · Oct 31, 2017

shashank1320 said:
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature

There is no B367 in the Repository,no boot.img or recovery. thanks for you help

I wait for the next update,and i will not forget to save the update.app to pc. And extract the files

shashank1320 · Oct 31, 2017 at 11:12 AM

Archerous said:
There is no B367 in the Repository,no boot.img or recovery. thanks for you help

I wait for the next update,and i will not forget to save the update.app to pc. And extract the files

@RedSkull23, please see bro. You have updated to this and may be able to share :good:

Archerous · Oct 31, 2017 at 11:15 AM

shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:

I share ist,with the next update :good:

RedSkull23 · Oct 31, 2017 at 2:45 PM

shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:

If we find the B367 package I'll upload everything from it!

shadowcliffs · Dec 20, 2017

I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."

What did I do wrong?

Update: recovered with the official rollback software to 6.0.

shashank1320 · Dec 20, 2017 at 7:39 AM

shadowcliffs said:
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."

What did I do wrong?

You can try full firmware for b365 if available via dload.
Unlock your bootloader and it will boot to twrp and then boot normally.

[GUIDE] OTA Update Rootet(Magisk) H6X (Honor 6X)

Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Recognized Contributor

Senior Member

Recognized Contributor

Senior Member

Recognized Contributor

Senior Member

Senior Member

Senior Member

Recognized Contributor