Database Develop

[Q] Huawei p7 Bootloop

A couple of days ago my Huawei p7 started to shut itself down and after that it keeps rebooting.
It starts itself up and I get into the choose your language screen and then it shuts down.
When i try to get into the system recovery (using volume & power) I get the following screen:
Android system recovery <3e>
Huawei software installed failed.
Please retry!
Shutdown system now
There is no UPDATE.APP
.............................................
FAIL
And even in system recovery it keeps rebooting.
Im kinda helpless at the moment not knowing what to do.
Did this occur to anyone ? Is there a solution for this problem ?
Thanks in advance.

You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??

wekii said:
You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??
Click to expand...
Click to collapse
I've downloaded the update file and proceeded with your steps. I continued to trigger the firmware update with the factory reset.
At first it seemed to work, the phone started updating but after a couple of seconds it started to reboot itself again
I got the phone in fastboot mode and at this moment it does not restart itself !
I went on downloading Hisuite and at this moment it keeps searching for drivers on the network.
The searching for drivers is taking quite some time is this normal ?
Thank you very much for your help so far !

OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked. If it's not you need to enter the next command "fastboot oem unlock 1234567812345678", where "1234567812345678" should be replaced with unlock code that is unique for your device. Instructions which explain how to obtain unlock code for your device can be found here,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.

wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
Hi,
I've got the same issue.
When I start to "force install" method, my phone doesn't boot.
It just stay in a state of "charging" but nothing append.
I flashed boot and recovery with Fastboot.
But now, when I start the phone in Fastboot&Rescue Mode, the device doesn't appear in the liste when I run adb devices.
But when I start in the "force install" mode, adb devices returns the serial of the phone (but it doesn't respond to fastboot command).
Are there other files to flash on the phone than juste recovery and boot ?
Thank's for those steps, i'll continue to try to flash again.
Edit :
Ok phone is back !
The problem came from my SD Card, I had not only the dload folder, but an other file.
Format SD Card -> dload folder -> "force install" method -> ENJOY !
Thank's a lot !

wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
I followed all your steps but i get stuck at step 7. When I give the command fastboot devices it doesn't show my phone's serial number. Instead it shows a ? (question mark).
Did I do something wrong or is there a solution for this?
Thanks in advance!

Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!

wekii said:
Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!
Click to expand...
Click to collapse
Thanks for your response !
So I followed through like you said. Gave the fastboot oem get-bootinfo command and then I got (bootloader) locked. So I followed the bootloader's unlock code (official way), entered my product SN and product IMEI, used the Huawei Product ID generator followed the procedure and all I get is : Please input the correct Product ID
What did I do wrong this time ? I'm not sure if it's even possible to do this wrong. Is there another way around ?

You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app

Pboguet said:
You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
I've downloaded Vroot (english version) but when i connect my phone it says not support mode
I tried to connect while in fastboot&rescue mode, because this is the only way the phone stays on without restarting.
I then tried to connect without fastboot&rescue mode. But my phone keeps rebooting. I did get a message that USB debugging is disabled. However I can't enable usb debugging because my phone won't boot up normally.

@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
 @zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.

wekii said:
@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
@zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.
Click to expand...
Click to collapse
Thank you very much for all your help!
Despite following all your steps my phone keeps rebooting

Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.

wekii said:
Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.
Click to expand...
Click to collapse
Ik
After unlocking my phone I got the message unlocked in CMD.
I then flashed recovery and boot. Both times it said that the flash was succesfull, this only took a few seconds I don't know if thats normal? I then followed your last steps ( dload folder etc) and put the SD card in my phone.
It start installing but after approximetaly 25 seconds the phone shuts itself down and then reboots.
The procedure then starts again and it starts installing followed by shutting down and rebooting.

I'm sorry to hear that. Seems like it's some hardware issue.
However I still have one more idea that you can try in fastboot mode. I would recommend you to install entire firmware manually with fastboot commands.
By following previously described procedure try to extract with "Huawei Extractor" tool next images also: SYSTEM, USERDATA, CUST and CACHE.
After step number 10, try to use next commands also:
"fastboot flash system system.img"
"fastboot flash cust cust.img"
"fastboot flash userdata userdata.img"
"fastboot flash cache cache.img"
When you are finished with flashing of all images, use "fastboot reboot" command to restart your phone. Steps 11, 12 and 13 should be ignored this time.
Let me know the result

Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122​- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method​- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought​- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked​- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection​- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again​- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)​
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...

mbert said:
Hey,
Only TWRP 2.7.1.0 does not reboot.
Thanks in advance...
Click to expand...
Click to collapse
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.

Ziółek said:
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.
Click to expand...
Click to collapse
failed
I tried se7en and miui.
I wiped dalvik,system,data,internal,cache and custom, which only lasted about 2 seconds, but said succesful (Is that enough to delete all partitions?).
Installation of both custom roms completed succesfully and lastet several seconds (max 1 min I think).
Se7en: reboot -> huawei logo -> reboot -> language selection (in the style of stock rom?) -> reboot ...
Miui: reboot -> miui logo -> reboot -> language selection (miui style) -> reboot -> wifi selection (I skipped) -> searching for sim card -> reboot

mbert said:
Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122​- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method​- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought​- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked​- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection​- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again​- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)​
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...
Click to expand...
Click to collapse
To use fastboot you need to unlock bootloader first. And before flash, you need to erase partition first, for a proper job. Please read well about the fastboot procedure is a dangerous procedure

My bootloader is unlocked, but fastboot sais I don't have permission to erase partitions ...
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk

[GUIDE] Downgrade Zenfone 2 Laser to any official firmware

