Database Develop

MEGA-THREAD ALE-L21, ALE-L23, ALE-L02, Converting, Root, Unbrick, Updating, Xposed

EVERYTHING YOU NEED TO RESTORE/UPGRADE THE HUAWEI P8 LITE​So i'm making this thread because i noticed many of you had some trouble with your devices. Here you're gonna learn what you can do with your device. Every chapter is something that you can do without the need of the previous chapters (unless told otherwise). I'm also gonna explain what happens to your device (in a simple way so you don't get confused).
WARNING: THIS THREAD IS TOWARDS ALE-L21, ALE-L23, ALE-L02 USERS. IF YOUR MODELNUMBER IS ALE-L04 YOU CAN'T USE ANY OF THE FILES IN HERE.
ALSO I'M NOT RESPONSIBLE FOR SCREWING UP YOUR PHONE, Kevin is.
Note: It will work on the Ale-L02 and the Ale-L23 but you have to settle with some functions that don't work.
Comparison for the modelnumbers ALE-L21, ALE-L23 and ALE-L02​
The Chapters:
1. Tools and prepping.
2. Unlock Bootloader.
3. Bootloop/Softbrick.
4. Unbricking.
5. Dual and single sim converting.
6. Upgrading to Marshmallow.
7. Installing TWRP.
8. Getting root.
9. Install Xposed framework.
10. Multiuser account.
11. After word.
Now take your kids and lock them in your basement and put your wife in the kitchen because you're going to learn some stuff and you will get hungry.
Note: If you're a woman take your neighbours wife to make you sandwiches.
Chapter 1: Tools and prepping.
What you need:
Drivers for our phone (Hisuite).
Minimal ADB and Fastboot.
Usb debugging enabled on your phone.
How:
Download and install Hisuite on your pc
Connect your device to your pc and let hisuite detect it.
Close Hisuite.
Download and install Minimal ADB and Fastboot on you pc.
Go to "Settings -> About phone" .
Tap several times on "Buildnumber" until a toast shows where it says "you're now a developer".
Go to settings -> developer options.
And there you will see usb-debugging.
Turn it on.
Congratz on doing this.
Chapter 2: Unlock Bootloader.
WARNING THIS WILL VOID YOUR WARRANTY.
But it doesn't matter. if your phone boots and all the hardware works, everything is fine. The software is something we can fix.​
What you need:
This site.
Unlock code(you will get it on the site).
Minimal ADB and Fastboot (see chapter 1).
How:
Just go to the site.
Make a profile.
Wait 14 days.
Fill in their form .
Get a 16 digits code.
Save that code.
Connect your device to your pc.
Open a cmd.
Type this:
Code:
adb devices
It should return a permission request on your phone just accept it.
After that you should see something like this on your computer
Code:
List of devices attached
WXXXXXXXXXXXXX device
That's perfect and you're a good boy or girl or Apache Attack Helicopter.
If it doesn't you're doing it wrong. "STOP KEVIN!!! THAT'S WRONG KEVIN!!! DAMMIT KEVIN!!!"
After that type this
Code:
adb reboot bootloader
Your device will restart into a white screen with the Android puppet (wich name is Andy btw) on it. Beneath Andy it will say "PHONE locked" in green. But not for long .
Wait until Windows installs the drivers.
Remember the 16 digits you got from Huawei?
Yeah whe're gonna need them here.
Next you enter this
Code:
[COLOR="Magenta"]PINK FLUFFY UNICORNS DANCING ON[/COLOR] [COLOR="Red"]R[/COLOR][COLOR="Orange"]A[/COLOR][COLOR="Yellow"]I[/COLOR][COLOR="Green"]N[/COLOR][COLOR="Blue"]B[/COLOR][COLOR="Indigo"]O[/COLOR][COLOR="Violet"]W[/COLOR][COLOR="Red"]S[/COLOR]
No wait, that's wrong. I'm sorry.
This
Code:
fastboot oem unlock xxxxxxxxxxxxx
Where you replace the xxxxxxxxxxx with the 16 digits you got from Huawei.
Now your bootloader screen should say "PHONE unlocked" in red.To be sure you can run this command.
Code:
fastboot oem get-bootinfo
If it returns something like this.
Code:
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
Your good. And your bootloader is unlocked.
Now just reboot with this command.
Code:
fastboot reboot
Congratz, you bootloader is unlocked and your warranty just went down the drain where it shall remain for the rest of its days.
Chapter 3: Bootloop/Softbrick.
Imagine a world where everything went perfect... that would suck, would'nt it? Sometimes our device wont start. This is what we call a "Bricked" Phone. We have 2 kind of bricks. If you encounter them you will sh!t bricks.
No serious... you will!!!
If your phone is bricked we check if we can still charge it and/or try to get something on the screen. If you can't then you have what we called a hard brick and there's nothing we can do about it. "GET OVER IT KEVIN!!!"
The chances are you brokes something.
If we can then HOORA!!! The chance is great whe can restore it. This is what we call a soft brick or a bootloop (for all you smartypants out there. yeah, a bootloop is when you get stuck on your bootlogo/animation).
Chapter 4: Unbricking.
It's very simple we try to push a new image into your phone trough an unlocked bootloader with fastboot (some other devices use special methods, we don't). So make sure your bootloader is unlocked.
Here is an example
Code:
fastboot flash boot boot.img
What happens here is this:
The fastboot calls the fastboot program.
The flash says fastboot i want you to do this.
The boot says on that location on the device that is connected.
The boot.img says with that file.
So for example:
"Hey fastboot you have to flash the recovery partition with the recovery.img".
Becomes:
Code:
fastboot flash recovery recovery.img
We get these "images" with the Huawei update extractor from official updates in the form of UPDATE.APP.
Most of the times we flash 4 images and in this order.
boot.img
recovery.img
cust.img
system.img
So open your cmd in the same folder as the .img files (or put the .img files in the fastboot folder). Connect your phone trough to your pc and press power while holding the volume down button (it will show the bootloader).
And then type this.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
After that just reboot and wait. It can take a long time for the first boot. Now thankfully there are some people, who made scripts for us lazy bastards so we just have to click and be lazy.
What you need:
The unbrick files for the Dual sim.
The unbrick files for the Single sim.
How:
Connect your device in fastboot and press the "flash all" file.
Let the script run.
The first time you're gonna boot you will have no imei's so your device wil register no sim. Just update your damn phone and everything will be fine.
Note: For the people with an Ale-L04. Just replace the .img files in the folder with the files from your stock recovery.
Chapter 5: Dual and single sim converting.
So you want to convert to a single/dual sim? Well good for you.
What you need:
Unlocked bootloader (see chapter 2).
Unbrick files for Dual sim or Single sim (see chapter 4).
Vendor files for Dual sim or Single sim.
Optional:
Dual sim b170 manual update.
Single sim b133 manual update.
How:
If you want to go to dual sim just download the files for dual sim unbricking otherwise download the single sim unbricking software.
Extract them.
Run them.
And here comes the trouble.
After doing this you will notice a few things:
You will notice that none of your sim's is detected.
You will notice you can't upgrade.
And You will notice that it didn't change anything (you don't see the the appereance/dissapreance of the dual sim settings).
At this point you probaly thinking i screwed up and you want to find me, come to my house and kill me slowly in some creepy basement where i shall remain in pain for the rest of my miserable short life. Well... That's to bad for you because i'm not gonna tell you that my name and address is P sherman, 42 Wallaby Way in Sydney.
Ok, so what the F happend to your phone?
1. Your sim detection.
This occurs when you downgrade from Android Marshmallow to Android Lollipop.
It's nothing to worry about. You just lost your Imei and that's the reason your phone won't detect your sim.
It will solve itself once you update.
2. You can't update.
This is a part of the Famous Balong bug.
what happend is, the phone got confused and just spit out some random build (there's a lot more to that but this sums it up). You can detect this bug by going into "settings -> about phone" and check the build number. If you see the word "Balong" in there, congrats, you are a proud owner of the Balong bug.
How to take care of the Balong bug?
Make sure that you walk it 3 times a day.
It also does sleep a lot so don't worry about that.
Please don't be like other people wo just dump it in the woods somewhere.
Be a responsible Balong bug owner.
No seriously. If you have the Balong bug just install the vendor file according your software.
Extract the file.
You will get a folder named "dload" that contains an "UPDATE.APP" file.
Put the folder with the file in it on your sd card or internal memory.
Go to "Settings -> Update".
Press the menu (at the bottom you will see 3 lines, that's the menu).
Choose "Local update".
Select "UPDATE.APP".
Press "Install".
After the install you should be able to upgrade to a higher build. If it doesn't (single sim i had some problems). You have to upgrade manually to the next build.
Same procedure, extract -> put in "dload" folder and manually update. Make sure you delete the vendor file first.
Now you're converted and can update your phone to the latest build from Lollipop trough Updater (OTA). You will also notice that your Imei has returnd and you wil notice the appereance/dissapreance of the dual sim settings.
Chapter 6: Upgrading to Marshmallow.
The upgrade to Android 6.0 doesn't go trough OTA.
You will have to do it manually.
But first... Let your wife make you a sandwich. You should be hungry by now.
It's done? You ate well? Ok then, let's do this.
What you need:
Dual sim b560 build.
Single sim b551 build.
How:
First check that you're build is B170 or higher (dual sim) or B171 or higher (single sim).
If not upgrade first trough OTA or local update.
Extract the file.
You will get a folder named "dload" that contains an "UPDATE.APP" file.
Put the folder with the file in it on your sd card or internal memory.
Go to "Settings -> Update".
Press the menu (at the bottom you will see 3 lines, that's the menu).
Choose "Local update".
Select "UPDATE.APP".
Press "Install".
Some builds are simlocked and wont upgrade.
Just follow the Unbricking chapter and start from there.
After this you can get the next update trough OTA.
Note:Whenever you update trough OTA or local (flashing is'nt updating.) Make sure you don't have root, TWRP or another custom recovery installed. Everything should be stock.
Chapter 7: Installing TWRP.
Congratz you've made it this far. At this point whe're gonna install TWRP.
Now? you ask, What does TWRP do and what does it stand for?
TWRP stand short for Team Win Recovery Project. It's an open-source software custom recovery image for Android devices. It provides a touchscreen interface which allows users to install third-party firmware and backup the current system, which are often unsupported by stock recovery images.
Soooooooowwwww... can you just install TWRP on any device?
NO. TWRP has to be modified to your current chipset in order to work on your device. The provided image we gonna install is TWRP 3.0.2 wich is specially build for our device. Ale-L04, NOT FOR YOU GUYS!!!
What you need:
TWRP 3.0.2 with script.
Unlocked bootloader (see chapter 2).
Usb-debugging enabled (see chapter 1).
How:
Extract the folder from TWRP.
Connect your device.
Just open the Install file and read what's happening on your screen. After it's done you can boot into TWRP by holding the volume down and the volume up button at the same time while powering up your phone. The principle is the same as described in chapter bootloop/softbrick. We just flashed trough fastboot the twrp.img .
If you installed TWRP you can't update trough local or OTA anymore. You first have to flash back the original recovery. You can get them by running Huawei update extractor on your current build UPDATE.APP that you download from the Huawai site and flash them trough fastboot
Code:
fastboot flash recovery recovery.img
Note:It doesn't matter wich build you're on.
Chapter 8: Getting root.
So it has come to this. The most famous feature on Android. The almighty ROOT.
Device manufacturers don't want us to get root because the most of us would screw up the device. So if we gain root acces our warranty is void. But we can restore our warranty with unrooting. Altough if your bootloader is unlocked it's unlikely.
Not that you have anything on your warranty... like, remember that time that you took your phone out of your pocket when it rained? Yeeeeaaaaah, if you send it back they will say it's waterdamage. For warranty on your software it's simple. With root acces, TWRP and the knowledge of XDA we can probarly fix the software issue before they even realize there's an issue.
"Throw your phone against a wall, exactly at 50 M/ph that will solve the problem. Be carefull, because 49 M/ph is not fast enough and 51 M/ph will break your phone." -XDA ​
Click to expand...
Click to collapse
Please don't try this, this is not a real solution!​
So go for the root and f*ck the warranty.
Just be sure that your device boots up and all buttons work before doing anything to it.
DON'T (and i can't stress this enough!!!) ROOT YOUR PHONE WITH KINGROOT!!!​You will get root but it also screws up a lot.​
For Android 5.0/5.1 Lollipop based
What you need:
Unlocked bootloader (see chapter 2).
Usb debugging active (see chapter 1).
Root file.
How:
Connect you phone to your pc.
Extract the "root P8 file".
Open the "root P8 file".
Follow the instruction on your computer screen.
Your phone is now rooted.
Note: Unroot first with the SuperSu app before trying to upgrade to a newer build.
For Android 6.0 Marshmallow based
What you need:
Unlocked bootloader (see chapter 2).
TWRP installed (see chapter 7).
1.Zip .
2.Zip .
How:
Put 1.zip and 2.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2.zip .
Install it.
Reboot
Your phone is now rooted. But your SuperSu app is still a user app.
If you want to make it into a system app here's how to do it.
What you need:
A root explorer (Es File Explorer).
How:
Go to /data/app folder.
Locate the eu.chainfire.supersu-1 folder and cut it.
Go to the /system/app folder.
Paste it.
Give it these permissions rwx r-x r-x.
Reboot your phone.
After you got root you can delete systemapps that you don't want/need or change a lot of things in your phone.
Chapter 9: Install Xposed framework.
Xposed installer is awesome. it's like a google play store for tweaks than can make your android device just right like you wanted it to.
Note:this version won't need an build.prop edit.
What you need:
Android 6.0 installed (see chapter 6).
TWRP installed (see chapter 7).
Root (see chapter 8).
Install from unknown sources enabled.
Xposed installer.apk.
Xposed installer framework zip.
Optional :
Xposed uninstaller zip.
How:
Enable unkown sources "Settings -> Advanced Settings -> Security -> Unknown sources".
Put the Xposed installer.apk on to your device.
Install the Xposed installer.apk onto your device.
Put the Xposed installer framework zip and the Xposed uninstaller zip into your sd card/internal memory.
Reboot into TWRP.
Install Xposed installer framework zip.
Reboot.
Wait for an hour before deciding that it's bricked. Seriously this will take long like 20 minutes up to 40.
If it's bricked just boot into TWRP again and install the Xposed uninstaller zip. It should work. Otherwise -> unbrick it (see chapter unbrick).
If you have succesfully installed it go to the Xposed installer app and click on "Framework". If it says "Xposed framework version 85.10 is active" in green everything is a gogo.
Chapter 10: Multiuser account.
As you know Huawei did a heavy job theming Android with it's Emui overlay. As so we don't have all the stock features that Android gave us. Here's how to get one back.
What you need:
Root (see chapter 8).
Build prop editor.
How:
Open your build.prop editor.
Locate it to /system/build.prop.
Search for these lines.
Code:
fw.show_multiuserui=0
fw.max_users=1
Change their value into this
Code:
fw.show_multiuserui=1
fw.max_users=3
Save your build.prop (grant your editor root acces).
Reboot your phone.
Then go to "Settings".
There you will see "Users".
Chapter 11: Afterword.
If you're new on XDA remember that the people here do anything in their free time. Be it helping, developing or just testing. Be nice to them and don't spam those people. they may now alot but everything they know is already explained somewhere on XDA and explaining the same thing 1000 times a day is frustrating.
So do a search before asking anything AND READ THE WHOLE THREAD!!! We lost the only 2 developers we had in the P8 lite section this way.
Also if someone helped you press the ":good: Thanks!" button on the right bottom of his/her post. to show your appreciation. The files i enclosed are files that i gatherd over the time at the P8 lite thread or from the Huawei website. I don't remember who made them all but it wasn't me.
Give this guy a thanks @sokkoban for his awesome development on the p8-lite and his site. It learned me a lot about my device. i think most of the files are his. don't know for sure (check out his multitool here). And give this guy @shimp208 a thanks for his awesome work on the Minimal ADB and Fastboot installler and his awesome thread.
Note:for the more advanced people in here who know what they're doing. I know that there are easier ways to do some stuff but i want the people to learn. If you have suggestions, let me know.

I'm in progress of taking control over the world. So i'm not active on this thread anymore. Further questions will be answered by people like @amageek. Give them a thanx for their trouble and send amageek goats, virgins and peanutbutter (he likes that).
Also... Geeky, you will be minister of education in my new world order.

congrats for you amazing tutorial,, i have a question, imagine if my mind turns crazy and i want to lock the boootloader? how can i do?

pl4t!n said:
congrats for you amazing tutorial,, i have a question, imagine if my mind turns crazy and i want to lock the boootloader? how can i do?
Click to expand...
Click to collapse
simple
do the same steps as unlocking but just put in
Code:
fastboot oem relock YOUR CODE
it will say relock and not locked
 @pl4t!n little update

Thanks for this tutorial, hopefully this will help many.

riaanck said:
Thanks for this tutorial, hopefully this will help many.
Click to expand...
Click to collapse
I hope so to. i got tired of typing out the same solution 30 times a day now i just have to share a link

Finally
I am very happy because it sets a new developer on the horizon who can explain absolutely correctly and peaceful. Keep the good work bro!
Now moderators should delete 90% of the subjects they are unnecessary, repetitive and full of crap! It is time for this forum to begin to moderate

sokkoban said:
I am very happy because it sets a new developer on the horizon who can explain absolutely correctly and peaceful. Keep the good work bro!
Now moderators should delete 90% of the subjects they are unnecessary, repetitive and full of crap! It is time for this forum to begin to moderate
Click to expand...
Click to collapse
Thx i will do that.
yeah the moderators don't do a lot of work here. there are questions in the general. post's that are the the same... and crap like that. i will try to contact them.

lordy, many many thanks man... nice post... all in one... very much appreciated...

amageek said:
lordy, many many thanks man... nice post... all in one... very much appreciated...
Click to expand...
Click to collapse
Done with typing everything a 1000 times
it was necceserry.
gonna try to update it but...

hi, i f***** my phone with king root. and now o cant uninstall it or unroot. can help me?

Holographik said:
hi, i f***** my phone with king root. and now o cant uninstall it or unroot. can help me?
Click to expand...
Click to collapse
You can use supersu me app or delete the app with a root deleter than start with the bootloader unlocking. Yes, you probarly unlocked it with king root. No, it didn't work.
Good luck dennis, i hope u can fix it

Thumbs up!
Thanks a lot for this useful guide! Finally it's all there together in one place, with good explanations. Just used it to install TWRP and root my device, worked flawlessly!
Edit: now we just need to wait for a nice custom ROM with stock android experience, without the EMUI shell we're stuck with..

THANKS a lot dude, i removed kinguser.
now i want just to update to android 6.0
what i need to unlock/do.

Holographik said:
THANKS a lot dude, i removed kinguser.
now i want just to update to android 6.0
what i need to unlock/do.
Click to expand...
Click to collapse
Just start reading the thread. And pick in where your phone will let you.

wouterbeer said:
Thanks a lot for this useful guide! Finally it's all there together in one place, with good explanations. Just used it to install TWRP and root my device, worked flawlessly!
Edit: now we just need to wait for a nice custom ROM with stock android experience, without the EMUI shell we're stuck with..
Click to expand...
Click to collapse
Their working on it

and what i need to unlock for android 6.0? im a little stupid with huawei
or just put in dload folder the update.app or what is and flash with both buttons and power button?

Holographik said:
and what i need to unlock for android 6.0? im a little stupid with huawei
or just put in dload folder the update.app or what is and flash with both buttons and power button?
Click to expand...
Click to collapse
Chapter 6 everything is explained there. Sorry for the short answers but not much time now

Would it be possible to add some original files or just the rom in case anyone would f*ck things up.

Very good summary!

Unlock Bootloader, Convert L23 to L21 and upgrade to Android 6 Official & Custom

Huawei P8 Lite - Unlock Bootloader, Convert L23 to L21 and upgrade to Android 6 Official & Custom - (October 30, 2016).
IMPORTANT!
This tutorial describes the steps and necessary order to update the Huawei P8 Lite L23 or L21 to a newer version of Android. All in one tutorial to walk not looking separately each step is explained as much as I practice possible, if still do not achieve good for Re-Lean and try it as many times as necessary or ask if flat can not, if no then go for a beer and tacos, relax and try again later.
If you do not feel ready or deplano have not the foggiest idea of ​​what arises in this best Tutorial leave your cell like this, if you also have your phone you used to what is necessary as well leave it, dedicate to research terms you do not understand Moreover, do not try to "run without first learning to walk," you're not coming back Millionnaire, or you're going back more handsome, strong, and you will be the most intelligent or interesting, or you will become immortal only by Update your phone to Android in June , so be patient, be aware and do not hasten. At the precise moment you decide to continue with this tutorial, you become absolutely responsible for what happens to your phone and your actions. Please proceed with caution and do not play the chingon.
ODYSSEY BEGINS HERE!
UNLOCK BOOTLOADER
You can get the code to unlock the Bootloader in the following ways:
Following in the footsteps of EloyGomez Video Tutorial:
PD: Add a "w" to download.
https://ww.youtube.com/watch?v=AVmAEQjOnNQ
Following the Steps of taking screenshots and a previous orientation with EloyGomez Video:
https://plus.google.com/u/0/photos/+JohnMillerDev7/albums/6305181114976401569
Using "Huawei Product ID Generator" and following the instructions (I recommend you go copying data from a notebook and save them, you never know when you can return to need):
Download "Huawei Product ID Generator" extract it where they like and run. (It is a very simple little program).
Product Model: HUAWEI Y300-0000 (selecionan that model).
Product IMEI / MEID: "Here put your IMEI / MEID".
Product ID: "Here Product ID generates them automatically according to product model & product IMEI / MEID previously placed, and which must wear on the page"
Enter the page to Unlock Bootloader Huawei, Whether the version in English or Chinese, the only thing that changes is the language. They can try with 2 pages.
Create an account so that they can log in, they can also log in with Facebook, it is very simple.
Once you have created your account and logged in, we see the page for the unlock code.
Fill the fields with the data that we requested and put the following:
Product type: Smartphone
Product model: HUAWEI Y300-0000 (If you do not work with this, try with all models that are in the generator) (Also try with CAPITALS & lowercase).
Product Serial number: They get in Settings> About phone> Status> Serial Number.
Product IMEI: They get in Settings> About phone> Status> IMEI.
Product ID: They get the "Huawei Product ID Generator" (The program that generated them a while ago).
Captcha place the page requesting them and pressed Send or Submit, you must give the unlock code for Bootloader, copy it into the notebook (which I suppose must carry).
Now Turn to Settings> About Phone and Pulsen several times on "Compilation" until muentre them the message "now are a developer" Returning to Settings and you will see the option "Developer" tab, go there, if they are not active options because the activated developer, now a little move down and activate "USB debugging".
Download the "UNLOCK HUAWEI BOOTLOADER" extract it where they like, then connect your phone to the PC and run "UNLOCK BOOTLOADER.bat" program.
And the rest is a cinch, just follow the instructions anger us indicating the program, Drivers ADB & HiSuite (At most only have to accept the terms, click next and finish) were installed, the phone will restart a few sometimes they do not worry or despair pANIC not normal will reboot.
When they unlocked the Bootloader can disconnect your phone from the PC on and off.
Now let's check that everything went well, keep pressed "Vol-" while we connect to the PC, you will see a white screen with some letters (that's the Fastboot mode), and if they see the text "PHONE UNLOCKED" because Congratulations, Make unlocked the bootloader correctly.
Hechate a beer, a soft drink, Pau-Pau or commits a loaf to celebrate, but do not get too excited because it only been the beginning, we still some way to go, but certainly this is the most important step of all, because without having the unlocked Bootloader is not at all advisable to make root the phone, install a recovery or install a custom ROM, those using KingRoot arise after them so rare mistakes and to get them to damage the phone.
OFFICIAL FOR HUAWEI UNLOCK CODE BOOTLOADER:
https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
HUAWEI OFFICIAL VERSION IN CHINA FOR UNLOCK CODE BOOTLOADER:
PD: Add a "w" to see the website.
https://ww.emui.com/plugin.php?id=unlock&mod=detail
TOOLS YOU NEED TO DOWNLOAD:
Bootloader unlock huawei:
https://mega.nz/#!uRkC2DQS!R2IMpEpUAtrDH4-Gi4VLi8Mcz5_h98jtKsBATpMBQYg
Huawei Generator Product ID:
https://mega.nz/#!eE81BbrT!_JBTy1ZCdFuYd7JwFLnaQe06I47ua__hEa4GHx6PZvM
If the PC does not recognize them the phone even after the program to automatically install the ADB drivers, then download, extract and install these, is not all that complicated should only connect your phone to the PC.
Run programs just follow the instructions and go. May need to click on Next, Finish, "Y" or "ENTER".
https://mega.nz/#F!SZM21JKa!gE1IWif0EJH6-UwrJWQBAg
CONVERT L21 To L23
(If you reached this step means that are already Pros .... hahaha Wes is not true, it is believed!, Read on!)
At this point what we will do first is to install the TWRP Recovery and make full Wipes in order to erase the system and leave the phone in white to make a much cleaner installation without errors. So we follow the following instructions:
PD: You can install the TWRP who like V2 or V3, the procedures are the same, just change a bit the interface.
Instructions for both versions:
Download TWRP INSTALL RECOVERY (V2 or V3) P8 HUAWEI LITE.rar
Download adb-setup-1.4.3.rar
Unzip adb-setup-1.4.3.rar and run the program. (This is for adb drivers and pc can detect the terminal is installed.)
We will see a blue screen console Type "and" or "accept" in everything and close the window. If you ask them to restart the pc, do it and go.
Begin your phone in Fastboot mode; Turn off the phone and press the "VOL" key and without releasing conectenlo to the PC until Fastboot screen appears.
Unzip "INSTALL RECOVERY TWRP (V2 or V3) HUAWEI LITE.rar P8" and execute the file "INSTALL RECOVERY TWRP (V2 or V3) HUAWEI LITE.bat P8" and follow the steps.
Do not take more than 5 minutes is just a matter of going press ENTER.
Turn off the phone and Start TWRP Recovery Mode (Vol + & Power) Click on WIPE, Advanced Wipe and make full wipes:
Should be marked:
Dalvik
Cache
Data
Internal storage
System
IMPORTANT !: not marques "micro sdcard".
Return to Menu, press Reboot, and then Bootloader.
Files:
TWRP V2:
https://mega.nz/#!SZkzlQCb!iKBl1-6arjT6_9exrp9sc2aVzp7NnuKxECz6MVJ_Oms
TWRP V3:
https://mega.nz/#!CZ91RQSA!B_kl3YPn7H38nbyG-5bVk2yt6qGDSsu3A2cnGysj7u4
ADB:
https://mega.nz/#!eY1giTYD!cPs8mlBxgVP8DLHgWhCmf6Ay9hi56aTOEps55CVwiHU
After you have successfully done this, we continue to spend our L23 to L21 P8 Lite, I recommend removing your SD card and SIM Card precaution. We follow the instructions:
Downloading "FlashRom C432B052 (Lollipop 5.0, 3.1 EMUI) Dual Sim Transition" extract it where they like, Begin your phone in Fastboot mode, connect it to PC, execute the "FLASH-ALL.bat" file (not execute permissions administrator), and follow the instructions that tells the program.
You complete the process when the phone is started with the new system, if you are targeting "About phone" say "Balong". To remove that must be installed Step2.
Downloading "Step2", extract it, look for the "UPDATE.APP" file and copy it to the "DLOAD" your SD card folder if you do not have then created. (Clearly it must first insert the SD on the phone).
Then head to Settings> Updater> Menu> Update Local and selecionan the UPDATE.APP (Step2). The phone will reboot, start the installation and wait for it to finish. When you start the system and check the "About phone" no longer tell Balong but L21.
After this I recommend doing a factory reset, first remove your SD card, then go to "Settings> Security> Backup and Restore" or type in the search bar settings "Backup and Restore" click "Factory Data Reset "mark" Delete memory ", press" Reset "and wait to finish the process. If for some reason out "Failed" do not worry just restart, anyway there will reset the cel, also do not worry if you have no signal or you will not detect the SIM, that is fixed by installing the following update.
Congratulations you get past your cel L21!
Files:
FlashRom C432B052:
https://mega.nz/#!LQNimCgQ!oq2C_Gwvwv7zoigo8GR2kstPdHDO5ESJ9Qglv_2UERs
Step2:
https://mega.nz/#!vdsDEZSb!3FIgh6WNgP4NWRfnGoDxisd1wAQk3CBPKdKl8_If-v0
UPDATED ANDROID 6 Official
The update command is as follows: "B052> B170> B560> B564" or "B052> B170> B550> B560> B564"
(Compiling B560 is the most stable so far).
Being in the B052 just have to download the following Compilaciones and be updated locally via:
"B170> B560> B564" or "B170> B550> B560> B564". I recommend that for every update they make, do a factory reset to eivtar errors, this is optional in the end, I just do them the recommendation from experience.
The B170 downloaded, extract the files, copy the DLOAD UPDATE.APP folder on your SD, head to Settings> Updater> Menu> Update Local and selecionan the UPDATE.APP, the phone restarts, start the installation and wait end.
Now being in the B170, repeat the previous step to install the B550 or B560 Compilation. (Depending on the order above mentioned update, they work better or decide to take)
Now when they are on the B560 turn to the B564 but no longer appear the option "Update Local", so there are 2 options to perform the update: (and must have the UPDATE: APP previously copied to the DLOAD, the update.app always be copied to Dload no other):
Option 1:
Type the following code in the app called "* # * # 2846579 # * # *" ​​(without quotes obviously).
Appear the famous hidden menu, click "Software Upgrade"> "SDCard Upgrade"> will leave them a message "Are you Sure" (are you sure?), Pressed OK, start the update and wait for it to finish.
Option 2:
Cel being off or on, press the (Vol-, Vol +, Power) aperezca keys until the update screen and wait to finish the process.
And that would be all, Congratulations and cell habras updated to Android in June!
If you get here it means you're half Pro.
Official Roms (Installation Via Local):
PD: Add "http:" extension links to download.
B170:
//download-c.huawei.com/download/downloadCenter?downloadId=57325&version=181091&siteCode=fi
B550:
//download-c.huawei.com/download/downloadCenter?downloadId=78426&version=312720&siteCode=es
B560:
//download-c.huawei.com/download/downloadCenter?downloadId=80469&version=319382&siteCode=pl
https://mega.nz/#!uRNRDRaA!zavgQtBakqdg_lbXmgoKwB7qotPoXOJvJofvnPlM1CI
B564:
https://mega.nz/#!aAVhkbgI!1cGtLB0HxQN0x-KeyB2MqQ3JWeGEnvD2aKll7vsCa60
UPDATED CUSTOM ROM ANDROID 6
Just click on the link, read the post and go following the instructions that you indicate. Patience and Success!
PD: Add "http" "://" "w" to see the website.
[TUTORIAL] Install Android B560 & B564 6 (Dual Sim) Custom Rom V2 - Sokkoban - (Updated July 18, 2016)
ww.htcmania.com/showthread.php?t=1188059
Rom ROM Spectre - Android 6 B560 (Dual Sim) - POST UPDATED (26 AUGUST 2016)
ww.htcmania.com/showthread.php?t=1200900
Rom ROM Phenom - Android 6 B564 (Dual Sim) - POST UPDATED (26 August 2016)
ww.htcmania.com/showthread.php?t=1220243
Rom ROM Opteron - Android 6 B574 (Dual Sim) - POST UPDATED (26 AUGUST 2016)
ww.htcmania.com/showthread.php?t=1218158
Nautilus Android ROM Rom 6 B564 (Dual Sim) - October 13, 2016
ww.htcmania.com/showthread.php?t=1241126
Rom ROM Helios - 6 B890 EMUI Android 4.1 (Dual Sim) - October 25, 2016.
ww.htcmania.com/showthread.php?t=1245909
DRIVERS EXTRAS
Here I leave some Drivers Extras to troubleshoot issues fastboot, adb, if the PC does not detect the Cell, the installation of each is very simple, just keep connected your cel to the PC, run programs, you must give "next" and then restart the PC if necessary.
Files:
https://mega.nz/#F!SZM21JKa!gE1IWif0EJH6-UwrJWQBAg
And that's all I hope I have been clear and supported with this Tutorial.
Greetings from Coatzacoalcos, Veracruz, Mexico! :fingers-crossed:

Lenovo K4 Note(MM) unlocking the bootloader without loosing apps and data

Hi All,
We all know that unlocking the bootloader resets the device to factory defaults which means you loose installed apps, their settings and user data. Reconfiguring the device(system apps), installing user apps and transferring the userdata back to the phone can be lengthy process. It will also result in unnecessary usage of your wi-fi and/or mobile data and which can be quite expensive (as updated versions of user and systems app, need to be installed again)
So in order to bypass the above issues, follow the following steps:-
Step 1 - Take a full dump of your ROM using SP Flashtool's readback method. Go to readback tab, create a new item and put the following start address and length values :-
Start address would be 0x0
length of the dump file would be 0x3A3E00000 (Lenovo K4 Note only)
Start the process, it will take around one hour to complete depending on the speed of your computer. The dump would be 15 GB file, so ensure you have space.
Step 2:- Unlock the bootloader now
Firtst enable the developer option menu if not already enabled by doing the following steps
a. go to "about phone"-->"Build number"
b. tap it 7 times, you will get a message that "your are a developer now"
c. Go back to about menu, click on newly visible "developer options" and enable "OEM unlocking", ignore the warning. Scroll down and enable "usb debugging"
Open command prompt and enter fastboot mode by issuing the command
"adb reboot bootloader"
Once in the fastboot mode, issue the command "fastboot oem unlock" and follow the on screen instructions to unlock the bootlaoder
3. Now reboot the phone and configure the initial steps. As of this step user data and apps are lost, system apps are reset to factory defaults, but don't worry we have a backup (created in step one). Once done power off your device.
4. Now comes the real part. Launch SP Flash tool and create the dump of the following partitions (You create the dump file in the same manner you have created the full ROM dump file in step 1. The difference would be the values of start address and the length of individual partitions, which you can get from the scatter file).
1. Boot
2. Secro
3. Seccfg
For safety purpose i suggest to also take the backup of the following partitions
1. preloader (you can also flash preloader from stock rom)
2. lk
3. recovery (this is stock recovery with unlocked bootloader)
4. nvram
5. tee1
6. tee2
Till date I haven't has a need to use the above mentioned 6 partitions, so it's your call
Once done, power off and disconnect your phone.
5. Now enter advanced write mode in SP Flashtool (ctrl+alt+v), then open write tab from windows menu item.
Select the ROM dump file you created in step 1, put the start address as 0x0.
Once the process is started, it will take roughly an hour to complete. Disconnect the phone and reboot. Power off the phone once again.
6. Your SP Flashtool write tab is still open, if you have closed the application then relaunch the flash tool and again enable advanced write mode. Now one by one write the partitions images(dump files only boot, secro and seccfg needed) created in step 4. Use scatter file for start address.
7. Reboot your phone.
Congratulations your phone is up and running with unlocked bootloader, rooted and/or twrp custom recovery (if you chose to install it in the first place itself) and all data preserved
You can verify whether your bootloader is indeed unlocked by entering in fastboot mode and executing the command "fastboot getvar all"). You should see the values of the variables
unlocked - yes
secure - no
The first boot might take a litter longer so be patient.
Once you have an unlocked bootloader you can install custom recovery and root your phone.
I think this method should be working on any mediatek chipset based smartphones.
Note:
1. Although till date I haven't had any issues with this method, but follow the tutorial at your own discretion. I am not responsible for any damage caused to your phone by following the above mentioned procedure.
2. Sometimes while trying to perform more than one operations at a time, like you will need to perform write memory operation 3 times since unlike readback operation you can only write one image at a time in sp flashtool, you may get the following error "ERROR: S_BROM_CMD_STARTCMD_FAIL", if that is the case then try the following steps
1. Simply pull out the usb cable at the phone end, close the dialog box and try again. If not resolved after trying 2-3 then step 2
2. Restart the application and repeat the write process. If the problem is still not resolved then step 3
3. Reboot the machine, relaunch the app and repeat the write process.
I don't know why this happens but my guess is it has something to do with cpu cycles allocation causing the delay in usb signalling since SP Flash tool is a single threaded application. So for the best results try to ensure sp flashtool is the only application opened on your machine.
If you use other applications, most of the time you will get through but you will notice significant slowdown during the read and write operations especially during reading and writing full ROM dumps.
Thanks

Thank you for your effort, but I lost you in step 4, how to create dump file using SP

tamerhaikal said:
Thank you for your effort, but I lost you in step 4, how to create dump file using SP
Click to expand...
Click to collapse
Hi,
You create the dump file in the same manner you have created the full ROM dump file in step 1. The difference would be the values of start address and the length of individual partitions, which you can get from the scatter file.
You can add multiple entries in the readback tab.
Hope this helps. Let me know if you have any trouble.
Thanks.
Sent from my Lenovo A7010a48 using XDA-Developers mobile app

Honor 9 Lite "how i repair MY bootloop"

Just for Info
I am brick MY phone, what have i done ?
On all my phones is first doing: bootloader unlock, install twrp and rooting.
1 - i login by huawei, fill the form and return my unlock-code
2 - search twrp ( i am found ; but it was the wrong one. [i think i need new eyes])
3 - on phone : menu / 7x tip on build activate developer options / go to developer options / enable oem-unlock and enable usb-debugging
4 - usb-wire in phone and pc, on pc (linux) start terminal (the same as windows dos-prompt), type "adb devices", on phone-screen "access for develop" hook & ok
5 - adb reboot bootloader
6 - fastboot devices (connection test)
5 - fastboot flash recovery_ramdisk twrp.img
6 - fastboot reboot
7 - phone reboot in twrp (not OS)
from now, what ever i do, phone boot only in twrp BOOTLOOP
now i am search in XDA and AH (german community AndroidHilfe) "honor 9 lite bootloop" NOTHING
by random found on AH "Huawei P smart [How to Root] + TWRP - Root - Anleitung". Huawei P smart is sister from Honor 9 Lite (very helpful thread-writer on AH)
ho help : at this moment no downloads at huawei/honor 9 lite (for help i need "update.app") now i wait...
2 days later (wait is not my strength) i found FHMate10Tool. users write "this can work/cant work - test it.
i test it. on windows-pc open explorer, go to folder, right-click on FHMate10Tool.exe, "run as admin", dos-prompt open and write text from tool
usb-wire in pc and phone (phone is on)
point 1 in tool: "root phone" ; i write "1" and press enter
tool write "this rooting phone: for yes press enter", i press enter, 4..5 seconds later write tool "your phone is rootet and rebooting"
phone reboot and boot i customOS - WOH :laugh: phone configure, apps install and phone working (always inside the wrong twrp)
5 days later phone write"new update anailable! install?" "yes" and ota-update download (i think 1 hour) and write "update now" "yes"
update go to factory-update-mode (erecovery?) begins and brake by 25%, "what a hell !!!", i reboot
now the best idea from my life. i copy with es-explorer(root) from /data/update/Hwouc/... the "update.app" to my sd-card.
my phone have build 8.0.0.121, the update.app is LLD-L31 8.0.0.127(C432)FULL. This is important, the little updates not inside "system, recovery". the FULL is what i need.
start HuaweiUpdateExtractor, select update.app, settings "all hook out", extract "recovery_ramdis.img" and "system.img" (automatic extract the header-files)
now copy this 4 files to my adb-folder, phone in bootloader-mode, usb-wire pc to phone
open dos-promt, cd.. to adb-folder, check connection with "fastboot devices", connection work and the fun begins
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
NOW is custom recovery and system on phone
to clear userdata
- fastboot erase userdata (this make what you reed: ERASE)
- now boot to erecovery (usb-wire in pc and phone, vol-up and power press on phone) and make factory reset. this make low-level-format with userdata.
- reboot and phone is clean and fresh as a new phone. no twrp, no rootet. if i wish (yes) i can fresh install
only restriction at this time: twrp is beta! no full work, backup/restore system = work, backup/restore data = NOT work.
supplement
this work on my phone! on your phone? test at your owen risk
bevor twrp has full-function: attention to this point. no data-backup. everyone brake phone: you begins by zero /better begins zero else phone ded
experience
i search for LOS15.1 or RR, for this phone nothing found. i test system.img(oreo!) from other models (my risk, my phone, my fun). i test to now 5x, next test in 5 minutes
now nothing run on my phone. flash *.img, no boot to OS, the game starts from the beginning
- inserted 20180325 13:05 test not work, return to customOS
- inserted 20180325 13:40 systemOS work, SuperSU is from old install! ALL GOOD :good:
bootloader is open if: PHONE Unlocked & FRP Unlock
I hope this is helpful for your bootloop :angel:
{
"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"
}

@JamesBott flash this RR.. it will work in Honor 9 Lite..
https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688

@VigneshS007
thank's for your help. i test rom in next 2..3 hour. then i see is work/no work...
i think, i open new threat > "Honor 9 Lite "my test's with other rom's" <
i am german, i need "order"
if i search "bootloop" i wish find bootloop and anwer for this theme in 1 thread
what is the bootlop answer is in "new rom" ? and i don't find this thread ? that's NO good
all other nations : this is "german thinking" (for you is "can" / not "must" !!!)
is the same as comedy "you can laugh, but you do not have to" <- it's a joke
here is not the place for principle disputes, it's only my thinking and i hope you understand me
my english is only "learning by writing" and google-translating
i am now installed Telegram and look in this group
i have to tell you, i think that's a pity
xda is the world-community for android and all world-user. any user search for question's and answer's and this in xda.
i wish, the tegram-group come in to xda and all user (world) find these inside xda (my thinking !)
why: look in this forum. i feel "this is my forum" . i wish other write also here (ROMs...Development)
or is it to early ? the phone is to young / to short on market ?
How is the developer to make twrp with 100% working ? for this phone ! i donate with 20€ ! honestly! (i hope, this is incentive enough)

sorry, duplicate from #3

@VigneshS007
hi brother, please look
https://forum.xda-developers.com/9-...r-9-lite-test-devices-developer-roms-t3768950

Bootloop again
JamesBott said:
Just for Info
I am brick MY phone, what have i done ?
On all my phones is first doing: bootloader unlock, install twrp and rooting.
1 - i login by huawei, fill the form and return my unlock-code
2 - search twrp ( i am found ; but it was the wrong one. [i think i need new eyes])
3 - on phone : menu / 7x tip on build activate developer options / go to developer options / enable oem-unlock and enable usb-debugging
4 - usb-wire in phone and pc, on pc (linux) start terminal (the same as windows dos-prompt), type "adb devices", on phone-screen "access for develop" hook & ok
5 - adb reboot bootloader
6 - fastboot devices (connection test)
5 - fastboot flash recovery_ramdisk twrp.img
6 - fastboot reboot
7 - phone reboot in twrp (not OS)
from now, what ever i do, phone boot only in twrp BOOTLOOP
now i am search in XDA and AH (german community AndroidHilfe) "honor 9 lite bootloop" NOTHING
by random found on AH "Huawei P smart [How to Root] + TWRP - Root - Anleitung". Huawei P smart is sister from Honor 9 Lite (very helpful thread-writer on AH)
ho help : at this moment no downloads at huawei/honor 9 lite (for help i need "update.app") now i wait...
2 days later (wait is not my strength) i found FHMate10Tool. users write "this can work/cant work - test it.
i test it. on windows-pc open explorer, go to folder, right-click on FHMate10Tool.exe, "run as admin", dos-prompt open and write text from tool
usb-wire in pc and phone (phone is on)
point 1 in tool: "root phone" ; i write "1" and press enter
tool write "this rooting phone: for yes press enter", i press enter, 4..5 seconds later write tool "your phone is rootet and rebooting"
phone reboot and boot i customOS - WOH :laugh: phone configure, apps install and phone working (always inside the wrong twrp)
5 days later phone write"new update anailable! install?" "yes" and ota-update download (i think 1 hour) and write "update now" "yes"
update go to factory-update-mode (erecovery?) begins and brake by 25%, "what a hell !!!", i reboot
now the best idea from my life. i copy with es-explorer(root) from /data/update/Hwouc/... the "update.app" to my sd-card.
my phone have build 8.0.0.121, the update.app is LLD-L31 8.0.0.127(C432)FULL. This is important, the little updates not inside "system, recovery". the FULL is what i need.
start HuaweiUpdateExtractor, select update.app, settings "all hook out", extract "recovery_ramdis.img" and "system.img" (automatic extract the header-files)
now copy this 4 files to my adb-folder, phone in bootloader-mode, usb-wire pc to phone
open dos-promt, cd.. to adb-folder, check connection with "fastboot devices", connection work and the fun begins
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
NOW is custom recovery and system on phone
to clear userdata
- fastboot erase userdata (this make what you reed: ERASE)
- now boot to erecovery (usb-wire in pc and phone, vol-up and power press on phone) and make factory reset. this make low-level-format with userdata.
- reboot and phone is clean and fresh as a new phone. no twrp, no rootet. if i wish (yes) i can fresh install
only restriction at this time: twrp is beta! no full work, backup/restore system = work, backup/restore data = NOT work.
supplement
this work on my phone! on your phone? test at your owen risk
bevor twrp has full-function: attention to this point. no data-backup. everyone brake phone: you begins by zero /better begins zero else phone ded
experience
i search for LOS15.1 or RR, for this phone nothing found. i test system.img(oreo!) from other models (my risk, my phone, my fun). i test to now 5x, next test in 5 minutes
now nothing run on my phone. flash *.img, no boot to OS, the game starts from the beginning
- inserted 20180325 13:05 test not work, return to customOS
- inserted 20180325 13:40 systemOS work, SuperSU is from old install! ALL GOOD :good:
bootloader is open if: PHONE Unlocked & FRP Unlock
I hope this is helpful for your bootloop :angel:
View attachment 4457135
Click to expand...
Click to collapse
I have to apply the procedure point by point unfortunately the factory reset of the erecovery remains blocking to zero, and I remain in bootloop. . . Do you have a backup stock flashable rom with twrp? OR ANOTHER SOLUTION? THANKS

i have finally twrp reflash and i made a factory reset with twrp ... normal boot result and everything works ... i have the possibility thereafter of reflashed erecovery stock ... but not useful for me for the moment ... how is it that my firmware number does not match your file? I am in b128 and your update full file is in b127?

@angixspirit
my last FULL-Update is "b127".
Now is TWRP with de-/encrypt in short time available (i am test beta-version)
I wish reset my "data" to factory-settings(crypt)
I use recovery_ramdisk_BKL-L04_nocheck (thank's @Atarii) for install my FULL-Update
After this reboot my phone, FULL-Update is installed AND "data" is crypted (factory-state)
Now work twrp (new twrp in test-version !) WITH de-/encryption.
I hope in next days comming new thread from developer in this forum.
The new TWRP is in standard-look and -feeling and -language.
Over night came update "b128"
The way with recovery_ramdisk_BKL-L04_nocheck (thank's @Atarii) have advantage
- the complete stock-rom is reflashed (with all partitions inside update)
- erecovery work (by me)
disadvantage
- the huawei-bloatware now again delete

Where to find this recovery?recovery_ramdisk_BKL-L04_nocheck?
---------- Post added at 04:11 PM ---------- Previous post was at 03:36 PM ----------
angixspirit said:
i have finally twrp reflash and i made a factory reset with twrp ... normal boot result and everything works ... i have the possibility thereafter of reflashed erecovery stock ... but not useful for me for the moment ... how is it that my firmware number does not match your file? I am in b128 and your update full file is in b127?
Click to expand...
Click to collapse
But I used your update full b127 and when such starts I'm in b128 (update at startup age maybe?)

https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085
your firmware
i think, your build is b128. if you update to b127 = downgrade. i dont know if this work in stock-rom.
Search
you see on xda-side in browser on top / right the "search-field" ?
Search-Field = "Type device or find apps, ROMs, & more"
this search in xda and is faster as search in google
Your personal task : search in xda "Huawei Firmware Finder" and look for thread.
If you found the thread then download the Software to your PC, install and search in FirmwareFinder "FULL-Upate" for your phone.
I am found LLD-L31 8.0.0.131(C432). This is actual the last build for download.
I'm curious if you think so
If you found : you can see, what TeamMT offer on Firmware for your phone.

Nice
I repeat the procedure with your ram file erecovery disk ... Same result impossible to make factory reset, and Huawei tells me that the tel is rooted and I am in b128 ... I have yet made a wipe of the storage system intern etc with twrp before, and. I used your full update b127 for fastboot ...
So here after installation I used firmware finder I chose the firmware b127 full I used the proxy for download internally .. And here my system asks me the official update to b127 ... No problem the system comes back with the bloatware in erecovery the factory reset works fine ... And since update removed to b128 b130 ... ?
Strongly the new twrp that I continue my experimentation
Ps Ps I just saw your message on update finder .. I know all this thank you very much

Huawei LLD-AL10
Phone Relocked
FRP Lock
any fix

Zunayedazad said:
Huawei LLD-AL10
Phone Relocked
FRP Lock
any fix
Click to expand...
Click to collapse
https://forum.xda-developers.com/9-lite/how-to/guide-unlock-frp-phone-bootlooping-t3808650
Tell me your C-Number to find the correct firmware to flash.
Sent from my kminiltexx using XDA Labs

How To Guide (Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet

Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Warning
As stated by @beatbreakee , do not flash anything on a T-Mobile related device.
Please read beatbreakee's comment regarding this.
Warning
This has only been tested on Android 13. This guide may not work for other Android versions.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Android 13
Spoiler: Step 1 - Unlocking Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"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"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Spoiler: Step 2 - Flashing TWRP
Step 2 - Flashing TWRP:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
This is not a bootable image. You must flash. fastboot boot img will not work
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.img
Code:
fastboot flash recovery_b twrp.img
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Spoiler: Step 3 - Flashing Magisk
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
5. Tap System
You should now enter the device
3.C - Installing Magisk APK
Install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Spoiler: Fixing Data Backup [Optional]
If you encounter a createTarFork() exited with error 255, do the following:
1. Reboot into TWRP
2. Select File Manager
3. Navigate to /data
4. Copy /data/fonts into /sdcard/
5. Copy /data/nandswap into /sdcard/
6. Delete /data/fonts
7. Delete /data/nandswap
The error should now be resolved
The deleted files should not cause any issues. If any issues do occur, then promptly restore them using the backups made to /sdcard/.
Spoiler: Bypassing Safetynet [Optional]
Step - Bypassing Safetynet:
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
F - Test Safetynet
1. Install YASNAC
2. Grant Super User rights
3. Select "Run Safetynet Attestation"
If both checks pass, you successfully have passed Safetynet!

PlasmaTornado said:
Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings -> About -> Tap on Build Number 7 times
2. Open Developer Settings
3. Enable OEM Unlocking
4. Enable Android Debugging Bridge (ADB)
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
View attachment 5792895
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot oem unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Then finally:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Step 2 - Flashing TWRP Image:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
! It is HIGHLY recommended that you boot into the twrp.img before flashing to ensure that TWRPworks . I did not, but I recommend you do. !
To test this, enter the following command:
Code:
fastboot boot twrp.img
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.image
Code:
fastboot flash recovery_b twrp.image
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
You should now enter the device
3.C - Installing Magisk APK
If for some reason the Magisk Installer did not install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Click to expand...
Click to collapse
Good post but one problem...to unlock is " fastboot flashing unlock"

Canuck Knarf said:
Good post but one problem...to unlock is " fastboot flashing unlock"
Click to expand...
Click to collapse
Of course! Thank you, used to the old way of unlocking

I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?

kouzelnik3 said:
I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?
Click to expand...
Click to collapse
Following the method created by @dladz should still work perfectly fine!
There could still be issues with this TWRP as this is not an official image.
AFAIK Switching ROM is still untested, but decryption, backups and flashing are all confirmed working, which for me makes me feel significantly more comfortable

I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!

kouzelnik3 said:
I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!
Click to expand...
Click to collapse
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!

PlasmaTornado said:
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!
Click to expand...
Click to collapse
I will try factory wipe...flash flash from 2213...to 2215...might work

Canuck Knarf said:
I will try factory wipe...flash flash from 2213...to 2215...might work
Click to expand...
Click to collapse
Fantastic news. Let us know the results!

i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. AND my 10T and 10 Pro BOTH have been fully bricked, then formatted and flashed thru an authorized MSM Account.... Doing an ERASE ENTIRE FILE SYSTEM, thru msm, did not get rid of this file, so i doubt a twrp level wipe will do it either... MAYBE an "unlock Critical" in Fastboot, followed by a "Fastboot wipe", "DM-verity disable", and "VB-Meta erasure" MIGHT take out this crazy security system, but i know this .... if you flash an original FW using TWRP, it has protections in it to keep IT (twrp) from being overwritten, so you might find yourself in bootloop territory if you region hop.... cuz the fw might notice the changes to the partitions... For now, until someone is brave enough to challenge the Android 12 kernel and remove these trapdoors, I would just be happy you have TWRP, and wait for the person who finds and slays the Tmobile Dragon hidden in our phones! But this is truly an android 12 function that was put in place for Carrier and Manufacturer benefit ONLY. Another strike against 1+

beatbreakee said:
i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. So this is truly an android 12 function that was put in place for Carrier benefit ONLY. Another strike against 1+
Click to expand...
Click to collapse
Absolutely despicable and such an anti-consumer technique.
This stands against everything OnePlus was. It's sad to see OnePlus turn into such an anti-developer phone
A Carrier should never have this much power over a device. It is absurd

heres a google drive link to my account if anyone wants to see a video of what you will go thru if triggered!
feel free to share or re-upload the link/video to anywhere... ppl need to know this is happening thanks to Tmobile and Oneplus collaboration. I have not seen any reference to another carrier inside any of the device policy files, and my phone was restored to a NON TMO branded build of android 12 for the 2217 NA model, so it should NOT have even recognized the TMO policies cuz i even used a new sim card after the MSM Unbrick, and it still instantly locked in less than a second of plugging it in... heres the vid
https://drive.google.com/file/d/17H6YpGrUCe1Y7PoFji4gperdpTHNX5AI/view?usp=sharing

also everyone should know, that EVERY fw on the internet no matter whether it is labeled, 2213, or 2215... 2217, as well as 2413-2419 ALL have EVERY other model's manifest built in and all of the restrictions / bloatware that each region comes with, saved into the OFP extracted files.... so there really is nothing that expressly was bricking your phones by simply flashing a different labeled FW..... the brick came from the manifest reading the region identifiers that the manifests are labeled under.... it is a file that is again picked by some random hidden check inside the TMO EFS, and as soon as your phone tries to boot the newly flashed FW, the TMO Lock is what bricks your phone, to either a bootloop state, or if you continue to force a flash by using Fastboot , you will have a non responsive phone, thanks to this stupid security issue. If unresponsive, the only way out is MSM Tool... and i can help you locate your test points if your buttons dont work.
I cannot publicly post a picture nor a description of where the test points lie inside the 10T , because i already got a cease and desist letter from BBK and i dont know if they have said anything to the mods here about posting Undisclosed hardware access points.... but ive been a member here almost 10 years, and i aint risking a ban from a tattle tale company! There are test points on the 10 t though,.. just well hidden!
The 2nd pic is of the 2217 Unpacked OFP , yet the build prop shows a 2210-2211 base in one and a 2413-2415 base in the.... with NO 2217 in either prop,or manifest file, yet when my phone was flashed back from Brick status, THIS is the FW that was used, and my phone identifies as a 2217 NA now..... can oneplus be any more clear that they have completely turned against us, by straight SHOWING US that they are being super cryptic and sneaky in something as common as the BUILD.PROP files?!?

The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?

kouzelnik3 said:
The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?
Click to expand...
Click to collapse
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )

Canuck Knarf said:
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )
Click to expand...
Click to collapse
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.

kouzelnik3 said:
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.
Click to expand...
Click to collapse
Yeah i hear you but I'm not sure if this a bootable version or a just install version....I will try it on mine to see if i get the same as you

Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works

Canuck Knarf said:
Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works
Click to expand...
Click to collapse
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?

kouzelnik3 said:
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?
Click to expand...
Click to collapse
It appears the image is not bootable. As stated, this is the one thing I didn't try.
I have amended the guide. Thank you