[GUIDE] Unlock bootloader, root the device and install any custom ROM! (ALE-L23/21)

Did this work for you?

  • Yes

    Votes: 26 72.2%
  • No

    Votes: 10 27.8%

  • Total voters
    36
Search This thread

SuwalTheGreat

New member
Mar 11, 2017
3
0
Wow wtf thank you so much for this guide, it worked like a charm. KingRoot didn't work for me however, but KingoRoot did, despite showing root failed (root checker showed the device was root already so idk what happened there). I never saw this day coming, using a custom rom in this phone.
 

MDSOPAN

Member
Jul 9, 2018
7
1
Not sure if the P9 lite has the same chip. If it does, it may work, but this only officially support P8 lite 2015.
IT has a different chip the kirin 650 but what happens when I run this command

su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"
 

tralph3

Senior Member
Aug 16, 2016
128
51
20
Ciudad Autonoma de Buenos Aires
su uses the root user, -c is a flag that tells su to execute a command, the command is what follows. grep is a utility to search for patterns in files, you don't really need to understand all that, it's basically searching for the code, nothing is being modified. So, yes, you can try it and nothing bad will happen as a result. At worst, you don't get the code, or you get something invalid.
 

MDSOPAN

Member
Jul 9, 2018
7
1
su uses the root user, -c is a flag that tells su to execute a command, the command is what follows. grep is a utility to search for patterns in files, you don't really need to understand all that, it's basically searching for the code, nothing is being modified. So, yes, you can try it and nothing bad will happen as a result. At worst, you don't get the code, or you get something invalid.
Thank you for your first replies. I have emailed huawei. If that does not work out will try this.
 

jeu_bm

New member
Jun 8, 2021
3
0
Costa Rica, Alajuela
I have an ALE-L02 device, it comes with 5.0 and EMUI 3.1 pre-installed, from the factory.

Would the method work for me and what things would I have to do differently?

I have been looking for a while and the truth is that this is the best I have found in terms of unlocking the bootloader for Huawei P8 Lite devices, I do not want to make any mistakes.
 

jeu_bm

New member
Jun 8, 2021
3
0
Costa Rica, Alajuela
I think it should work, as long as your chipset is the Kirin 620, then you should be good to go. But as always, at your own risk.
OK, I'll give it a try.

Regarding the method itself, the device already comes with Android 5.0 and so on. Do you think that in order to unlock the bootloader it is enough for me to simply skip the startup steps (install 5.0, etc) and then continue with the method as normal?

Sorry for so many questions, this kind of thing is a bit difficult for me.
 

meubeukeu

New member
Mar 7, 2012
2
0
Hi all

My phone is ALE-L21C150B564
Impossible to flash anything with SDCARD. i tried many official ROM, even those used specialy to rollback from 6.0 to 5.0 ... The only way to unlock bootloader for me is with PotatoNV.

now i am working on root it because i am blocked with this C150B564 version ...


Important ; PotatoNV give original unlock code and defaults options are changing it, if unlock code is not the original one, it is impossible to flash recovery

fastboot.exe flash recovery recovery.img
Sending 'recovery' (25152 KB) OKAY [ 0.810s]
Writing 'recovery' FAILED (remote: 'image verification error')
fastboot: error: Command failed


after restoring original unlock code with PotatoNV again ... flashing recovery is working

fastboot.exe flash recovery recovery.img
Sending 'recovery' (25152 KB) OKAY [ 0.810s]
Writing 'recovery' OKAY [ 1.030s]
Finished. Total time: 1.940s



Thanks !!
 
Last edited:

masemoel

Senior Member
Jul 24, 2019
281
104
Jaén
Hi all

My phone is ALE-L21C150B564
Impossible to flash anything with SDCARD. i tried many official ROM, even those used specialy to rollback from 6.0 to 5.0 ... The only way to unlock bootloader for me is with PotatoNV.

now i am working on root it because i am blocked with this C150B564 version ...


Important ; PotatoNV give original unlock code and defaults options are changing it, if unlock code is not the original one, it is impossible to flash recovery