I have discovered multiple ways of downgrading ZenFone 2 Laser out of which two methods proved out to be easy and reliable. Both methods have been tested and are working.
Method 2 doesn't require root while method 1 needs root access.
Pre-requisite: Stock firmware zip file. You can find download links from index thread for all variants.
WHILE THIS GUIDE HAS VERY LESS CHANCES OF MESSING UP YOUR DEVICE, HUMAN ERROR CAN ANYWAY HARM THE DEVICE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO ANY DEVICE. YOU ARE DOING THIS AT YOUR OWN RISK
METHOD 1: Requires ROOT-
Short instruction:
Some users say you can downgrade by renaming the OTA zip to correspond to a higher version but that will NEVER work because the update script has this line
(!less_than_int(1457089250, getprop("ro.build.date.utc"))) || abort("Can't install this package (Fri Mar 4 19:00:50 CST 2016) over newer build (" + getprop("ro.build.date") + ").");
Click to expand...
Click to collapse
The recovery reads ro.buid.date.utc value from buid.prop. If the value is less than the value in updater-script (like the value highligted in above quote) any recovery will not flash it, neither stock nor custom. Just increaase the value of ro.build.date.utc (in build.prop) to any value higher than the value in updater-script and then flash the zip via recovery.
Detailed Instructions:
1. Open updater-script from the firmware zip. It will be found in /META-INF/com/google/android inside the .zip
2. look at the first line (!less_than_int(1457089250, getprop("ro.bui....
3. The value 1457089250 is taken as an example, your updater-script may have a different value. Keep a note of this value.
4. Install any root file manager like ES file explorer (if you dont have already)
5. Goto /system (the system folder) using the root file manager. Grant root access if prompted
6. Open buid.prop file as text and look for the line "ro.build.date.utc=1446585430"
1446585430 is taken as example, your phone will have a different value.
7. Now increase this value in build.prop to any number greater than the value you noted from updater-script
for example, if my updater-script has 1457089250 this value and buil.prop has 1446585430 this value, I will simply change the value in build.prop to 1546585430 or 1448585430 or 1457089251. Any number greater than 1457089250 will work in my case.
8. Now reboot to recovery (vol down + power)
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Method 2: Without root, requires computer
Short instructions:
As I mentioned earlier, recovery reads "ro.build.date.utc" But you can bypass this check by erasing system partition.
Just do
Code:
fastboot erase system
from fastboot mode and then flash the zip from recovery
Detailed Instructions:
1. Install Asus drivers to your computer. (link in index thread)
2. Download adb_fastboot.zip and extract its contents
3. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold "volume down Up" button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
4. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
5. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
6. On command prompt type
Code:
fastboot devices
and hit enter
and check if it is detecting your device.
7. Then type
Code:
fastboot erase system
(this will erase your current OS, you are warned!)
8. After it is done type
Code:
fastboot oem reboot-recovery
to boot into recovery mode
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.

Successfully downgraded to 1.16.40.763 from 1.17.40.1234 without root
Thanks!

sziraqui said:
I have discovered multiple ways of downgrading ZenFone 2 Laser out of which two methods proved out to be easy and reliable. Both methods have been tested and are working.
Method 2 doesn't require root while method 1 needs root access.
Pre-requisite: Stock firmware zip file. You can find download links from index thread for all variants.
WHILE THIS GUIDE HAS VERY LESS CHANCES OF MESSING UP YOUR DEVICE, HUMAN ERROR CAN ANYWAY HARM THE DEVICE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO ANY DEVICE. YOU ARE DOING THIS AT YOUR OWN RISK
METHOD 1: Requires ROOT-
Short instruction:
Some users say you can downgrade by renaming the OTA zip to correspond to a higher version but that will NEVER work because the update script has this line
The recovery reads ro.buid.date.utc value from buid.prop. If the value is less than the value in updater-script (like the value highligted in above quote) any recovery will not flash it, neither stock nor custom. Just increaase the value of ro.build.date.utc (in build.prop) to any value higher than the value in updater-script and then flash the zip via recovery.
Detailed Instructions:
1. Open updater-script from the firmware zip. It will be found in /META-INF/com/google/android inside the .zip
2. look at the first line (!less_than_int(1457089250, getprop("ro.bui....
3. The value 1457089250 is taken as an example, your updater-script may have a different value. Keep a note of this value.
4. Install any root file manager like ES file explorer (if you dont have already)
5. Goto /system (the system folder) using the root file manager. Grant root access if prompted
6. Open buid.prop file as text and look for the line "ro.build.date.utc=1446585430"
1446585430 is taken as example, your phone will have a different value.
7. Now increase this value in build.prop to any number greater than the value you noted from updater-script
for example, if my updater-script has 1457089250 this value and buil.prop has 1446585430 this value, I will simply change the value in build.prop to 1546585430 or 1448585430 or 1457089251. Any number greater than 1457089250 will work in my case.
8. Now reboot to recovery (vol down + power)
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Method 2: Without root, requires computer
Short instructions:
As I mentioned earlier, recovery reads "ro.build.date.utc" But you can bypass this check by erasing system partition.
Just do
Code:
fastboot erase system
from fastboot mode and then flash the zip from recovery
Detailed Instructions:
1. Install Asus drivers to your computer. (link in index thread)
2. Download adb_fastboot.zip and extract its contents
3. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
4. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
5. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
6. On command prompt type
Code:
fastboot devices
and hit enter
and check if it is detecting your device.
7. Then type
Code:
fastboot erase system
(this will erase your current OS, you are warned!)
8. After it is done type
Code:
fastboot oem reboot-recovery
to boot into recovery mode
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Click to expand...
Click to collapse
Currently iam on marshmallow. My phone is zenfone laser 550kl. Iam having some problems with the marshmallow recovery because of that when doing apply update from sd card it is resulting an error.
Failed to mount/asdf.
So i like to flash the lolipop recovery while iam on the marshmallow and then do apply update from sd card. I like to go back to the 1.13 lolipop firmware
Is it possible to to flash the lolipop recovery while iam on marshmallow. If possible. Help me how to do that

ThanveerAliSayed said:
Currently iam on marshmallow. My phone is zenfone laser 550kl. Iam having some problems with the marshmallow recovery because of that when doing apply update from sd card it is resulting an error.
Failed to mount/asdf.
So i like to flash the lolipop recovery while iam on the marshmallow and then do apply update from sd card. I like to go back to the 1.13 lolipop firmware
Is it possible to to flash the lolipop recovery while iam on marshmallow. If possible. Help me how to do that
Click to expand...
Click to collapse
"Failed to mount /asdf" error is harmless you will get that error even on latest twrp. You can ignore the error and use the MM stock recovery like normal. Recovery will do its job it can format, install updates, clear cache and everything, you just need to ignore that /asdf error
But you can use any stock recovery from any firmware version lower than or equal to your current firmware version. Drawbacks: You cannot apply update to MM OTAs if your recovery version doesn't match the current firmware version.
Going back to stock 1.13 is a bad idea. I would recommend you to stay on MM since it has many performance improvements.
But still if you want to go back to lollipop, consider downgrading to the last lollipop update i.e. v1.17.40.1531
Xda Tips: 1. Never quote the entire OP (the main post here, called original post)
2. Don't say thanks, instead hit the :good: button
3. Use "Post Reply" option on top if you want to reply to a post. Use @username to gain attention of a user

sziraqui said:
"Failed to mount /asdf" error is harmless you will get that error even on latest twrp. You can ignore the error and use the MM stock recovery like normal. Recovery will do its job it can format, install updates, clear cache and everything, you just need to ignore that /asdf error
But you can use any stock recovery from any firmware version lower than or equal to your current firmware version. Drawbacks: You cannot apply update to MM OTAs if your recovery version doesn't match the current firmware version.
Going back to stock 1.13 is a bad idea. I would recommend you to stay on MM since it has many performance improvements.
But still if you want to go back to lollipop, consider downgrading to the last lollipop update i.e. v1.17.40.1531
Xda Tips: 1. Never quote the entire OP (the main post here, called original post)
2. Don't say thanks, instead hit the :good: button
3. Use "Post Reply" option on top if you want to reply to a post. Use @username to gain attention of a user
Click to expand...
Click to collapse
I got a 412 mb ota update some days before. I downloaded it. Apply it for proceed. Then it start checking system as usual phone restarted. But update did not happened. Instead this same error show up. Then i can only reboot system. Got an update failed message.since that when i check for updates iam not even getting any. May be it will be solved by a factory reset .but even if i get an ota. The update wont proceed .because the recovery wont allow me to do that
And also that wipe cache partition also results the same error .so without solving this error i cant update to the latest MM too :/ .

In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Flash that recovery with fastboot
Wipe /system in fastboot
Reboot to recovery and update with the stock ROM .zip
Or
Even easier, use Sziraqui's fastboot ready .IMG files and just flash them via fastboot.:good:

where can i find the recovery file in Stock rom
4llerbuntu said:
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Thanks for the Information, Can you please help to find the recovery file in Stock rom.
Click to expand...
Click to collapse

The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?

4llerbuntu said:
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
Click to expand...
Click to collapse
Hi, I see only boot.img in the zip file. Is there a hidden recovery?

4llerbuntu said:
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
Click to expand...
Click to collapse
I see only boot.img file , i didn't find any recovery.img file, in case if you have already done this probably yes then please share us the steps to get recovery from Stock rom.

4llerbuntu said:
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Flash that recovery with fastboot
Wipe /system in fastboot
Reboot to recovery and update with the stock ROM .zip
Or
Even easier, use Sziraqui's fastboot ready .IMG files and just flash them via fastboot.:good:
Click to expand...
Click to collapse
I cant find any recovery.img in the firmware zip. :/
Can you detaily explain that fastboot method as it is for flashing the lolipop recovery for downgrading to 1.13.
Iam a beginner in android. This is my first android phone.

murat124 said:
Hi, I see only boot.img in the zip file. Is there a hidden recovery?
Click to expand...
Click to collapse
I found out that recovery for each firmware is available here. You should use a desktop browser to use this website.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa

ThanveerAliSayed said:
I found out that recovery for each firmware is available here. You should use a desktop browser to use this website.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
Click to expand...
Click to collapse
Thank you.
Can ZE551KL use the recovery.img from ZE550KL? My ZE551KL has the extra 1700(AWS) band.

Please where are you guys downloading your stock rom from?
The stock zip is NOT flash-able like a custom ROM .zip. That's not how it works. If the Roms you have are custom recovery flash-able, they are not the OEM rom, they have been modified.
All the Roms I have come with a recovery.img file...
Then again if I have to explain how to use fast boot to flash the recovery, there is a good chance you shouldn't be messing around with fast boot.......
---------- Post added at 10:03 PM ---------- Previous post was at 10:02 PM ----------
murat124 said:
thank you.
Can ze551kl use the recovery.img from ze550kl? My ze551kl has the extra 1700(aws) band.
Click to expand...
Click to collapse
no it cannot. Do not try it

Weird ..... I can find recovery.img

Can anyone explain me detail. How to flash recovery only. My bootloader is not unlocked. Someone said that i need to unlock bootloader to flash the stock recovery

ThanveerAliSayed said:
Can anyone explain me detail. How to flash recovery only. My bootloader is not unlocked. Someone said that i need to unlock bootloader to flash the stock recovery
Click to expand...
Click to collapse
You don't need to unlock bootloader for flashing stock recovery that you downloaded from the above mega drive.
To flash the recovery.img (or any .img) You need to have Adb and fastboot files in your pc as well as Asus Zenfone drivers installed
All info and downloads for adb and fastboot can be found here
Search and download Asus ZenFone 2 laser drivers.
Once you have your pc setup with these tools,
With Administrator priveleges, locate the folder where adb.exe and fastboot.exe files are present. Hold down shift key and right click on that folder and select "open command window here". Then reboot your phone to fastboot mode [power off, hold vol up +power, release power when logo appears]
Connect your device to pc.
Type the following command on cmd
Code:
fastboot devices
Output should be something like this
Code:
FCAHSJSJJAKAK fastboot
This command will check if your device is connected or not
If output is blank, device is not being detected.
To flash recovery.img, copy the recovery.img file to the same folder where fastboot.exe exists and then type
Code:
fastboot flash recovery recovery.img
Output is easy to understand, if it says [OKAY] then flashing succeeded

Tried downgrading ze551kl by fastboot erase system then installing .zip from Asus website (via sdcard). All of the Asus updates except the earliest fail with 'fota return code 403'.
1.14.40.550 installs ok but then boots (gets as far as displaying the wallpaper), gives an error message in german (looks like 'android media process stopped') and goes into boot loop. Anyone seen this before?
Also, any way to build a recovery.img from the Asus update files?

invalid boot image whenever i flashed stock recovery,any one know why ?
What i do is flash the stock recovery and flash relock bootloader.

Leftrand said:
invalid boot image whenever i flashed stock recovery,any one know why ?
What i do is flash the stock recovery and flash relock bootloader.
Click to expand...
Click to collapse
I think OP needs a small correction to enter into FASTBOOT you need to press volume up and power instead of volume down and power buttons
---------- Post added at 05:45 PM ---------- Previous post was at 05:38 PM ----------

[GUIDE][ZS620KL][Update 29.08.2019] 5Z How to unlock root up/downgrade and unbrick

Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 29.08.2019] Added new download locations for raw images
[Update 07.01.2019] Added more current raw image for ZS620KL WW 80.30.96.111
[Update 25.10.2018] Added raw image for ZS621KL.
[Update 09.08.2018] Updated for 80.11.37.95 and future versions.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as of 20.07.18 is 80.11.37.86. Newer versions will work too!
This guide is written for firmware 80.11.37.86. If you do not want to upgrade/downgrade to 80.11.37.86 you will need to use the firmware (zip file from ASUS) you are on in all the steps.
If you upgrade your firmware to a newer version AFTER rooting it you will lose root! You will need to patch the boot.img of the new firmware again > follow the rooting guide.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty! Currently there is no method known to relock it!
You will get a warning message about your unlocked bootloader at every boot.
You will no longer receive OTA updates but you can download the new firmwares directly from Asus.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware (ZS620KL WW):
WW 80.10.8.54
https://www.androidfilehost.com/?fid=1899786940962570681
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
WW 80.30.96.111
https://www.androidfilehost.com/?fid=1899786940962570682
https://drive.google.com/file/d/16OgxiPFSDJwhitnqJaITuO-XPOrg_7q9/view
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by amscova.
raw firmware (ZS621KL):
https://addrom.com/raw-rom-unbrick-for-asus-zenfone-5z-zs621kl/
https://www.androidfilehost.com/?fid=1899786940962570680
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by B Nath.
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware from 80.11.37.86 up with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this. There is currently no method know to relock the bootloader.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
flashall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide, GSPD and amscova for providing the ZS620KL raw image links and B Nath for finding the ZS621KL raw image.

Nice Theard
Thank You for your work

Upgrade after rooting
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.

isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
Click to expand...
Click to collapse
Process is too long. I am working on unofficial Unlock Tool so that we can retain the warranty.
For downgrading, there is a tool for that. For me, fastboot codes may mess up the system/cache partitions.
If anyone wanna test my unlocking tool, feel free to PM me via Telegram
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward

mihaitaiosub said:
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.
Click to expand...
Click to collapse
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.

isthisadagger said:
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.
Click to expand...
Click to collapse
And is not possible to root again whith method described on this thread?

mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
This is why we need TWRP.

mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
It is possible with Magisk Manager 5.8.3.

isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as iof 20.07.18 is 80.11.37.86.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
This guide is written for firmware 80.11.37.86. If you do not want to upgrade to 80.11.37.86 you will need to use the firmware you are on in all the steps.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty!
You will get a warning message about your unlocked bootloader at every boot.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware:
https://drive.google.com/file/d/1ogbQeeNDRPFCb9jl3kpRDK_DmsneQ0xL/view?usp=drivesdk
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware up to 80.11.37.86 with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
patchall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide and GSPD for providing the raw image name.
Click to expand...
Click to collapse
Does unbricking lock the bootloader back since we will be flashing a raw a file.

With Magisk Manager 5.8.3 the whole guide works like a charm
THX

My Zenfone 5z isn't being detected in fastboot mode, kindly help with correct driver softwares, my PC is running on Windows 10
Update : I got my phone to detect in fastboot

How to wipe cache partition
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks

chandru.biradar2 said:
Does unbricking lock the bootloader back since we will be flashing a raw a file.
Click to expand...
Click to collapse
No.

kelly66 said:
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks
Click to expand...
Click to collapse
Honestly killing the cache rarely helps things.

hi guys how to do this on Macbook pro? Any clues?

shantanudl said:
hi guys how to do this on Macbook pro? Any clues?
Click to expand...
Click to collapse
I do not have any experience with mac os but if you want to root:
Adb/fastboot is available for mac os. All you need to do is find a tool to extract the boot.img from the payload.bin.
If you want to downgrade/unbrick: You would need to convert the bat/cmd files in the full firmware to some shell scripts and exchange the fastboot.exe.

How do I un-root, re-lock bootloader?

ferez said:
How do I un-root, re-lock bootloader?
Click to expand...
Click to collapse
unroot: You press "uninstall" in magisk manager or install an updated firmware without patching boot.img or downgrade.
I have not tried re-locking the bootloader.

So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens

jens13 said:
So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens
Click to expand...
Click to collapse
You won't get OTAs + your warranty is voided (due to unlocking Officially)
Yes, you can update your phone by sideloading the zip from ASUS Support Website

HELP!! (Soft-) bricked my P20Pro CLT-L29

He guys,
as you've read I bricked my phone and I don't know how or where I did the mistake?
Status before brick:
-) FW: EMUI 8.xxx (not exactly sure which one it was)
-) TWRP: 3.2.3.0
-) Rooted
-) BL: unlocked
-) PHONE Unlock
-) FRP Unlock
What I wanted to do:
-) FW Update to: EMUI 9.0 via FirmwareFinder
What I've done:
-) Did a Titanium Backup
-) Installed Firmware Finder
-) Downloaded the Firmware CLT-L29C432E5R1P9B195 (9.0.0.195) (BUT there were ONLY 2 files)
-) 1. file was "update.zip"
-) 2. file was "update_full_CLT-L29_hw_eu.zip"
-) Renamed the files to
-) 1. kept file name "update.zip"
-) 2. file renamed "update_full_CLT-L29_hw_eu.zip" --> update_all_hw.zip
-) Put the 2 files + hurupdater_04.zip + recovery.img (TWRP 3.2.1.0.img) to a folder in Root on my device
-) Reboot to recovery -> TWRP
-) TWRP -> Install -> hurupdater_04.zip
ERRORS:
-) first I saw a message --> "CLT-L09 "Firmware installing --> how can that happened, if I downloaded the CLT-L29 version?
-) Then it aborted the installing process
Current situation:
-) TWRP is installed again --> TWRP 3.2.1.-0 by Pretorian
-) PHONE Unlock
-) FRP Unlock
-) no OS
!! Cannot access my files either via TWRP or Windows explorer --> all files are encrypted and have totally weird names
So please, please help me installing an OS again!
!! And is there a chance to get access to my pictures back???
I appreciate every helpfull advise.
Thanks in advance!!!

