Database Develop

Stuck in Oneplus logo. Can't access recovery. Fastboot working.

Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.

Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.

rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.

Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?

rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can

Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS

rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear

Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here

rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway

Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!

rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..

nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working

Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?

pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer

Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.

przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.

Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.

redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)

Oreo TWRP Backup needed

Hello
I have bricked my p10. I think backup from working device would be fix it. Probably a lot of people use emui 8 so. I need help
Someone Can upload? I tried really everything

I can try backup from nougat as well, someone could help me with this guys?
Please.

no nothing yet, you can try kingroot and flashify.

ure3808 said:
no nothing yet, you can try kingroot and flashify.
Click to expand...
Click to collapse
I'm rooted, i've got recovery. Now i'm without OS and nothing work.
It's possible to remove and recreate partitions? i cant flash nougat, cuz partitions like... "recovery" "boot" doesn't exist( in oreo boot.img = ramdisk.img, recovery.img = recovery_ramdisk.img) ehh

Did you try this?
If TWRP works than this should work, too.
When you're on Oreo use Tutorial #2.

Jannomag said:
Did you try this?
If TWRP works than this should work, too.
When you're on Oreo use Tutorial #2.
Click to expand...
Click to collapse
Yes, I tried this few days ago..
Tap on oreoupdate.zip and install it.
Click to expand...
Click to collapse
I clicked this file, looked like it was supposed to be installed but I knew the phone has been rebooted too fast.. and I was right, after reboot didn't install update from eRecovery, just start twrp and that's all..

You need Update.APP 8.0.0.360 decompile, use 3 img files, boot, system, vendor, and use fastboot commands.

I said, i tried many methods and no one was good. I flash correct .IMG's via fastboot ( by information from cmd of course ). After flash i reboot to recovery( twrp) and I saw, in partition /system takes some GB so i tried to boot normally but still didn't work, 1st information after reboot - "DEVICE IS NOT TRUSTED" or something like that ( cuz bootloader is unlocked ) after few seconds, system should boot, but it's stuck for while on 1st screen like I said, and then did reboot to eRecovery so..

It's possible to damage bootloader as much.. ?

How many people bricked their phone while Rebranding/OTA and what solutions used ?

How many people bricked specifically hardbricked their phone after 2018-04-16 updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if they see we are bunch of people.
Edit: Just comment only if you solved the issue with this tool or any other tool that is not mentioned,here we are seeking help.

reza6d said:
How many people bricked specifically hardbricked their phone after 2018-04-16 noxloader updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if the ysee we are bunch of people.
Click to expand...
Click to collapse
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.

ante0 said:
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
Click to expand...
Click to collapse
maybe i recall wrong but after first time seeing these noxloaders,somethings changed,anyway i edited the post.thanks.

My BLA-L29 is still on the black screen and I can not even revert to DC-Phoenix. After upgrading to 138.

Used funky

mikaole said:
Used funky
Click to expand...
Click to collapse
i think your phone was in fastboot or bootloop,we are talking about hardbrick bro,black screen not even charge led in our devices.

I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.

Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know

durc12 said:
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
Click to expand...
Click to collapse
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions

Carnage! said:
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Click to expand...
Click to collapse
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.

Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
I see. I only tried flashing the recovery_ramdisk and system.img. I will try it later and I will let you know if it worked.

Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS

durc12 said:
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
Click to expand...
Click to collapse
No, first he has to recover the current OS, and my advise was only for that.
Then he will need to use a TWRP + NoCheck combo, to get back to Oreo.
HuRUpdater can't get you back to Oreo so you guys should stop using that with Pie.

Mate 10 Pro BLA-L09
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.

diowil4 said:
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
Click to expand...
Click to collapse
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?

Pretoriano80 said:
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Click to expand...
Click to collapse
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK

diowil4 said:
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Click to expand...
Click to collapse
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.

Pretoriano80 said:
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Click to expand...
Click to collapse
After flashing It cannot boot to recovery.

diowil4 said:
After flashing It cannot boot to recovery.
Click to expand...
Click to collapse
So you can only boot to fastboot, no matter what?

Pretoriano80 said:
So you can only boot to fastboot, no matter what?
Click to expand...
Click to collapse
Yes.

flashing rom via TWRP with frp lock?

Hi, I'm in a bad situation. My honor 9 lite (Europe) has no OS, frp lock. But it does have TWRP installed.
My question would be, since I can't flash an OS (given the frp lock) via fastboot, would it work via TWRP? Or should I just give up and buy a new phone?
Thanks a lot.
Best

