Database Users

P8 Lite Boot loop

I've been trying almost everything for days. When I turn on the phone the bootloader enters in a loop.
I can't access to recovery (vol up + power), not even in update mode(vol up & vol down + power).
The only thing I can access is the fastboot but my phone is locked and I don't the have the imei to unlock via calculator or the oficial huawei page.
If someone have any suggestions.

Instalar ROM vía fastboot
Sent from my ALE-L21 using XDA-Developers Legacy app

VicenteR93 said:
I've been trying almost everything for days. When I turn on the phone the bootloader enters in a loop.
I can't access to recovery (vol up + power), not even in update mode(vol up & vol down + power).
The only thing I can access is the fastboot but my phone is locked and I don't the have the imei to unlock via calculator or the oficial huawei page.
If someone have any suggestions.
Click to expand...
Click to collapse
If getting your IMEI is your only concern then you can get that from the box... But you'll need Product ID too, and for that you'll need to have your phone booted up...

amageek said:
If getting your IMEI is your only concern then you can get that from the box... But you'll need Product ID too, and for that you'll need to have your phone booted up...
Click to expand...
Click to collapse
There is a program for that. Huawei product id generator. You can find this program very easy.

amageek said:
If getting your IMEI is your only concern then you can get that from the box... But you'll need Product ID too, and for that you'll need to have your phone booted up...
Click to expand...
Click to collapse
when you mean the box. Is the box where I bought the phone? 'Cause I don't have it anymore and is not even behind the battery.

VicenteR93 said:
when you mean the box. Is the box where I bought the phone? 'Cause I don't have it anymore and is not even behind the battery.
Click to expand...
Click to collapse
Yes that box.. There may be other way too, I'll look into it and share is I find anything

Fedroid said:
Instalar ROM vía fastboot
Sent from my ALE-L21 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I downloaded the official ROM from huawei and is the recent version but when I tried to install it with "fastboot update file.zip" is asking for an android-text.txt and I been searching to re-create that file manually and then is asking for another file and so on.
I've been searching if I can install the oficcial ROM by fastboot even if is not unlocked and find this guide but it is not usefull for me 'cause I can't access into the download mode or use adb.
This is the information I could extract from my phone.
Firmware : ALE-L21C109B130
I couldn't fint this version of firmware.
If you could light my way if you have another method.

VicenteR93 said:
I downloaded the official ROM from huawei and is the recent version but when I tried to install it with "fastboot update file.zip" is asking for an android-text.txt and I been searching to re-create that file manually and then is asking for another file and so on.
I've been searching if I can install the oficcial ROM by fastboot even if is not unlocked and find this guide but it is not usefull for me 'cause I can't access into the download mode or use adb.
This is the information I could extract from my phone.
Firmware : ALE-L21C109B130
I couldn't fint this version of firmware.
If you could light my way if you have another method.
Click to expand...
Click to collapse
Extract files and flash it one by one using fastboot commands

I recommend you watch this video even if it is in Spanish, it can help you
,is from
EloYGomeZTv:good:
Sent from my Huawei P8lite/P8 Lite using XDA Labs

Fedroid said:
Extract files and flash it one by one using fastboot commands
Click to expand...
Click to collapse
Everything failed when tries to write 'cause the bootloader is locked.

davidlikeandroid23 said:
I recommend you watch this video even if it is in Spanish, it can help you
,is from
EloYGomeZTv:good:
Sent from my Huawei P8lite/P8 Lite using XDA Labs
Click to expand...
Click to collapse
I already saw a tutorial like this one but my bootloader is locked and I don't have the imei to unlock it. But thanks anyway.

VicenteR93 said:
I already saw a tutorial like this one but my bootloader is locked and I don't have the imei to unlock it. But thanks anyway.
Click to expand...
Click to collapse
Ok i searched for ways to find an IMEI number and found couple of ways...
1) Look under/in the sim tray. It may be there (I didn't check this out)
2) Find the IMEI/MEID using Google Dashboard. This is Google's control center that can be accessed from any computer with a web browser. You will need to log in with the Google account associated with your Android phone.You can access Google Dashboard by visiting www.google.com/settings/dashboard Expand the "Android" section by clicking the "Android" heading.Locate your phone in the list. If you have multiple devices associated with your account, all of the devices will be displayed. Find the device that you are trying to retrieve the IMEI/MEID number for. (This works)
3) At last, you can try to remove the back case and remove the battery. This can help you in 2 ways. Firstly, there should be IMEI code present under the battery. Secondly, this may cause you to get out of bootloop