He guys,
nobody has an idea to solve/help me with my issues/situation?
I searched the forum and also other forums and pages to find a solution to "my" problem, but without any helpful results.
I am afraid of doing an eRecovery restore because of losing all my data.
I have currently: TWRP installed -> Files/folders with weird names (shown in TWRP & Phone connected to PC "Explorer")
What can I do to save, restore, copy my pictures and files from phone to PC?
Please give me some hints.

This way brought me back
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.

Vedrick said:
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Click to expand...
Click to collapse
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.

Da_Hausa said:
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.
Click to expand...
Click to collapse
I honestly don't think any twrp will work, another reason i'll never buy a huawei again. You could try extracting the image files from the update.app that you get from the update.zip file. then manually flash:
You can extract the image files using EMUI Extractor Application.
fastboot flash cust cust.img
fastboot flash system system.img
I believe the pictures are located on the userdata partition. be sure to flash the right android version as it may depend on what framework you have and how far you got when it was updating. You may want to verify the location of those pictures first.

SO I replicated your soft brick, after I backup up my photos. I ccouldn't save them. I'm up and running though. Turns out I had to first manually flash those image files located in update.app. Then I had to do this

Modified\Updated (Bricked device fix)
1) Try downloading the firmware here: FIRMWARE
2) Extract the update.app file from the update.zip, then use EMUI extractor to extract all the image files. You'll then need to manually flash a few of them: (You can move all these images into the main folder of the Reflash tools located in step 3, then run CMD-HERE)
Commands: (Some might error, i forget which but its alright)
fastboot flash cust cust.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk recovery_ramdis.img (Very Important)
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash vector vector.img
fastboot flash system system.img
fastboot reboot, unplug the USB-C cable and hold the volume up button. this will put you into recovery mode.
Then you'll need to format data using with the EMUI recovery and if given the option format cache.
Reboot back into bootloader\Download mode.
3) Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.