fastboot.exe flash recovery recovery2.img
Sending 'recovery' (25152 KB) OKAY [ 2.025s]
Writing 'recovery' FAILED (remote: 'image verification error')
fastboot: error: Command failed


after restoring original unlock code with PotatoNV again ... flashing recovery is working

fastboot.exe flash recovery recovery.img
Sending 'recovery' (25152 KB) OKAY [ 0.810s]
Writing 'recovery' OKAY [ 1.030s]
Finished. Total time: 1.940s



Thanks !!
Which is that recovery2.img? TWRP??
 

bobcov

Senior Member
Aug 27, 2007
85
8
So....I am in the dark-ages in terms of equipment and here is my problem. Kingroot has to be run from a PC because WiFi and Bluetooth are out of service on the P8lite. (I don't know if this really was a massive chip problem or some kind of one-way software screw-up, but regardless, I can't use Kingroot on the P8lite.)
The MTP driver won't load on my XP home edition pc and maybe that is why Kingroot is failing. Sometimes I get a message that Kingroot thinks I have two phones attached. I switch USB from file mode to disk mode and this message goes away and Kingroot tries to root. I tried using reverse tethering so that I could run Kingroot on the phone, but it seems King is looking at the wrong network interface and just when it gets to trying to find a rooting strategy, it says "no network." Same with Kingoroot.