amageek said:
Ok i searched for ways to find an IMEI number and found couple of ways...
1) Look under/in the sim tray. It may be there (I didn't check this out)
2) Find the IMEI/MEID using Google Dashboard. This is Google's control center that can be accessed from any computer with a web browser. You will need to log in with the Google account associated with your Android phone.You can access Google Dashboard by visiting www.google.com/settings/dashboard Expand the "Android" section by clicking the "Android" heading.Locate your phone in the list. If you have multiple devices associated with your account, all of the devices will be displayed. Find the device that you are trying to retrieve the IMEI/MEID number for. (This works)
3) At last, you can try to remove the back case and remove the battery. This can help you in 2 ways. Firstly, there should be IMEI code present under the battery. Secondly, this may cause you to get out of bootloop
Click to expand...
Click to collapse
You're the best Sir, the holy ruler!!!
I finally found it. With the option 1.
I checked to the second option and it was there too. Didn't know that option.
Thank you so much.

VicenteR93 said:
You're the best Sir, the holy ruler!!!
I finally found it. With the option 1.
I checked to the second option and it was there too. Didn't know that option.
Thank you so much.
Click to expand...
Click to collapse
Cheers... Now you may proceed further.. Do tell us about your methods/steps/processes for future reference...

Did you try installing hisuite to a windows machine there is a recovery option on it it will install the LATEST emui ROM to your phone and recover it.
http://consumer.huawei.com/minisite/HiSuite_en/index.html
Edit: if I remember correctly you just have to be in fastboot to recover it

ndg_2000 said:
Did you try installing hisuite to a windows machine there is a recovery option on it it will install the LATEST emui ROM to your phone and recover it.
http://consumer.huawei.com/minisite/HiSuite_en/index.html
Edit: if I remember correctly you just have to be in fastboot to recover it
Click to expand...
Click to collapse
I tried but at the end it tells me that I need to take the phone to the nearest center.

I downloaded a lot of ROM to try but I'm still trapped in the boot loop.
I tried all the solutions that has been posted before.

VicenteR93 said:
I downloaded a lot of ROM to try but I'm still trapped in the boot loop.
I tried all the solutions that has been posted before.
Click to expand...
Click to collapse
Have you managed to get the boot loader unlocked if not you need to tackle that first then your recovery options open up some what

ndg_2000 said:
Have you managed to get the boot loader unlocked if not you need to tackle that first then your recovery options open up some what
Click to expand...
Click to collapse
I already unlocked the bootlooader but I still have the boot loop even after pass cust, system, recovery, boot.

VicenteR93 said:
I already unlocked the bootlooader but I still have the boot loop even after pass cust, system, recovery, boot.
Click to expand...
Click to collapse
Stupid question but I will ask it anyway did you md5 check all of the files you have downloaded as I have had issues with another device and it was because of bad files

BND-L24 Unbrick And restore Honor 7x USA