Unfortunately I seem to have the same issue. I followed @Vedrick's tutorial.
However after fastboot reboot I'm stuck on 'Your device is booting now...'
Any ideas?
I worry that perhaps the 'boot image' on my p20 is messed up. However in the .APP file I can't find the boot image to restore. I do however see 2 SYSTEM images.
nvm! Got it! Had to fastboot erase userdata.

How to install Lineage 13 in P7 LXX

FULL INSTALLATION GUIDE OF LINEAGE 13.0 IN HUAWEI P7
Requirements
1. Data transfer cable
2. A laptop or desktop pc
3. Huawei P7 (obviously :silly
4. All the files i'll leave as the guide progresses
Observation:
I'm not responsible for you doing the wrong steps and bricking your phone. If you pass look for a tutorial on Youtube to fix it. Without further ado, let's get started.
STEPS IF YOU ARE IN EMUI 3.1 B8XX – ANDROID 5.X.X WITH THE BOOTLOADER LOCKED:
1). The first step is to back up all your data including pictures, songs, photos, documents, and so on a USB or on a pc.
Once we have backed up all personal data we proceed to download the rollback, this file will help us to return to Android version 4.4.2.
Link: https://bit.ly/2CMwg45
2). After downloading we unzip it and pass it to the phone (if you are already on the phone unzip it with some app, just search the Google Play "unzip files" and ready), more specifically in the internal storage or in a folder called "dload" (if you don't have any folders like that, create it and place the file there).
We go to the EMUI 3.1 update app (or directly in the phone settings), and select Local Update, after doing so let the phone restart and install the roll back.
In some cases when the rollback is being installed and goes by 95% will say it failed, do not give greater importance to that message and restart the phone manually. One sign that the rollback worked properly is by observing that when the phone starts doing its power animation (bootlogo) the lower message that says "Powered by ANDROID" will no longer appear.
SO YOU SHOULD SEE THE STARTUP ANIMATION AFTER YOU HAVE INSTALLED THE ROLLBACK
{
"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"
}
WHAT TO DO AFTER YOU HAVE INSTALLED THE ROLLBACK?
3). Once the phone has turned on we proceed to download the B609 version, we will leave it in the "dload" folder of the internal or external memory and install it in the same way we did with the rollback.
Note: If your "dload" still contains the rollback file, delete it and leave only the B609 file.
Link: https://bit.ly/2Oz88q2
In some cases when the percentage of the installation goes by 95% it will say that it failed, but once again we will not pay attention to it and restart the phone manually.
Once the phone is switched on, it will tell us that the data partition will not work and that it is time to format the phone, we will select the format option and again the phone will restart and start charging.
As I said before, it may be that by formatting an error, but we will not pay attention to it, we restart the phone manually and configure it.
4). Once configured we will notice that in the notification tray there is no message related to the Android version is Beta, IF IT HAPPENS this they have to download the following file and install it as the previous ones.
If it does not happen they skip this step.
Note: if your “dload” still contains the B609 file, delete it and leave only the file that is used to correct this. (MANDATORY IF YOU HAVE THAT NOTICE IN THE NOTIFICATION TRAY worth the redundancy)
Link: http://bit.ly/2FME1IS
5). After having configured it, we will download the B621 version (unzip it) and proceed to leave it in the “dload” folder of the internal or external memory, installing it as we did with the rollback or the B609.
Note: if your “dload” still contains the notification fix file, delete it and leave only the B621 file.
Link: http://bit.ly/2Wzm5rr
6) .After having installed the B621, the next thing we will do is download the KingRoot from the browser. I will leave the link in case you don't want to download virus.
Link: http://bit.ly/2U5VZiu
7). Once the KingRoot is installed, we tell it to root us, after the procedure is finished, we restart the phone and go to “about the phone” there we look for where it says “Build number” and press it often until it appears We are already developers.
8). We return and enter the developer options, once there, we look for the option that says “USB debugging” and activate it, in doing so we take the data cable and connect the phone to the PC and download the following program (PC).
Link: http://bit.ly/2V7h7RL
9). We decompress it and open the file that says “Get_bootloader_code”, once opened it will show us the following interface.
10). Press the "4" key on our keyboard and press "enter", the following will appear.
11). Again we press “enter” and a window will appear on the phone saying that “ADB programs” wants to get the benefit of a super user. We grant you the permits and then the advantage will appear in the bootloader code.
12). We copy it to a notebook and then turn off the phone and without disconnecting it from the PC, press the "volume -" keys and the power button.
If we did all the steps correctly when the phone turns on in download mode the phone will say “Phone Unlocked”
13). If you tell us this we can restart the phone in the normal way, and with root we go to the G Play and install Flashify and grant super user permissions.
14). We go to the "backup" tab and make backup of the kernel and recovery stock.
15). We go to the G Play and look for the “EFS backup” application and install it, we make a backup copy of the IMEI.
16). Once having these backups we pass them to the PC to have them safe.
17). Between almost the last steps we go to the following link and download the TWRP 3.0.3
Link: http://bit.ly/2HR2iA6
18). We leave it anywhere on the phone and unzip it.
19). Once decompressed we go to Flashify and select the option to install recovery, we look for the file where we would have saved it and flash it.
20). Already with the TWRP installed we make sure that if it is installed by getting into recovery mode (look for a tutorial on how to enter recovery mode on Huawei devices)
21). If everything works correctly, if not, go back to point 19.
2. 3). Once selected you will understand that there is a small iPhone-style button to slide, we will slide it and we will be in front of the TWRP interface
24). We go to the "backup" option there we check the boxes "system, start and cust" then slide the iPhone style button and wait for the proper backup.
25). We return to the main interface, we give it "restart" and then "system" and wait for the phone to turn on.
26). Once on we connect the phone to the PC and go to the internal memory, once there we look for a folder called “TWRP” we copy it to any part of the PC and it is YOUR decision to delete it from the phone.
27). Download the file of the rom Lineage 13.0
Link: http://bit.ly/2CMzTqt
28). Once the file is downloaded, we pass it to the phone and leave it on a route that is easily accessible.
29). We go back to recovery mode and we go to the "clean" option and slide the iPhone style button.
30). Once cleaned, we return to the main interface and go to where it says "install"
31). Once there we look for the folder where we leave the downloaded Lineage file, and select it.
32). After selecting we slide the iPhone style button and let it load
Note: This process usually takes a long time, DO NOT RESTART the phone until it vibrates and a “restart” button appears, when it appears we give it and if you see a button to slide once more, we click on “do not install” and wait to restart the phone
READY! The phone should turn on correctly and should show the new Lineage interface.
You can now configure the phone and restore everything.
IF YOU ARE IN ANDROID 4.4.2 IN VERSION B6XX AND YOU HAVE THE BLOCKED BOOTLOADER START THE GUIDE FROM POINT NUMBER 5.
IF YOU ARE IN ANDROID 4.4.2 IN THE EMOTION VERSION 2.3 WITH THE BOOTLOADER BLOCKED, START FROM POINT NUMBER 5.
IF YOU ARE IN ANDROID 5.1.1 IN VERSION B8XX WITH THE UNLOCKED BOOTLOADER AND WITH ROOT, START FROM POINT NUMBER 13.
I'm sorry for my English. I hope you find this guide useful.
ROM developer: Kostyan_nsk - https://forum.xda-developers.com/member.php?u=6152035
Original Post of the ROM: https://forum.xda-developers.com/as...rom-lineageos-13-0-huawei-ascend-p6s-t3879236
Update: 28/10/2019