What other PC, OSX or Linux root programs are there which can tackle the P8 with locked bootloader? If push comes to shove, I will try the PotatoNV route. I also tried using Win10 under Virtualbox in Osx, but I can't find a way to force OSX to let go of the usb connection to the phone. So much fun. The entire point of this is to turn the P8lite into a bicycle GPS, but I can't download the map files because there's no connectivity. I can't place the map file where they need to be because I don't have root.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 26
    Hi all! So, you have a P8 lite in your pocket and you hate EMUI? Well, that was my case too, it's uncustomizable, ugly, and removes plenty of features from android stock. I do not like it one bit, and I like even less the fact that this phone is getting no more updates, ever. This sucks, it all sucks, luckily we can say "F all that" and do whatever we want with this device, provided you follow this guide.

    I am making this guide because I want to condensate every single thing I know about this device in one single thread. One big guide to help all of you out installing custom ROMs. Without this, you would have to do research along multiple threads, often with conflicting information, and what's even worse, DEAD LINKS! There's nothing more frustrating than finally finding the solution to your problem, just one download away, just to be greeted by a dead link, and you would need to scout for another file that may or may not work... ugly stuff.

    So, the point of this is to bring up to date info so you can make this device rock. This guide assumes you have Huawei's EMUI 4.0 installed which runs on Android 6.0. I'm also assuming you have your bootloader locked, and I will explain how to unlock it FOR FREE. No need to pay to some shady site in order to access what effectively belongs to you.

    These are the requirements for this guide:

    Code:
    #USB cable
    #A PC
    #Some charge on the device to ensure nothing goes wrong
    #An SD Card
    #Patience

    Before beggining, a quick disclaimer:

    Code:
    #It's not my objective to break your device, however there's always a risk when doing these kind of things.
    #When you follow this guide's steps your are accepting the risks and are taking full responsiblity for whatever may happen to your device.
    #Don't blame me for breaking your stuff if that happens, all I'm listing here worked for me, and should work for you.
    #I won't be babysitting anybody to help solve their specific problems, don't PM me asking me why X doesn't work.
    #I am unaware if this works in other versions of this device, but I'm positive this works on both ALE-L23 and ALE-L21
    #If you have a "CAM-XXX" device, it's highly likely this works for you too, but as with everything, TRY AT YOUR OWN RISK.
    #YOU HAVE BEEN WARNED!

    Ok, so let's begin. As the title says, the guide is applicable to any custom ROM. However, I will be installing Lineage OS 14.1 which runs on (almost stock) Android 7.1.2. Regardless, the final step where we install the custom ROM is interchangable, and you can use whichever you please.

    This process WILL wipe all of your data (except SD card). Make sure to make a backup of everything you want to save (app configs, photos, videos and whatever else).

    1. DOWNGRADING TO ANDROID 5

    As you may know, Huawei has stopped providing bootloader unlock codes for very stupid reasons. This has led to many unable to unlock their bootloader and having to pay for third party apps in hopes they don't get scammed. There are some trustworthy sites where you can get these at a fee tho (mainly DC Unlocker at 4 bucks), so if you want to pay up to avoid having to downgrade to Android 5, you can do so. However, I understand that you may not want to pay at all, I didn't want to either.

    To get the bootloader unlock code, we need root, and to get root, we need Android 5. Why? Because getting root in Android 6 requires us to flash some zips, and for that we need TWRP, and for that we need an unlocked bootloader, everyhing closes up very nicely. So, we have no choice but to downgrade.

    An SD card is not needed for this process, but it is going to be required at a later point, so why not use it now too?

    NOTE: It may be a good idea to make a factory reset at this point, to avoid issues. For that, do the following:

    1. Turn your phone off.
    2. Boot the phone by holding the power button and the volume up button at the same time.
    3. Wait untill the Huawei logo appears, then let go of both buttons.
    4. You should be in recovery mode, navigate with the volume keys to the "Wipe data/factory reset" option.
    5. Select it with the power button and wipe everything.
    6. Reboot the device with the option in the menu.
    7. Once the device has booted up, follow the guide.


    Alright, once that's done, connect your phone to the PC to transfer some files:

    NOTE: There's two Stock Android 5s downloads ("HW_Android_5_Transition.zip" and "HW_Stock_Android_5.zip"). One is a transition package, as the name implies, and the other is Huawei's EMUI 3.1 in all of it's glory. What's the difference? The transition package is a much smaller file that is designed to downgrade the phone from EMUI 4.0 (Android 6) to EMUI 3.1 (Android 5). If you are running EMUI 4.0 (which should be the case) then you can use the transition package which will take less to download. If you have another version (i.e. EMUI 4.1) you should use "HW_Stock_Android_5.zip". However, the latter is the safe bet. If you are not sure which one to use, use "HW_Stock_Android_5.zip". The process is exactly the same for both packages.

    1. Extract the "UPDATE.APP" file from "HW_Stock_Android_5.zip" or "HW_Android_5_Transition.zip".
    2. Navigate to your phone's internal memory or SD card (whichever you want to use) and locate a folder called "dload". If there's not one, create it.
    3. Put the "UPDATE.APP" file inside of the "dload" folder.
    4. Turn your phone off.
    5. Once it's off, press the power button and the two volume buttons until you see the Huawei logo.

    That should make the phone recognize the "update" and start flashing it. Once it finishes, it will try to boot by itself, so pressing those 3 buttons was your last input until the phone boots into Android 5. It will take a long time for it to both finish and boot, don't be afraid, the phone is not bricked. If you think the phone is indeed bricked because it has been stuck at the logo screen for way to long (longer than an hour) then proceed to the "Unbricking" section of this guide. However, it's highly unlikely that this will happen, as Huawei checks the file before flashing it, so if it's incompatible with your device it should not do anything and boot again into Android 6 with everything untouched.

    2. ROOTING ON ANDROID 5 AND EXTRACTING BOOTLOADER UNLOCK CODE

    Once you are in Android 5, we will need to root the device. Download KingRoot (proved to work) or another one click root app of your choice. I'm aware of KingRoot's bad reputation because of the spyware accusations, but the phone will be wiped anyway and we are sure it works, so it doesn't really harm at all. If you still don't want to use it, check with other apps, I haven't done so myself so I don't know what else works.

    Once your phone is rooted, we will need to use the terminal for the first time. We will need to setup ADB and Fastboot, if you already have that, skip this step.

    1. Extract the "platform-tools" folder from the zip and place it somewhere nice.
    2. Shift right click on a blank space INSIDE of the "platform-tools" folder.
    3. Select "Open command window here".

    This should be enough to get ADB working, but we need to make some config on the phone itself too.

    1. Go to Settings -> About Phone
    2. Look for a line that says "Build Number" and tap it multiple times.
    3. When the message saying "You are now a developer" pops up, go back and enter the new "Developer Options" menu.
    4. In there, look for an option called "USB Debugging" and turn it on.
    5. Connect the phone to your PC via USB cable.
    6. A message should have popped up on the phone asking for permission to use USB Debugging, tap on "Always allow from this PC" and then on "Allow".

    NOTE: If the message doesn't pop up, you can try a number of things. I prefer to tap the "Revoke USB debugging authorizations" button to ensure that no PC is authorized, so the message must pop up at some point. Once you revoked authorizations, disconnect and connect the phone again, if you still don't see it, try to select MTP as the transfer protocol. If not, then PTP, if you still don't see it install Hi Suite on your PC and open it, it should pop up now.

    Once you have everything working, type the following in the terminal in your PC:

    Code:
    adb devices

    If you see a serial number there, that's your phone, and that means everything is set up correctly (make sure you don't have any other device attached to your PC, or you could confuse the two and make bad stuff happen for that other device). If you don't see it, make sure USB Debugging is enabled. You can try to use different cables if you still have problems. Now type:

    Code:
    adb shell

    And then:

    Code:
    su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"

    KingRoot (or the app you used to root) should prompt you (in your phone) if you want to give ADB root access, make sure to allow it to make this work. This should give you your unlock code. SAVE IT INTO A TXT FILE AND COPY THAT FILE TO ALL OF YOUR PCS, ALL OF YOUR CLOUD ACCOUNTS AND ALL OF YOUR MOBILE DEVICES.

    (Maybe the terminal gets stuck at this point, press CTRL + D (or C) to get it unstuck).

    Seriusly tho, it didn't happen to me, but it is a possibility that your Bootloader can re lock after doing some of the things that follow, in which case you will need to unlock it again, and if you don't have that code... it's back to square one.

    3. GOING BACK TO ANDROID 6

    Now that we have done all that we wanted on Android 5, it's time to go back. The process is exactly the same.

    1. Extract the "UPDATE.APP" file from the "HW_Stock_Android_6.zip" file and move it to the dload folder (SD card or Internal).
    2. Turn off your phone and turn it on again with all three buttons pressed.
    3. Wait.
    4. ???
    5. Profit.

    So, we're back on Android 6. Why did we go back you may ask? Why did we not just flash our precius custom ROM? Well, for once, this gives people the chance to stay on EMUI if all they wanted was to unlock the bootloader and maybe root on Android 6 (which I will explain how to do too, in case you want to). Another, more important reason, we need Android 6 to install the B895/B896 update, which is a requirement for any custom ROM (mainly Android 7.0+) if you don't want any problems with your SIM card (and others that may arise).

    4. UNLOCKING BOOTLOADER AND FLASHING TWRP

    Now, we need to turn on USB Debugging again, and to allow our PC... again. Do so, and check that everything is right with:

    Code:
    adb devices

    If that's the case, then type the following:

    Code:
    adb reboot bootloader

    Your phone will reboot, and you should see a white screen with a wasted android above a green text saying "PHONE LOCKED". If that's the case, take a moment to say goodbye to that green text, because it will soon turn very red. We will need to unlock the bootloader with the code you got from the previous steps, for that type the following:

    Code:
    fastboot oem unlock ****************

    In place of the "****************" you must enter your code, of course. And that was it, now the green text is replaced with a red "PHONE UNLOCKED". This are good news. Now, we need to flash our custom recovery if we want to do anything fancy with the device. For that, extract the "recovery.img" file from the "TWRP_3.1.1.zip" file and paste it into the same folder where all of the ADB files are located (where "adb.exe" is). Now type:

    Code:
    fastboot flash recovery recovery.img

    This will flash TWRP into your device, hooray! Now type:

    Code:
    fastboot reboot

    And your device should turn back on, today is a bright day my son. Now you must take a decision, do you want to flash a custom ROM and get very nice and fancy features or do you want to stay with what you have? If you prefer Huawei's EMUI 4.0, then follow to the next step. If you want to flash custom ROMs, then skip the next one.

    5. ROOTING ON ANDROID 6 (OPTIONAL)

    I don't know why you would prefer EMUI over... anything else really, but it's your call. I'll tell you how to root it so you can at least take some advantage of it. You see that file called "HW_Android_6_Root.zip"? Extract it, inside there will be... another folder called Root... huh? Redundant. Anyway, inside of that there should be two zips. 1.zip and 2.zip. You will need to place the folder called "Root" inside of your SD card or your internal storage. Then, go back to the terminal and type:

    Code:
    adb reboot recovery

    You should reboot into TWRP, isn't it nice? Anyway, we have to flash some zips! Go to "wipe" first and wipe the "Cache" partition and the "Dalvik" partition. Once that's done, go to install and navigate to the Root folder your placed... well, you know where. Select 1.zip and flash it, once it's finished reboot the device. If TWRP prompts you to install it's app, DO NOT DO IT. Once the phone has rebooted (it will take longer because of the cache and dalvik wipe), repeat the process but flash 2.zip this time, reboot and your phone should be rooted. This is the end of the line for you now, as you don't want to make anything else to the phone. However, you can go to the final chapter where I explain how to install Xposed framework, if you want more customization. EMUI doesn't like Xposed very much, so there's little you can do with it, but it's something I guess.

    6. INSTALLING THE B895/B896 UPDATE

    So, you followed the power user path, the one we all really want deep down. That's cool, I respect you. We gotta use that custom recovery we just flashed, but first we need to transfer some files into our phone's memory. We need to install an update to the phone, for which you need Android 6 (that you should already have anyway). There's two different updates, B895 and B896. As you may guess, B896 is newer. However, any of these two will (or rather should) work without issues. I personally used B896, but some people claim B895 is more stable. I can't find a difference really, but the process is the same regardless of which you choose. Once you have made that decision, move "B895_update.zip" or "B896_update.zip" to your phone's internal storage or SD card AS IS (don't extract it). Then type into the terminal:

    Code:
    adb reboot recovery

    You should be in TWRP now. Go to wipe and select the "Cache" and "Dalvik" partitions ONLY, then wipe them. Once that's done, go to install and flash your update of choice. Once finished, reboot the device. If TWRP prompts you to install it's app, DO NOT DO IT. The boot should take longer than usual because of the "Cache" and "Dalvik" wipe... and because of the update too. Once booted, you should be in EMUI 4.1. Go to settings and into "About Phone". In there, look for a field called "IMEI". If you see a number, that means you did everything properly, if you see "unkown" or nothing at all, then that means you lost your IMEI... which means you will have connectivity issues. To fix this, you will need to do a full wipe (so, boot into recovery (we lost TWRP due to the update) and then go to wipe, in there select everything except SD card) and follow the steps again starting from 3, this time flashing the other update (so if you flashed B895, flash B896 this time and vice versa)).

    Now, this last step we made has wiped our custom recovery... so sad. We have to flash it again, but we are almost finished!! Now it's time for you to move the custom ROM you want to your SD card (SD card is mandatory, as we will wipe internal storage). You should also move your custom ROM of choice. If you want root, also move the "SuperSUv82.zip" file.

    OPTIONAL:

    If you want Gapps, that means the Google apps, so PlayStore, Google services and such (and you really should want them, as Android without PlayStore is kinda rough), then you need to download them separately.

    So, go to the Gapps website and select the pacakge you want. You NEED to choose the ARM64 platform, the android version depends on the ROM you are flashing, so check which version it runs, and the package itself is personal preference. Here you can see a comparison of each package, detailing what each one contains so you can make a decision. The aroma package is kinda bugged, I would avoid it. Choose wisely, as flashing another Gapps package once you have flashed a different one can and most likely will cause issues. If you want my opinion, I would stick to the nano package. It offers the basic Google functionality and allows you to download other Google apps you may need/use with the PlayStore once you are booted up.

    Once you choose your package, move it to your phone's SD card along with the ROM and the SuperSU zip if you want it.


    Check that USB Debugging is still enabled, and then type:

    Code:
    adb reboot bootloader

    Once into the bootloader, flash the custom recovery once again with:

    Code:
    fastboot flash recovery recovery.img

    Then:

    Code:
    fastboot reboot

    Once booted up again, type:

    Code:
    adb reboot recovery

    And now it's time to drop the bomb, say bye bye to EMUI, and say hello to... whatever it is you are installing.

    7. FLASHING YOUR CUSTOM ROM OF CHOICE

    MOST CUSTOM ROMS REQUIRE AN LTE CAPABLE SIM IN ORDER TO HAVE CELLULAR NETWROK WORKING CORRECTLY, THIS DEPENDS ON A ROM TO ROM BASIS, DO YOUR RESEARCH BEFORE FLASHING

    Once in TWRP, go to wipe and check every box, I'm serius, check everything except the SD card. Once that's finished, the moment of glory has come. Go to install and flash your ROM. It will take a while, and when that's done reboot. The phone should boot into your ROM. If you want either Gapps or SuperSU, make a quick setup and enable USB Debugging again, then reboot to recovery with:

    Code:
    adb reboot recovery

    Once in TWRP, go to install and flash the Gapps package and the SuperSU zip (in that order) if you want it. Reboot. That should be it! You are done!

    8. UNBRICKING

    I don't know why, but with all the flashing and the testing I've done you would have thinked that I should have suffered of a brick state at least once... that was, luckily, not the case. I haven't suffered a single brick. I don't know if I'm extremely lucky or if this phone is tremendously resilient, but the case is I haven't had any issues of this kind.

    However, I can understand that it is a possibility, so if this happens to you my best advice is to do the following: Boot into recovery mode (either stock or TWRP depending on where in the whole process you got stuck), make a full wipe and apply the update from "HW_Stock_Android_6.zip" with the dload folder and the three buttons method. That should get it unstuck, if not... try the same with the "HW_Stock_Android_5.zip" 's "UPDATE.APP".

    9. INSTALLING XPOSED FRAMEWORK (OPTIONAL)

    What? A custom ROM is not enough for you? Getting freed from EMUI is not enough? Well fear not then, because there's one last step for the true power user, for that man who thinks that everything is not enough, the good old Xposed Framework *queue fireworks and trumpets.

    So, you need to install the Xposed Installer apk. Get it from here, and ONLY THERE. I once installed an apk from another source... ended up being adware, not fun. The apk is at the very bottom of the thread. You will also need the framework itself, get it from here.

    Get the latest (arm64) version for your ROM. This depends on what Android version it is running on:

    Code:
    SDK21 = Android 5.0
    SDK22 = Android 5.1
    SDK23 = Android 6.0
    SDK24 = Android 7.0
    SDK25 = Android 7.1
    SDK26 = Android 8.0
    SDK27 = Android 8.1

    You should also get the uninstaller in case things go south.

    Once you got the files, install the apk on your phone. Open the app once. Transfer the framework and the uninstaller into your SD or internal storage. Boot into TWRP recovery and install the framework, reboot the device.

    NOTE: Android 6.0 takes about 20 mins to boot, wait about an hour before deciding that it's bricked. Android 7.1.2 took me about 2 mins. I'm unaware of the boot times of other versions, but be aware that it can take LONG. If you think it really got bricked, boot into TWRP again and flash the uninstaller. That should get it unstuck and you can either try again or leave it as is.

    ----------------------------------------------------------------------------

    Well guys, that's all I got, quite a big write up huh? I don't really have nothing else to say, just remember that what you are doing here is at your own risk and I don't want anybody blaming me for the bad things that can happen. I will proceed to leave you with the download links so you can try this yourself. I'm currently running Lineage OS 14.1 which features Android Nougat 7.1.2 on my Huawei P8 lite ALE-L23, I've never been happier to be free from the manufacturer's ROM.

    DOWNLOADS

    (The B895 and B896 update's links are not mine)

    Huawei's Stock Android 5:
    Android Filehost
    Mediafire

    Huawei's Android 5 Transition:
    Android Filehost
    Mediafire

    Huawei's Stock Android 6:
    Android Filehost
    Mediafire

    Huawei's Android 6 Root:
    Android Filehost
    Mediafire

    EMUI 4.1 (B895):
    Android Filehost

    EMUI 4.1 (B896):
    Android Filehost

    Platform-Tools:
    Android Filehost
    Mediafire

    TWRP 3.1.1:
    Android Filehost
    Mediafire

    Gapps:
    Open Gapps

    SuperSU:
    Android Filehost
    Google Drive
    2
    @tralph3 hats off to you... having written a couple of tutorials myself i can see the passion and work behind this guide.Excellent and most useful work for those few still using this device.Thanks a lot!

    Glad I could help ;) This is still my daily driver to this day. The battery is pretty busted at this point and it only stays alive for about 5 hours or less. I should buy a new one but they are expensive so I'll keep using this while I can. When I do get a new one, you can be sure I'll make a guide for it too, I love to customize my devices.
    1
    Thanks <3 -notes

    Thank you tralph3, you make my life so easy, great easy guide. I have a few suggestions for improving clarity:
    • Step 1. "Stock_Android_5.zip" contains "transitional" android 6.0 ALE-L21C900B500 firmware According to including Spanish documentation "3., 3.1 Download the Android5.0 update package" It must be downloaded another 5.0 firmware. I use this 5.0 firmware to make kingroot preform root.
      Firmware: huaweidl.com/download/p8-lite/ale-l21/b204/


    • Look for a line that says "Compilation Number" and tap...
      Step 2. second point 2. Change to "Build Number"

    • su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"
      Step 2. getting unlock code. After executing command. Add step -Kingsroot display root access prompt ALLOW it.
    t
    Thanks for your work.
    1
    okay i can give you L21C02B893 tomorrow because i don't have wifi right now and ill be going campus tomorrow

    L21C02B589 LINK: http://huawei-firmware.com/rom/huawei-p8-lite/ale-l21/2539

    damn i can't pay that much for L21C02B181 , it requires you to pay a whole package instead of the single file.

    IF i temporarily get the root like he said, how do i get the bootloader code?

    Using build L21C02B598 try to follow the step "2. ROOTING ON ANDROID 5 AND EXTRACTING BOOTLOADER UNLOCK CODE":
    https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
    1
    Thank you very much!

    Thanks to your guide and with the additional firmware-links provided by @razorfancy in post #31 (the transition pack was needed) I was able to unlock the boot loader and upgrade back to android 6 and b896. Installed twrp, then wiped everything. I wanted to install LOS 15.1 but got the error 7, so I updated twrp to a newer version without knowing what there is to consider, like checking for compatibility beforhand since I did not bother to do more research. After installing the new Version I got the lovely mesage

    Error!
    Func NO: 13 (recovery image)
    Error NO: 2 (Boot failed in recoveryboot mode)

    "adb devices" was listing nothing and when trying to flash the working twrp back with "fastboot flash recovery" it was "waiting for device". Then (after hours of reading up which I should have done before) I ran some fastboot diagnostic commands like "fastboot oem get-bootinfo" "fastboot oem get-build-number" which all gave back results corresponding to my phone. This encouraged me to try flashing the recovery again. Even though "adb devices" still did not list anything, flashing suddenly worked.
    Just thought I share this here as a warning to NOT DEVIATE from this instruction if you don't know exactly what you are doing, which I sure did not, when I started this and I consider myself having had more luck than sense and will definetly do more research before tying anything on my primary phone.

    So in the end I was able to flash the twrp version provided here back onto my phone. Now I'm running LOS 14.1

    Thanks again, and also thanks to the other active members sharing knowledge :)