Since you have TWRP, try using HURUpdater tool. It is compatible with H9L.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279

BS4388 said:
Since you have TWRP, try using HURUpdater tool. It is compatible with H9L.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Hi,
thanks a lot for the tip. Unfortunately, I keep getting an error when flashing following the instructions.
I discovered that nonetheless I can flash roms with TWRP. There is one particular rom, this one https://forum.xda-developers.com/honor-view-10/development/rom-t3753555 that works particularly.
However, my device with that rom keeps giving me an error "bluetooth keeps stopping". Any way to solve that?

I really don't know a solution.
Can't you enable OEM unlock in settings/developer options? so that to make frp unlocked?

Yes.
After that, I was able to finally flash stock rom
However, there's a new issue: wifi doesn't work. It actually seems like whatever rom I flash, wifi won't work the slider turns off as soon as I turn it on

Did you wipe data/factory reset through eRecovery after flashing? That is important in most cases!

BS4388 said:
Did you wipe data/factory reset through eRecovery after flashing? That is important in most cases!
Click to expand...
Click to collapse
No I did not. I think I used TWRP to do that. Will do with eRecovery next time and update you

I am still without WiFi.
I think the problem lies in the fact that my stock ROM comes from here: https://forum.xda-developers.com/9-lite/how-to/guide-unbrick-device-recover-bootloop-t3772563
I had oreo 8.1 before brick, and the rim above that I flashed is 8.0 and Indian version (not european). That maybe could explain the issue.
Problem is, I would need a system.img stock ROM to file and I can't seems to find that. In Huawei firmware finder, I only get update.zip kind of files and TRWP returns error when flashing that or when I use the HuRUpdater tool.
Also, I've noticed it's not just the WiFi, but also security options and themes for some reason

you need a working frp image which in twrp can flashed via dd... so the frp lock is gone...
In telegram group you can find image.

gabfur01 said:
I am still without WiFi.
I think the problem lies in the fact that my stock ROM comes from here: https://forum.xda-developers.com/9-lite/how-to/guide-unbrick-device-recover-bootloop-t3772563
I had oreo 8.1 before brick, and the rim above that I flashed is 8.0 and Indian version (not european). That maybe could explain the issue.
Problem is, I would need a system.img stock ROM to file and I can't seems to find that. In Huawei firmware finder, I only get update.zip kind of files and TRWP returns error when flashing that or when I use the HuRUpdater tool.
Also, I've noticed it's not just the WiFi, but also security options and themes for some reason
Click to expand...
Click to collapse
The system.app file you search for is in the update.zip file you get and you cannot flash update.zip directly from twrp, you need HuRupdater for that and the dload method doesn't work for almost anyone including me.
And you need correct the firmware for your motherboard if you want your phone to work properly.
First tick oem unlocking in developer options. Then unlock fastboot and flash TWRP.
Since you are able to boot up check your varient, the complete one not just the LLD but the rest too. Search for it in Huawei firmware finder and download the latest firmware for your model. You'll get 3 links and you'll need all three.
Download HuRupdater 0.3 zip and then rename the 3 files you got as told in the HuRu instructions. get twrp image and rename it to recovery.img and put all files in the same folder.If you want to completely revert to stock you don't have to have recovery.img but keep it just in case.
Then flash HuRupdater using twrp. You should be up and running if you did everything right.
You can then remove the recovery.img and then flash again using HuRupdater and relock the fastboot too later if you wanna play things safe using fastboot relock bootloader 'your code' .

please help me, honor 9 lite last night my flash rom forgot the data format so now can not boot into the operating system, locked FRP, can not enter the TWRP.

Hello, I know it's been a long time. I put the issue aside for a few months as I had another phone to use in the meanwhile just wanted to let you know i Just did the procedure you described and it worked perfectly! The phone is back to life :laugh:

Flashed android pie firmware and now bricked my device need your help guys

my variant is LLD-L21C185 and i did the most stupid thing I flashed a pie firmware which was for LLD-L21C636 and now i am stuck with bricked phone.
bootloader : unlocked
frp: unlocked
Fastboot mode is accessible
I tried to flash twrp with command fastboot flash recovery_ramdisk twrp.img result is sucessful but i can not load it.
it loads with stock recovery no matter what.
normal start is loading erecovery
i tried to download oreo rom (lld-l21c185b138) from erecovery but update fails at 5% every time.
i also tried the dload method with sd card but did not succeed .
can anybody tell me a way to get back to oreo with fastboot commands.

try fastboot reboot recovery, or fastboot boot twrp.img