I got P7 L10 B623 EU with Android 4.4.2 (EMUI 3.0).
I can't skip bootloader status check, I have to buy dc-unlocker coupons to unlock it.
Locked bootloader = no root. It seems that it is different than while on Lollipop already.
Free bootloader unlock was banned in 2018 by Huawei.
Besides most people report bugs, lags and other issues on original Lollipop 5.x with this phone.
I cant find any succesful report about upgrading Huawei P7 with blocked bootloader. So what are the advantages while using Lineage 13 on this phone, because it sounds strange. More details please.

whiteindian said:
I got P7 L10 B623 EU with Android 4.4.2 (EMUI 3.0).
I can't skip bootloader status check, I have to buy dc-unlocker coupons to unlock it.
Locked bootloader = no root. It seems that it is different than while on Lollipop already.
Free bootloader unlock was banned in 2018 by Huawei.
Besides most people report bugs, lags and other issues on original Lollipop 5.x with this phone.
I cant find any succesful report about upgrading Huawei P7 with blocked bootloader. So what are the advantages while using Lineage 13 on this phone, because it sounds strange. More details please.
Click to expand...
Click to collapse
I tell you, exactly about the locked bootloader I left a file that only serves exclusively to unlock the bootloader to P7, as for what, without the unlocked bootloader, root cannot be done, it is not so, it can be achieved.I know that many people have problems with Android 5 on P7, but in my personal situation, I installed Lineage 13 on my P7, successfully, so I decided to make this guide that can be long.but I explain exactly what I had to do because there is no tutorial on YouTube that shows it, so I did this written tutorial for the community. You only have to follow the steps to the letter if you do not want the phone to be damaged, and Lineage has some advantages over Huawei EMUI. Sorry for just answering this post.
Edit: If you need Android 5.0.1 on your P7 to be able to do the same procedure, tell me. I don't remember if I left download link to upgrade to Android 5.0.1 based on EMUI.