Ok guys bare with me. This is my first Thread. So it may look a little different then the others :laugh:
At least Your honor 7x will no longer be a paper weight
I posted last week that I do Indeed have a good TWRP Honor 7x BND-L24 USA Variant. Since then I have been getting hammered with requests for it. So being the great guy that I am, I have come to the rescue. NO MORE PAPER WEIGHT :laugh: I have also included TWRP 3.1.1. You will Find Direct download links below.
I have heard that Huawei will be releasing the firmware by end of next week. Go to play store and download Huawei Firmware
Finder(FF) To keep checking for it. Once there you can download it through Huawei FF.
When I did the backup TWRP gave me error 255 with the data.img but it did still back it up. I have the boot.img, system.img and data.img. data.img (data.img untested but should work)
If it does not I have a post here https://forum.xda-developers.com/showthread.php?p=75735265#post75735265 that explains how to use just the boot.img and system.img to recover your phone. IGNORE that it is for the 6x. It does indeed work with the 7x
If your phone is bricked and do not have twrp
1.Turn off phone
2. hold volume down while plugging in usb cable from your pc or laptop. That will put you in fastboot.
Tutorial here https://www.xda-developers.com/how-to-root-honor-7x/ on how to download and install ADB tools.
3.. Download TWRP 3.1.1 for honor 7x here https://drive.google.com/open?id=1dzP5ie7vQEn_dGfZHI383bt2sFxwtcTb
For people with TWRP installed
1. Download My TWRP backup here https://drive.google.com/open?id=1Udc4thELESZ4n_nXYmx6loQtTkjHOqSy
2. Extract the zip file to your ext, sdcard.
3. Boot phone into twrp.(Bricked phones hold volume up and press power to launch twrp assuming it is installed.
4. Select restore in twrp menu then choose sd card then the backup folder.
5. Flash the boot system and data img files
6 Reboot.
NO more paper weight :good:
Oh if anyone has twrp 3.2x that works with this with 7x BND-L24 do share please
Well hope this was not to bad :laugh:
Hit that thanks button. Yea that one under my post on the right :laugh:
Hope this has helped

Thank you

lowspeed said:
Thank you
Click to expand...
Click to collapse
No problem. Least I can do. This site has helped me out a lot
Paper weights suck :laugh:

Didn't work. I got to the "booting now" screen and was stuck there forever. I had to restore my old System and Boot partitions to get back to normal.

Didn't Work for me. goes tot the erecovery page.

Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.

Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.

tomjfmu said:
Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.
Click to expand...
Click to collapse
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?

This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.

dukethedj said:
This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.
Click to expand...
Click to collapse
Yes please would love some insight on this. thanks in advance.

forgotenxlegacyx said:
Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.
Click to expand...
Click to collapse
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files

BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
Would you mind linking a thread on how that is done? sorry for my ignorance

forgotenxlegacyx said:
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?
Click to expand...
Click to collapse
i have an idea, maybe you can make a backup not just including the system, data, and boot but other stuff. Because I accidentally wiped everything, and I changed the vender to a10/tl10, and that bricked the phone even more. And the data img doesn't work. You can fix it with this https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468. If someone has a working bnd-l24 or bnd-l34 can you give me everything in the backup?

BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
So you first do that then you do the rest?

Tried again. Getting the 255 error when flashing the Data

Yeah, error 255 is boot looping me too.

does it works well?

Thanks!

RoxRedEye said:
Thanks!
Click to expand...
Click to collapse
You were able to get it to work?

I want to get behind and support this, so much, .But the OP is not registered user, so cant even verify their reputation.
I am late to this device and thread, but my phone will arrive tmw.
I would like to know if this is the only current available restore method for BND-L24?

[Thread Deprecated] Unbrick your device/Revert to Stock-A complete guide

[Update as of May 23, 2020] - Thread no longer active and all download links are invalid
A brief history - A few weeks ago, i got fed up of EMUI and all the bloat. EMUI has a bunch of very useful features but i did miss the AOSP look and feel, root advantages. So, i tried magisk and couldn't get it to work with EMUI(pre 15.4 version). So i switched to Open krin 8.1 AOSP. Used it for a few days but it was too much of a sacrifice (VOLTE and Camera) and occasional buggyness for me to live with.
During this adventure, i found myself (multiple times) with a bricked device (A critical brick with FRP on aswell!).
After a lot of struggle(Specially to find working download links), i'm making this thread, to help fellow users like me.
Before we get started,
This is tested on my device but may not necessarily work with yours! I'm not responsible for any loss/damage/whatever caused because of the information in this thread.
Note 0 : Do not Quote the entire post!!
Note 1 : This guide will be updated as and when necessary.
Note 2 : These methods are only tested on Honor 8 Pro - Indian Variant(DUK-L09-C675)
Note 3 : This guide assumes the bootloader is unlocked.
Note 4 : Do text if you need any clarification on any step!
Thanks to @nanortemis (https://forum.xda-developers.com/honor-8-pro/how-to/restoring-dukfullotaromflasher-t3741223) for the ROM flasher
Download links for every file needed - Download links are now removed.
Let's get started.
Reboot your device into bootloader mode.
How? ​Method 1​1. Shut down the phone.
2. Hold the volume down button and connect the usb cable connected to your PC.​Method 2 (If device is boot looping)​1. Press and hold power button untill phone reboots.
2. Hold volume up key to boot to e-recovery.
3. Click shutdown.
4. Now follow Method 1.​
Now that you are in bootloader mode,
You may find yourself in one of these three conditions
Condition 1. You read Phone unlock , FRP unlock ( Hurray !! This is the easiest to recover from.)
Condition 2. You read Phone unlock , FRP Lock AND you have TWRP flashed and working. ( Phew , there is still hope!)
Condition 3. You read Phone unlock , FRP Lock AND you have STOCK recovery! (Not sure how you got here, but this method is not tested by me.) (Please text if someone is stuck in this situation. I Will think of something if needed)(Guide is not yet updated with instructions on how to do this yet!)
Steps to recover from condition 1
1. Download stock rom files and stock rom flasher(from here) ( I have updated files for indian version.
Please get the version appropriate to your location.)
2. Extract files into a folder and transfer them to an exteral SD or USB OTG(If you can get it to work. I
Couldn't get my OTG to be detected) and insert it into your phone.
3. Reboot to recovery.
How?​ 1. Shutdown the deive(Look above for instructions, if needed.)
2. Hold volume up and then simultaniously press the power key.​ 4. In TWRP, erase everything except micro-sd/otg.
5. Reboot the device into recovery.
6. Flash the zip with the file name "FlashThisZip-DUK_FullOTA_ROM_flasher".
7. Done ! You should now be on Stock Indian oreo rom 8.0.0.323
8. (Optional) Relock bootloader (Check other guids please.)​
Steps to recover from condition 2
1. Download and extract the twrp recovery files i made. ( You may use any stock emui (all partition)
backups you have made!
2. Transer the TWRP folder to External SD / OTG and insert it into the phone.
3. Reboot to recovery.
How?​ 1. Shutdown the deive(Look above for instructions, if needed.)
2. Hold volume up and then simultaniously press the power key.​ 4. In TWRP, erase everything except micro-sd/otg.
5. Restore the backup.
6. Done !!! To flash full stock fresh rom, read on.
7. (Optional) Boot up the phone, head into settings, enable developer options and enable OEM unlock.
8. (Optional) Now, simply follow steps from Condition 1(which is above!)​
Guide is still under construction. I got this out as soon as i can to help anyone who is stuck. Please ignore any typos(They will be fixed when i find time to make this guide better).
All the best :good: :fingers-crossed:
---------------------------------------
Guide created on : 10 June, 2018
Last modification : None

Anirudh A said:
A brief history - A few weeks ago, i got fed up of EMUI and all the bloat. EMUI has a bunch of very useful features but i did miss the AOSP look and feel, root advantages. So, i tried magisk and couldn't get it to work with EMUI(pre 15.4 version). So i switched to Open krin 8.1 AOSP. Used it for a few days but it was too much of a sacrifice (VOLTE and Camera) and occasional buggyness for me to live with.
During this adventure, i found myself (multiple times) with a bricked device (A critical brick with FRP on aswell!).
After a lot of struggle(Specially to find working download links), i'm making this thread, to help fellow users like me.
Before we get started,
This is tested on my device but may not necessarily work with yours! I'm not responsible for any loss/damage/whatever caused because of the information in this thread.
Note 0 : Do not Quote the entire post!!
Note 1 : This guide will be updated as and when necessary.
Note 2 : These methods are only tested on Honor 8 Pro - Indian Variant(DUK-L09-C675)
Note 3 : This guide assumes the bootloader is unlocked.
Note 4 : Do text if you need any clarification on any step!
Thanks to @nanortemis (https://forum.xda-developers.com/honor-8-pro/how-to/restoring-dukfullotaromflasher-t3741223) for the ROM flasher
Download links for every file needed - https://drive.google.com/open?id=1qkFa9uMWWVWwnF3GS75Pzw6vDQ9GKx6J
Let's get started.
Reboot your device into bootloader mode.
How? ​Method 1​1. Shut down the phone.
2. Hold the volume down button and connect the usb cable connected to your PC.​Method 2 (If device is boot looping)​1. Press and hold power button untill phone reboots.
2. Hold volume up key to boot to e-recovery.
3. Click shutdown.
4. Now follow Method 1.​
Now that you are in bootloader mode,
You may find yourself in one of these three conditions
Condition 1. You read Phone unlock , FRP unlock ( Hurray !! This is the easiest to recover from.)
Condition 2. You read Phone unlock , FRP Lock AND you have TWRP flashed and working. ( Phew , there is still hope!)
Condition 3. You read Phone unlock , FRP Lock AND you have STOCK recovery! (Not sure how you got here, but this method is not tested by me.) (Please text if someone is stuck in this situation. I Will think of something if needed)(Guide is not yet updated with instructions on how to do this yet!)
Steps to recover from condition 1
1. Download stock rom files and stock rom flasher(from here) ( I have updated files for indian version.
Please get the version appropriate to your location.)
2. Extract files into a folder and transfer them to an exteral SD or USB OTG(If you can get it to work. I
Couldn't get my OTG to be detected) and insert it into your phone.
3. Reboot to recovery.
How?​1. Shutdown the deive(Look above for instructions, if needed.)
2. Hold volume up and then simultaniously press the power key.​4. In TWRP, erase everything except micro-sd/otg.
5. Reboot the device into recovery.
6. Flash the zip with the file name "FlashThisZip-DUK_FullOTA_ROM_flasher".
7. Done ! You should now be on Stock Indian oreo rom 8.0.0.323
8. (Optional) Relock bootloader (Check other guids please.)​
Steps to recover from condition 2
1. Download and extract the twrp recovery files i made. ( You may use any stock emui (all partition)
backups you have made!
2. Transer the TWRP folder to External SD / OTG and insert it into the phone.
3. Reboot to recovery.
How?​1. Shutdown the deive(Look above for instructions, if needed.)
2. Hold volume up and then simultaniously press the power key.​4. In TWRP, erase everything except micro-sd/otg.
5. Restore the backup.
6. Done !!! To flash full stock fresh rom, read on.
7. (Optional) Boot up the phone, head into settings, enable developer options and enable OEM unlock.
8. (Optional) Now, simply follow steps from Condition 1(which is above!)​
Guide is still under construction. I got this out as soon as i can to help anyone who is stuck. Please ignore any typos(They will be fixed when i find time to make this guide better).
All the best :good: :fingers-crossed:
---------------------------------------
Guide created on : 10 June, 2018
Last modification : None
Click to expand...
Click to collapse
woaw.. is very well created! it might be handy in any case! thank you
Sent from my DUK-L09 using Tapatalk

Hi, Thanks for the guide.
However, I'm in deep shi*. I'm currently stuck in bootloop, I'm even unable to get to e-recovery. I'm able to get to fastboot though. Even though, I read PHONE Locked and FRP Unlock. What options do I have? I got my bootloader unlock code from EMUI but when I try to unlock bootloader, it says that the password is incorrect..

Check your password
tuniekonematei said:
Hi, Thanks for the guide.
However, I'm in deep shi*. I'm currently stuck in bootloop, I'm even unable to get to e-recovery. I'm able to get to fastboot though. Even though, I read PHONE Locked and FRP Unlock. What options do I have? I got my bootloader unlock code from EMUI but when I try to unlock bootloader, it says that the password is incorrect..
Click to expand...
Click to collapse
Hey,
While i was messing around with my H8P bootloader, i noticed an additional 's' in my password ! Probably while saving it would have got added.
I recommend cross checking if you're actually using the right password. (To the extent that you go through the request process again! Recommend doing this and taking screenshots as after a few days, you will no longer be able to request codes anymore!).
Also, post the error you get while trying to unlock the bootloader.

Anirudh A said:
Hey,
While i was messing around with my H8P bootloader, i noticed an additional 's' in my password ! Probably while saving it would have got added.
I recommend cross checking if you're actually using the right password. (To the extent that you go through the request process again! Recommend doing this and taking screenshots as after a few days, you will no longer be able to request codes anymore!).
Also, post the error you get while trying to unlock the bootloader.
Click to expand...
Click to collapse
Hi Anirudh,
I've gone through the same process several times and every single time I get the same Bootloader Password with the same error when trying to unlock:
{
"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"
}
That's the password Huawei gives me:
(I'm using H8 NON-pro version btw, sorry)

tuniekonematei said:
Hi Anirudh,
I've gone through the same process several times and every single time I get the same Bootloader Password with the same error when trying to unlock:
That's the password Huawei gives me:
(I'm using H8 NON-pro version btw, sorry)
Click to expand...
Click to collapse
Hey. Sorry for the late reply. Before investigating further, any progress?

Anirudh A said:
Hey. Sorry for the late reply. Before investigating further, any progress?
Click to expand...
Click to collapse
Hi,
Eventually I had to pay 15€ for DC Phoenix to be able to flash my Honor. Absolutely nothing helped and none of C434 firmwares worked on C900B131 rollback package, therefore I had to flash C636B130. I received an update to B360 which worked just fine. Then B380 update came which is a nightmare that bricks our phones and the reason I bricked my Honor 8 the first time (back in October of 2017). I had to reflash it through DC Phoenix once again. Later on I tried to move from B360 to B389 which bricked my phone AGAIN. So I am staying on B360 which, I think, works just fine. It is sad that I am unable to get the latest firmware updates but it is what it is. Although I really hate the notification on my Settings icon which informs to update the phone. I disabled all the Updater notifications and so on but it is still there.
I like Honor 8 and I've been always recomending it to everyone but as of now I doubt I'll ever buy Huawei phone again.

tuniekonematei said:
Hi,
Eventually I had to pay 15€ for DC Phoenix to be able to flash my Honor. Absolutely nothing helped and none of C434 firmwares worked on C900B131 rollback package, therefore I had to flash C636B130. I received an update to B360 which worked just fine. Then B380 update came which is a nightmare that bricks our phones and the reason I bricked my Honor 8 the first time (back in October of 2017). I had to reflash it through DC Phoenix once again. Later on I tried to move from B360 to B389 which bricked my phone AGAIN. So I am staying on B360 which, I think, works just fine. It is sad that I am unable to get the latest firmware updates but it is what it is. Although I really hate the notification on my Settings icon which informs to update the phone. I disabled all the Updater notifications and so on but it is still there.
I like Honor 8 and I've been always recomending it to everyone but as of now I doubt I'll ever buy Huawei phone again.
Click to expand...
Click to collapse
DC Phoenix always to the rescue. Unfortunately , this is the sad state of Huawei/Honor . Your device should be fixed free , because of Honors fault. Now that they're also not giving out unlock codes after a month , it's a direct screw you to all the advanced users. There's no predicting how this gamble will play out for them. I'm also not going to recommend Huawei /Honor to any advanced users . One plus has my money. However , Huaweis midrangers and just about OK for regular use.

i just restore your backup now stuck with bootloop frp lock phone lock

jazzy ╰_╯ said:
i just restore your backup now stuck with bootloop frp lock phone lock
Click to expand...
Click to collapse
Ensure your phone varient is what is specified in this thread. Phone lock is impossible. Please mention condition before, steps taken.

jazzy ╰_╯ said:
i just restore your backup now stuck with bootloop frp lock phone lock
Click to expand...
Click to collapse
Also, try factory reset, with data erase

Anirudh A said:
Ensure your phone varient is what is specified in this thread. Phone lock is impossible. Please mention condition before, steps taken.
Click to expand...
Click to collapse
i was on condition 2 i formated the phone as you said and downloaded twrp back up when i restored the back the first boot took me to erecovery then i try to go to twrp but it was gone i booted into fastboot and saw that phone is locked frp is lock stuck with bootloop ( which boots up my device to erecovery again and again) i do have an indian varient and was already on mm it was just that i had rooted device with magisk where i was not able to pass safenet so i thought to unroot it to stock and reroot again
---------- Post added at 01:52 AM ---------- Previous post was at 01:51 AM ----------
Anirudh A said:
Also, try factory reset, with data erase
Click to expand...
Click to collapse
already tried nothing happen

Anirudh A said:
Also, try factory reset, with data erase
Click to expand...
Click to collapse
are you going to help me out

jazzy ╰_╯ said:
i was on condition 2 i formated the phone as you said and downloaded twrp back up when i restored the back the first boot took me to erecovery then i try to go to twrp but it was gone i booted into fastboot and saw that phone is locked frp is lock stuck with bootloop ( which boots up my device to erecovery again and again) i do have an indian varient and was already on mm it was just that i had rooted device with magisk where i was not able to pass safenet so i thought to unroot it to stock and reroot again
---------- Post added at 01:52 AM ---------- Previous post was at 01:51 AM ----------
already tried nothing happen
Click to expand...
Click to collapse
Got it repaired by service center even though I want to do it by myself

jazzy ╰_╯ said:
Got it repaired by service center even though I want to do it by myself
Click to expand...
Click to collapse
Yikes. Is yours an Indian Honor 8 pro ?

jazzy ╰_╯ said:
Got it repaired by service center even though I want to do it by myself
Click to expand...
Click to collapse
Yikes. Is yours an Indian Honor 8 pro ?

I am stuck with condition 3. I have flashed project treble, but i wanted to revert back to stock so flashed stock ramdisk.img and my phone is showing phone unlock and frp lock. i can boot into the treble rr rom, but i want to revert back to stock emui. what should i do?

rhijuloves said:
I am stuck with condition 3. I have flashed project treble, but i wanted to revert back to stock so flashed stock ramdisk.img and my phone is showing phone unlock and frp lock. i can boot into the treble rr rom, but i want to revert back to stock emui. what should i do?
Click to expand...
Click to collapse
First thing, go to developer options and enable oem unlocking.. DO NOT FLASH/ DO ANYTHING BEFORE THIS STEP. Then you'll be on condition 1 so you can follow those steps.

Anirudh A said:
First thing, go to developer options and enable oem unlocking.. DO NOT FLASH/ DO ANYTHING BEFORE THIS STEP. Then you'll be on condition 1 so you can follow those steps.
Click to expand...
Click to collapse
can't change oem unlocking, it says bootloader unlocked. Kindly help me.

rhijuloves said:
can't change oem unlocking, it says bootloader unlocked. Kindly help me.
Click to expand...
Click to collapse
Bootloader and frp unlock are different and are independent of each other.Turn on your internet/connect to one and then try oem unlocking. Also, share the screenshot of the oem unlock screen.

Le pro 3 x720 brick?

Hi, since yesterday I have a big problem with my le pro 3, while charging the phone suddenly turned off. The system did not want to turn on, so I went into recovery (TWRP) and tried to format and upload a new rom, unfortunately during the flashing, a blue screen appeared. When changing the kernel, the flashing of the rom was done, but with the installation of the gapps it hung. I tried to install another rom, but it also spilled, with this addition, that I can not enter recovery, because artifacts appear or reboots.. Only fastboot works. With it, I tried to flash the kernel, recovery, but it did not do anything. I also used (TOOL ALL in ONE) and uploaded the stock rom, but the phone still does not work. Do you know what else could help, or is buying a new phone? Thanks for help

If you can use fast boot, your phone is not hard bricked. A brick is when you can not do anything , you will have a black screen and a red blinking light if a usb cable is connected.
Try pushing Twrp ( newest version) to the phone. If that is successful boot to recovery, fully wipe your phone, reboot to recovery and install you Rom> Gapps, and Magisk. I would suggest initially flashing Lineage 15.1. Once your phone is restored, flash whatever you would like.
If it doesn't work try another cable, or another port, or another computer. Computer needs to be up to date and you may need to temporarily disable antivirus, if the All in One tool isn't working its likely that your computer is blocking the install. especially if you are using Windows 10. All the program to be open within your firewall settings. Make sure its up to date and use AIO to update android drivers and adb.

I'm not giving anything, I still can't get into recovery

miichus said:
I'm not giving anything, I still can't get into recovery
Click to expand...
Click to collapse
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4

tsongming said:
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4
Click to expand...
Click to collapse
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot

miichus said:
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot
Click to expand...
Click to collapse
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?

tsongming said:
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?
Click to expand...
Click to collapse
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.

miichus said:
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.
Click to expand...
Click to collapse
For the second time I tried to use flashOne
Click to expand...
Click to collapse
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121

tsongming said:
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Click to expand...
Click to collapse
I am using flashone 2.0 and flashing from your link, the file "le_zl1_qfil_ufs_fix.zip". Port 9008 is open. After three flash in 2.0 flash, I could enter recovery, but when flashing custom rom, a blue screen appeared.

Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs

tsongming said:
Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.

miichus said:
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.
Click to expand...
Click to collapse
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html

tsongming said:
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
Click to expand...
Click to collapse
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance

mavelino said:
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance
Click to expand...
Click to collapse
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.

tsongming said:
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.
Click to expand...
Click to collapse
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance

mavelino said:
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance
Click to expand...
Click to collapse
All I have is in the link you just responded to.
if that doesn't work try unpacking the Qfil and and see if you can just extract them.
I will look further when I get back home.

i also have an bricked LEX 3 Pro . i bought it as an X722 but of cause iam not shure . could also be an X720. i can not find the difference.
so Phone has only fastboot.
when i plug in usb cable it just reboot every 10 sec . no charging sreen appears
i flash Qfil, but not helped it stay the same

"Device is corrupt" HELP!

I was just trying to install the 9.0.6 update manually following the instructions in the thread for it here on xda and it wouldn't work. I uninstalled magisk and restored images through magisk manager as the directions stated to do. I couldn't get the update to show in the local upgrade section under system update so decided to reboot to see if that would fix it but now my phone will not boot. It goes to a screen that says my device is corrupt and won't go past that. It says to hit the power button to continue but that just makes it boot back to that screen and if I just wait the phone shuts off.
Any help is appreciated.
(UPDATE) Thanks for the help guys. I got the phone booting again by flashing the 9.0.6 ROM in fastboot. I'm still getting the "device is corrupt" message and have to hit the power button twice to get it to boot so if anyone knows a fix for this I would appreciate it. At least I can use the phone now.

imucarmen said:
I was just trying to install the 9.0.6 update manually following the instructions in the thread for it here on xda and it wouldn't work. I uninstalled magisk and restored images through magisk manager as the directions stated to do. I couldn't get the update to show in the local upgrade section under system update so decided to reboot to see if that would fix it but now my phone will not boot. It goes to a screen that says my device is corrupt and won't go past that. It says to hit the power button to continue but that just makes it boot back to that screen and if I just wait the phone shuts off.
Any help is appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6t/how-to/tool-t-mobile-oneplus-6t-msmdownloadtool-t3868916
Worked for me. Unzip to a folder....run it.....with phone off press and hold all 3 buttons......it will find device.... press start.....Yahtzee....hope this helped

imucarmen said:
I was just trying to install the 9.0.6 update manually following the instructions in the thread for it here on xda and it wouldn't work. I uninstalled magisk and restored images through magisk manager as the directions stated to do. I couldn't get the update to show in the local upgrade section under system update so decided to reboot to see if that would fix it but now my phone will not boot. It goes to a screen that says my device is corrupt and won't go past that. It says to hit the power button to continue but that just makes it boot back to that screen and if I just wait the phone shuts off.
Any help is appreciated.
Click to expand...
Click to collapse
Are you able to boot into fastboot?

mang0 said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
Yes.

mang0 said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
Mine wouldn't boot into anything....said hardware/software mismatch.

headcreepz said:
https://forum.xda-developers.com/oneplus-6t/how-to/tool-t-mobile-oneplus-6t-msmdownloadtool-t3868916
Worked for me. Unzip to a folder....run it.....with phone off press and hold all 3 buttons......it will find device.... press start.....Yahtzee....hope this helped
Click to expand...
Click to collapse
That says it's for the T Mobile version only. I have the global version.

imucarmen said:
That says it's for the T Mobile version only. I have the global version.
Click to expand...
Click to collapse
Shoot...sorry
There is one on here for international.....look in guides
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448

imucarmen said:
Yes.
Click to expand...
Click to collapse
You could try to use msm download tool linked above or flash the full rom again since you can get into fastboot. I'd prob try that before the msm tool though.

mang0 said:
You could try to use msm download tool linked above or flash the full rom again since you can get into fastboot. I'd prob try that before the msm tool though.
Click to expand...
Click to collapse
do you have any instructions on how to go about flashing a rom in fastboot? I've never done it before.

imucarmen said:
do you have any instructions on how to go about flashing a rom in fastboot? I've never done it before.
Click to expand...
Click to collapse
Check this link
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

imucarmen said:
do you have any instructions on how to go about flashing a rom in fastboot? I've never done it before.
Click to expand...
Click to collapse
Just download full zip of fastboot rom, extract into a folder, connect you phone in fastbbot mode and run flash all bat file.
You can find all in this thread:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

VampireHeart said:
Just download full zip of fastboot rom, extract into a folder, connect you phone in fastbbot mode and run flash all bat file.
You can find all in this thread:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Thanks. I got that part and was able to get my phone booting again but I still get the corrupt device message when I start the phone. Wish I knew how to get rid of it. IS there any return to full stock methods that also locked the bootloader and restore all partitions to stock? That is the only thing I can think of that might work.

imucarmen said:
Thanks. I got that part and was able to get my phone booting again but I still get the corrupt device message when I start the phone. Wish I knew how to get rid of it. IS there any return to full stock methods that also locked the bootloader and restore all partitions to stock? That is the only thing I can think of that might work.
Click to expand...
Click to collapse
Someone say that wiping all with stock recovery solved, but device work fine also whit that message, otherwise you can try MSM Download Tool, it will restore all stock to 9.0.5 with locked bootloader.

imucarmen said:
Thanks. I got that part and was able to get my phone booting again but I still get the corrupt device message when I start the phone. Wish I knew how to get rid of it. IS there any return to full stock methods that also locked the bootloader and restore all partitions to stock? That is the only thing I can think of that might work.
Click to expand...
Click to collapse
Use the MSMDownloadTool for the international version, it's the only way to bypass the verity trigger, it will restore the device to full stock as if you never unlocked the bootloader to begin with.

VampireHeart said:
Someone say that wiping all with stock recovery solved, but device work fine also whit that message, otherwise you can try MSM Download Tool, it will restore all stock to 9.0.5 with locked bootloader.
Click to expand...
Click to collapse
Dark Nightmare said:
Use the MSMDownloadTool for the international version, it's the only way to bypass the verity trigger, it will restore the device to full stock as if you never unlocked the bootloader to begin with.
Click to expand...
Click to collapse
Thanks guys. I will try this out in the future. For now I'm just going to ride with what I got since I don't feel like setting my phone up again. I don't reboot much so it shouldn't bother me too bad. I guess it's good I learned something new.

Dark Nightmare said:
Use the MSMDownloadTool for the international version, it's the only way to bypass the verity trigger, it will restore the device to full stock as if you never unlocked the bootloader to begin with.
Click to expand...
Click to collapse
Can you provide me a link? The only MSMDownloadTool I see says it's only for the T-Mobile version. Thanks.

imucarmen said:
Can you provide me a link? The only MSMDownloadTool I see says it's only for the T-Mobile version. Thanks.
Click to expand...
Click to collapse
Msm download tool for int : https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448

Just paste this in terminal and device is corrupt message will be gone
su
Reboot "dm-verity enforcing"
Hit enter
Enjoy

[email protected] said:
Just paste this in terminal and device is corrupt message will be gone
su
Reboot "dm-verity enforcing"
Hit enter
Enjoy
Click to expand...
Click to collapse
Yep this should do the trick. It worked for me!

[email protected] said:
Just paste this in terminal and device is corrupt message will be gone
su
Reboot "dm-verity enforcing"
Hit enter
Enjoy
Click to expand...
Click to collapse
I keep getting this error and I typing it wrong?