Try to flash manually this files from oreo firmware: system. img, ramdisk. img and kernel. img via fastboot

wetito said:
Try to flash manually this files from oreo firmware: system. img, ramdisk. img and kernel. img via fastboot
Click to expand...
Click to collapse
do i have to flash them in this particular order??
extracted from oreo update.app (lld-l21c185b138)
i tried fastboot flash system SYSTEM.img and it says can not open system.img
i tried flashing ramdisk img with fastboot flash ramdisk RAMKDISK.img and i get remote: partition length get error
however fastboot flash kernel KERNEL.img flashes successfully

Now are you with EMUI 9?
Bilal.151 said:
my variant is LLD-L21C185 and i did the most stupid thing I flashed a pie firmware which was for LLD-L21C636 and now i am stuck with bricked phone.
bootloader : unlocked
frp: unlocked
Fastboot mode is accessible
I tried to flash twrp with command fastboot flash recovery_ramdisk twrp.img result is sucessful but i can not load it.
it loads with stock recovery no matter what.
normal start is loading erecovery
i tried to download oreo rom (lld-l21c185b138) from erecovery but update fails at 5% every time.
i also tried the dload method with sd card but did not succeed .
can anybody tell me a way to get back to oreo with fastboot commands.
Click to expand...
Click to collapse
Have you flashed Pie rom of GSI or EMUI based? If its EMUI based some partitions have changed from EMUI 8.0 to 9.0

excelly2k1 said:
Have you flashed Pie rom of GSI or EMUI based? If its EMUI based some partitions have changed from EMUI 8.0 to 9.0
Click to expand...
Click to collapse
yes now i am with emui 9
i flashed emui9 based pie firmware............... i think you are right partitions have been changed with pie and maybe that is why i can not flash ramdisk img.......... is there any way to restore the partitions to the way they were before so oreo firmware can be flashed????

Did you tried hisuite to recover the phone?

PAPalinskie said:
Did you tried hisuite to recover the phone?
Click to expand...
Click to collapse
i tried almost everything but it says model not supported.
i took it to the local shop and the guy said partitions are damaged thats why oreo firmware is not flashing....
i need to know is there any way to repair the partition so that i can be ready flash oreo again

First off starting another thread about the same issue is never a good idea and is not in keeping with forum etiquette . https://forum.xda-developers.com/9-lite/help/how-to-repair-ramdisk-partition-t3923406
IMHO you will not repair this phone without testpoint flashing using IDT and board software.
Google it, not too hard but not for the feint hearted either, requires opening the phone to 'earth' the testpoint for flashing.

Sparkrite said:
First off starting another thread about the same issue is never a good idea and is not in keeping with forum etiquette . https://forum.xda-developers.com/9-lite/help/how-to-repair-ramdisk-partition-t3923406
IMHO you will not repair this phone without testpoint flashing using IDT and board software.
Google it, not too hard but not for the feint hearted either, requires opening the phone to 'earth' the testpoint for flashing.
Click to expand...
Click to collapse
I guess you are right the only way to fix this is to flash test point...................... my phone is still under warranty period.......... should I sent it to them or should I get it open and repair from local shop?
and how can I delete my duplicate thread

Ask a moderator to remove it.

New user here, so unable to post link, maybe this help for you, tool are edited to adjusting needed to Unbrick and Downgrade.
mega.nz/#!jREhlCaS!WyphdD-vDr5-OGvXxukOrxW80hyThg_vrAYLh32izh0

Adhy 18 said:
New user here, so unable to post link, maybe this help for you, tool are edited to adjusting needed to Unbrick and Downgrade.
mega.nz/#!jREhlCaS!WyphdD-vDr5-OGvXxukOrxW80hyThg_vrAYLh32izh0
Click to expand...
Click to collapse
I tried but it did not worked
I send it to honor repair service center and now its good as new again :fingers-crossed::fingers-crossed:

after sending it to honor service center the phone is back to life and working fine but I noticed that both imei number and Serial number are changed and bootloader is locked again. My previously saved bootlaoder unlock code is not working to unlock bootloader. What could be reason behind changing the imei number and serial number ? does anybody knows about it?

Bilal.151 said:
after sending it to honor service center the phone is back to life and working fine but I noticed that both imei number and Serial number are changed and bootloader is locked again. My previously saved bootlaoder unlock code is not working to unlock bootloader. What could be reason behind changing the imei number and serial number ? does anybody knows about it?
Click to expand...
Click to collapse
More than likely they just changed the motherboard, same case but different guts, so to speak.
Cheapest and fastest way out for them.