You have to buy 4 credits to unlock the bootloader in 2019. Now I got rooted phone.
It is impossible to unlock bootloader different way and you have to keep your code to use it with fastboot mode at any time.
If you already rooted you can unlock bootloader and go back to B621 with it https://forum.xda-developers.com/ascend-p7/general/guide-how-to-unlock-bootloader-p7-l10-t3879952 No idea why B621 is an initial release.
There ia an old topic with .img files supposed to be related wit changing stock Android kernel but no idea what are advantages here for stock fw https://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
I got Europeand B623 with CUST C432D001 . There is an Asian version of the Lollipop with B853 and could be used on European P7's with C432D001 https://forum.xda-developers.com/ascend-p7/general/best-method-to-install-b853-european-p7-t3299829 but I don't know if it is simple to get back to stock in this case. Then we change CUST number. No idea what are advantages of Asian version and if it is simple to unlock bootloader on different region firmware.
I have to know a guide what are transition packs to make it all without issues if we get up and get back with certain upgrades.(can't find topics on xda)
- get up to Lollipop 5.1.1 and the get back to stock
- get up to Lineage project (Android 6.0) and get back to stock 4.4.2
. I think there could be more issues while not upgrading in correct order than while using a certain version of Android https://rejzor.wordpress.com/2015/12/03/update-huawei-ascend-p7-l10-to-android511/
I suppose Lineage project is the last one for this phone. Ascend P7 is a real slim 5.0" smartphone really fast for KitKat. I think a Lineage project for P7 has to be treated as an upgrade from Lollipop and its disadvantages. If its (Android 6.0) has so many crappy apps, have to find one what are the real advantages in certain situations than Lollipop. For many companies in my country Android 5.1.1 is an initial realease version (i.e. shopping).

Android 4.4.2
then B621 -> (B621 CUST fix)* -> B830 -> B839 -> B852
or*
B623 -> B852
or
B621 -> B621 CUST fix (432 to 433) -> B853
or when on Lollipop
B800 -> B621 -> B621 CUST fix -> B853
-----
So as I understand the best way now is to get into B852 and then flash Lineage
I dont know why in your guide we need to install B609, but as I had mentioned in first link Ive sent we need basically two files B621 and Rollback B800. In fact if I could choose I would install B853 but not sure if its safe when CUST failed. B853 was designed for Asia not for Europe.

downgrade to emui 2.3
SharkyBeAre said:
FULL INSTALLATION GUIDE OF LINEAGE 13.0 IN HUAWEI P7
Requirements
1. Data transfer cable
2. A laptop or desktop pc
3. Huawei P7 (obviously :silly
4. All the files i'll leave as the guide progresses
Observation:
I'm not responsible for you doing the wrong steps and bricking your phone. If you pass look for a tutorial on Youtube to fix it. Without further ado, let's get started.
STEPS IF YOU ARE IN EMUI 3.1 B8XX – ANDROID 5.X.X WITH THE BOOTLOADER LOCKED:
1). The first step is to back up all your data including pictures, songs, photos, documents, and so on a USB or on a pc.
Once we have backed up all personal data we proceed to download the rollback, this file will help us to return to Android version 4.4.2.
Link: https://bit.ly/2CMwg45
2). After downloading we unzip it and pass it to the phone (if you are already on the phone unzip it with some app, just search the Google Play "unzip files" and ready), more specifically in the internal storage or in a folder called "dload" (if you don't have any folders like that, create it and place the file there).
We go to the EMUI 3.1 update app (or directly in the phone settings), and select Local Update, after doing so let the phone restart and install the roll back.
In some cases when the rollback is being installed and goes by 95% will say it failed, do not give greater importance to that message and restart the phone manually. One sign that the rollback worked properly is by observing that when the phone starts doing its power animation (bootlogo) the lower message that says "Powered by ANDROID" will no longer appear.
SO YOU SHOULD SEE THE STARTUP ANIMATION AFTER YOU HAVE INSTALLED THE ROLLBACK
WHAT TO DO AFTER YOU HAVE INSTALLED THE ROLLBACK?
3). Once the phone has turned on we proceed to download the B609 version, we will leave it in the "dload" folder of the internal or external memory and install it in the same way we did with the rollback.
Note: If your "dload" still contains the rollback file, delete it and leave only the B609 file.
Link: https://bit.ly/2Oz88q2
In some cases when the percentage of the installation goes by 95% it will say that it failed, but once again we will not pay attention to it and restart the phone manually.
Once the phone is switched on, it will tell us that the data partition will not work and that it is time to format the phone, we will select the format option and again the phone will restart and start charging.
As I said before, it may be that by formatting an error, but we will not pay attention to it, we restart the phone manually and configure it.
4). Once configured we will notice that in the notification tray there is no message related to the Android version is Beta, IF IT HAPPENS this they have to download the following file and install it as the previous ones.
If it does not happen they skip this step.
Note: if your “dload” still contains the B609 file, delete it and leave only the file that is used to correct this. (MANDATORY IF YOU HAVE THAT NOTICE IN THE NOTIFICATION TRAY worth the redundancy)
Link: http://bit.ly/2FME1IS
5). After having configured it, we will download the B621 version (unzip it) and proceed to leave it in the “dload” folder of the internal or external memory, installing it as we did with the rollback or the B609.
Note: if your “dload” still contains the notification fix file, delete it and leave only the B621 file.
Link: http://bit.ly/2Wzm5rr
6) .After having installed the B621, the next thing we will do is download the KingRoot from the browser. I will leave the link in case you don't want to download virus.
Link: http://bit.ly/2U5VZiu
7). Once the KingRoot is installed, we tell it to root us, after the procedure is finished, we restart the phone and go to “about the phone” there we look for where it says “Build number” and press it often until it appears We are already developers.
8). We return and enter the developer options, once there, we look for the option that says “USB debugging” and activate it, in doing so we take the data cable and connect the phone to the PC and download the following program (PC).
Link: http://bit.ly/2V7h7RL
9). We decompress it and open the file that says “Get_bootloader_code”, once opened it will show us the following interface.
10). Press the "4" key on our keyboard and press "enter", the following will appear.
11). Again we press “enter” and a window will appear on the phone saying that “ADB programs” wants to get the benefit of a super user. We grant you the permits and then the advantage will appear in the bootloader code.
12). We copy it to a notebook and then turn off the phone and without disconnecting it from the PC, press the "volume -" keys and the power button.
If we did all the steps correctly when the phone turns on in download mode the phone will say “Phone Unlocked”
13). If you tell us this we can restart the phone in the normal way, and with root we go to the G Play and install Flashify and grant super user permissions.
14). We go to the "backup" tab and make backup of the kernel and recovery stock.
15). We go to the G Play and look for the “EFS backup” application and install it, we make a backup copy of the IMEI.
16). Once having these backups we pass them to the PC to have them safe.
17). Between almost the last steps we go to the following link and download the TWRP 3.0.3
Link: http://bit.ly/2HR2iA6
18). We leave it anywhere on the phone and unzip it.
19). Once decompressed we go to Flashify and select the option to install recovery, we look for the file where we would have saved it and flash it.
20). Already with the TWRP installed we make sure that if it is installed by getting into recovery mode (look for a tutorial on how to enter recovery mode on Huawei devices)
21). If everything works correctly, if not, go back to point 19.
2. 3). Once selected you will understand that there is a small iPhone-style button to slide, we will slide it and we will be in front of the TWRP interface
24). We go to the "backup" option there we check the boxes "system, start and cust" then slide the iPhone style button and wait for the proper backup.
25). We return to the main interface, we give it "restart" and then "system" and wait for the phone to turn on.
26). Once on we connect the phone to the PC and go to the internal memory, once there we look for a folder called “TWRP” we copy it to any part of the PC and it is YOUR decision to delete it from the phone.
27). Download the file of the rom Lineage 13.0
Link: http://bit.ly/2CMzTqt
28). Once the file is downloaded, we pass it to the phone and leave it on a route that is easily accessible.
29). We go back to recovery mode and we go to the "clean" option and slide the iPhone style button.
30). Once cleaned, we return to the main interface and go to where it says "install"
31). Once there we look for the folder where we leave the downloaded Lineage file, and select it.
32). After selecting we slide the iPhone style button and let it load
Note: This process usually takes a long time, DO NOT RESTART the phone until it vibrates and a “restart” button appears, when it appears we give it and if you see a button to slide once more, we click on “do not install” and wait to restart the phone
READY! The phone should turn on correctly and should show the new Lineage interface.
You can now configure the phone and restore everything.
IF YOU ARE IN ANDROID 4.4.2 IN VERSION B6XX AND YOU HAVE THE BLOCKED BOOTLOADER START THE GUIDE FROM POINT NUMBER 5.
IF YOU ARE IN ANDROID 4.4.2 IN THE EMOTION VERSION 2.3 WITH THE BOOTLOADER BLOCKED, START FROM POINT NUMBER 5.
IF YOU ARE IN ANDROID 5.1.1 IN VERSION B8XX WITH THE UNLOCKED BOOTLOADER AND WITH ROOT, START FROM POINT NUMBER 13.
I'm sorry for my English. I hope you find this guide useful.
ROM developer: Kostyan_nsk - https://forum.xda-developers.com/member.php?u=6152035
Original Post of the ROM: https://forum.xda-developers.com/as...rom-lineageos-13-0-huawei-ascend-p6s-t3879236
Update: 28/10/2019
Click to expand...
Click to collapse
Hello I used first steps to downgrade my phone from aweful B852 because it was damaged. I am now on your B621 but I want to downgrade to emui 2.3 cos I want a complete rom.please help.
By the way. How is that Lineage 13? I want something veeery smooth and fine. I can't stand bugs and low speed... . Thanks all.:good:

whiteindian said:
Android 4.4.2
then B621 -> (B621 CUST fix)* -> B830 -> B839 -> B852
or*
B623 -> B852
or
B621 -> B621 CUST fix (432 to 433) -> B853
or when on Lollipop
B800 -> B621 -> B621 CUST fix -> B853
Click to expand...
Click to collapse
I am not sure 100% if this guide is 100% good, but now I am under Lollipop with B853. I had upgraded it manullly to B852 and then OTA B853 upgrade.
Lineage 13 is still beta release you can experience many bugs. For Android 5.1.1 there are no lags and bugs (I use EU version for my region), and you can install without issues most of Google Play Store apps.
If you know how to downgrade to B621 you know how to use transition packs, and it doesnt make sense if you had damaged your phone on B852....How is it your bootloader status?

go back to original soft
I did use this tutorial and succeed with the first attempt. So thank you very much for this.
But...
I'm in need of using WPA2-Enterprise Wi-Fi connection and LOS13 isn't capable to connect. (It connects and disconnects in a loop) so .... I'd like to go back to B852 but I don't know how. I tried downloading Full ROM 852 via Huawei Finder and flash downloaded update.zip file by using TWRP but program prevents me from doing this. First error code 7 was that signatures doesn't match (By the way LOS changed model number to L7-00 from L7-10 but let's just say that it's irrelevant for now) because it check for original based ROMs:
Code:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Huawei/P7-L10/hwp7:5.1.1/HuaweiP7-L10/C900B852:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Huawei/P7-L10/hwp7:4.4.2/HuaweiP7-L10/C00B623:user/ota-rel-keys,release-keys");
assert(file_getprop("/system/build.prop", "ro.product.device") == "hwp7" ||
file_getprop("/system/build.prop", "ro.product.device") == "hwp7" ||
file_getprop("/system/build.prop", "ro.build.product") == "hi6620oem" ||
file_getprop("/system/build.prop", "ro.build.product") == "hi6620oem");
So i edited \update\META-INF\com\google\android\updater-script and simply deleted those positions but then an "apply_patch_check("/3rdmodem/modem_image/viacbp8d/boot.rom" showed up. So I believe that this isn't the proper way to go back.
Please help.

You dont need to use Huawei Finder, did you try 3-button method to force fw update?

whiteindian said:
You dont need to use Huawei Finder, did you try 3-button method to force fw update?
Click to expand...
Click to collapse
??? I have TWRP installed so using method with 3 buttons just launches TWRP
//edit
Okay, I have figured it out. I downloaded Full 852
Code:
http://download-c.huawei.com/download/downloadCenter?downloadId=73403&version=270293&siteCode=hu
Extracted .rar and then extracted update.app via HuaweiUpdateExtractor_0.9.9.5 and did flash via fastboot:
Code:
C:\adb>fastboot flash cust CUST.img
target reported max download size of 536870912 bytes
sending 'cust' (468232 KB)...
OKAY [ 20.680s]
writing 'cust'...
OKAY [ 21.900s]
finished. total time: 42.580s
C:\adb>fastboot flash recovery RECOVERY.img
target reported max download size of 536870912 bytes
sending 'recovery' (12510 KB)...
OKAY [ 0.620s]
writing 'recovery'...
OKAY [ 1.020s]
finished. total time: 1.640s
C:\adb>fastboot flash boot BOOT.img
target reported max download size of 536870912 bytes
sending 'boot' (9432 KB)...
OKAY [ 0.460s]
writing 'boot'...
OKAY [ 0.750s]
finished. total time: 1.210s
C:\adb>fastboot flash system SYSTEM.img
target reported max download size of 536870912 bytes
sending sparse 'system' 1/3 (523460 KB)...
OKAY [ 22.061s]
writing 'system' 1/3...
OKAY [ 24.650s]
sending sparse 'system' 2/3 (522666 KB)...
OKAY [ 23.140s]
writing 'system' 2/3...
OKAY [ 24.580s]
sending sparse 'system' 3/3 (429950 KB)...
OKAY [ 18.430s]
writing 'system' 3/3...
OKAY [ 20.175s]
finished. total time: 133.041s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.010s
C:\adb>
then I needed to wipe data via stock recovery (by then) due to boot loop. Then instant OTA update to 853 via system tools.
The bad news is that it didn't resolve my problem. I don't know why WPA-2 Enteprise doesn't work ; / At least it acquieres IP but then disconnects and so on...