Database Develop

Bricked mate s

PLEASE help : My phone stopped working after trying to change it to a L09 and now is dependent on the company's logo and does not accept any Software

You need to read about flashing from the bootloader using fastboot. You will be able to get it back working but you will need to get an extracted rom to flash the right parts.

Now I have a bit of time, I will tell you how I solved my issues. My phone was stuck with only the bootloader screen available or the eRecovery screen which would not find any suitable download. It said that the bootloader was unlocked yet I could not flash anything that I have extracted using the ROM extractor.
After much frustration I opened and ADB session and used Fastboot commands and re-entered the number in the Fastboot OEM Unlock command and it then confirmed that it was actually unlocked. It seems that although it said it was, it really wasn't.
Now that I knew it was unlocked, I could now start to flash parts of the extracted ROM.
I used the Huawei Rom Extractor tool to extract the Boot, Cache, Cust, Recovery, System and the Userdata image files of the ROM I needed and in this case it was the CRR-UL00470B110. I renamed the extracted files and removed the prefix numbers and put them in the ADB folder for ease of flashing.
I then used the Fastboot command to flash each part in the normal Fastboot format i.e. - Fastboot flash system system.img , and so on for each part. A reboot after brings it up in a nice new live usable phone. Well that is what I thought until I started to load the apps back on. I then noticed that I only had about 3gb left of my 64gb of memory! This took me a while to resolve and after more reading, more flashing of different ROMs I found the answer.
I had to flash the TWRP recovery using Fastboot, then format the data partition from TWRP. This restored the full size of the partition. Another flash of the correct recovery using Fastboot left me with a fully working unbricked Mate S.
I know that some of you may know all about this but I could not find any information and had to work through it myself and from various websites. I hope that this will help you to unbrick your phone.
I still think there may be something missing like the oeminfo file etc. but at least it works, you may just have to update it in future using adb and Fastboot if no OTA is available or works. Not too much of a worry now you know how to do it.

I should also add that if you ever get an 'Invalid Argument' when flashing in fastboot mode and some oparts flash while others dont, it will be your cable. Trust me, one cable workws well another gives you this Invalid Argument error! Strange but true and may catch you out.

Thank you(Sathelp) to help me to solve the problem of mate s mobile, but I found only three orders adb work when used fastboot screen, there are boot, recovery and cust but the system and other order give fault result in adb. Therefore the phone remain broken. ..sorry for language

Is it possible to provide me a complete backup copy of the phone to be downloaded to my phone via the twrp recovery , perhaps back to life again, I would be grateful to you

my p[hone is a U00 not a L09, so my back up will not work. Have you changed your cable, I had simular problem, changed cable and other ROM parts worked OK. If not, then you will need to ask for a L09 TWRP back up from here. May be someopne will make one for you.

Finally, the problem has been resolved and the phone returned to work and all this is due to the help of (Sathelp), which benefited greatly from his observations in this matter ,the issue has been resolved by updating the ADB and the execution of an order (FASTBOOT FLASH SYSTEM.IMG) , which i could not be implemented except adb updated, but the phone remained unresponsive for OTA updates and remained on the android 5. Thank to xda forums.

Glad it is now working

Huawei Mate S CRR-L09 bricked
Hi
I have a Huawei Mate S (CRR-L09) does not work and remains stuck on the android logo. Mention that is installed TWRP and I tried to "wipe data factory reset". I accidentally erased everything on it, including Systema. I did not back up your data and restore the system. I downloaded firmware B145 stock on which I copied to root your phone but, but can not flash TWRP. I entered the menu Update (Vol + Vol- and Power) but does not see that folder "dload". Can someone help me with a backup or a tutorial on how to flash TWRP firmware.
Thank you

Unbrick P9 single sim (using DC Phoenix)

There are many cases of people recovering their bricked phones but their solutions arent so clear when browsing the thread. For example, threads get abandoned once their phone was recovered, leaving people like me confused or stranded. I decided after days of trying to recover my phone share what I did to revive my P9. I hope this can help you.
Disclaimer***
- DC Phoenix costs 15 euros for 15 credits to use for 72h after initial flash (small price to pay compared to sending to repair shop or having a useless brick).
- i am NOT responsible for what you do to your phone if it broke
- this is what worked for ME, but im confident it would work for yours but no guarantees
- please read as it might give you some background information
- Bootloader code changes
- serial number resets to ABCDEF012345678
As most people on XDA, we like to flash stuff on to our phones. I was on EMUI 4.1 MM and I wanted to update to EMUI 5 Nougat. I did so successfully by installing twrp, flashing C432 oem info, and flashing B136 via SD card force update, and then using software update in the settings app to B182. Finally, I managed to flash B361 nougat via HuaweiUpdater2.0 and HiSuite.
Then, I decided to try and root my P9 but somewhere along the way, which I cant remember, I flashed the wrong recovery or something and my phone wouldn't boot - it was stuck at the huawei boot logo. I panicked and tried doing all these things using SRK tools, and HiSuite recovery mode, and eventually I was left with a super hard bricked P9. And for the next 3 days I tried all sorts of stuff to recover my phone. I really think I had tried everything (except sending to repair shop). Believe me, I think I had all of the symptoms of everyone in other threads along the way of trying to recovery it. I downloaded about 4 - 6 firmware files just trying to flash and flash but it kept being stuck at 5% or some error. I even bought the 15 euro credit to use DC Phoenix, which allowed me to flash the firmwares but it didn't change anything besides making my semi brick to brick again vice versa.. Nothing seemed to work. This was using Method 1 in their unbricking guide.
What worked.
There was a second method in the DC Phoenix unbricking guide, but the reason I didn't consider this method is because it required me to flash my P9's image file (.dgtks file) which seemingly can only be downloaded from DC Phoenix's download page (searched everywhere but nada). There is only the P9 Dual SIM image file, and I was afraid that this would have been very bad to flash. But in the end I had no real choice cause my warranty was void when I'd unlocked my bootloader.
Here's what I did:
Using DC Phoenix's guide, follow the steps for method 2.
When the guide points you to downloading the image file, find the image for EVA-AL10 (P9 Dual SIM) and flash it.
I followed the exact steps in the guide for method 2. *dont forget to remove your sd card during the process*
Once the flashing has finished, it should boot up briefly to encrypt the storage and reboot into update install screen. If not, then the phone should be fully booted up. There are no themes or any useful apps at this stage.
At this point you must flash your desired firmware using the force update method.
Simple - copy the dload folder of your firmware on to your sd card. On the home screen of your phone, there should be a tool (sorry i cant remember which) and once opened to have an option to force update via sd card. click that and you should be all good with your working phone. In my case, I wanted to flash the firmware EVA-L09C432B136. I copied its contents into the sdcards dload and flashed it without a hitch (i even got ota updates).
Please ask questions if you are unsure because I've probably missed some important stuff.
EDIT:
After flashing with DC Phoenix, for some reason the serial number becomes ABCDEF0123456789, and the bootloader unlock code changes, so the code is different from what you would get from the Huawei bootloader code

Thanks ever so much for above. I was bricked into a corner for the last day or so!

You are a life saver. I had accidentally installed the NRD90M test-keys version of Android N. Caused all sorts of issues. One of the issues with NRD90M was the fact there was no keyboard installed. I relied on google voice. When it restarted it wanted to be reactivated against my google account. FRP Lock had enabled itself. I used a USB A to USB C adapter and physically connected a computer keyboard and was able to enter credentials. I used DC Phoenix to flash the EVA-AL10 firmware as you did. I then used their HCU software to change my vender and country to hw,eu. After doing that I had to use DC Phoenix again to reflash EVA-AL10. Once reflashed I used the Software app on the phone to install VIE-L09C432B180 from the SD Card. I am now all working with Android M using a C432 (eu) firmware on a New Zealand Huawei P9 Plus. I should be able to install Android N now OTF. Thanks for your detailed post.

Question: so moodie007, do you confirm me: on P9 PLUS you flashed at the start the AL10 version of the "standard" P9 ?
It's not clear:
Once reflashed I used the Software app on the phone to install VIE-L09C432B180 from the SD Card
Click to expand...
Click to collapse
What software app did you used to install that firmware? the standard eRecovery (Vol+ Vol - Pwr buttons?)

Thank you so much, you literally saved my life.

what is the DC Phoenix,is it the same as the sd card?

moodie007 said:
You are a life saver. I had accidentally installed the NRD90M test-keys version of Android N. Caused all sorts of issues. One of the issues with NRD90M was the fact there was no keyboard installed. I relied on google voice. When it restarted it wanted to be reactivated against my google account. FRP Lock had enabled itself. I used a USB A to USB C adapter and physically connected a computer keyboard and was able to enter credentials. I used DC Phoenix to flash the EVA-AL10 firmware as you did. I then used their HCU software to change my vender and country to hw,eu. After doing that I had to use DC Phoenix again to reflash EVA-AL10. Once reflashed I used the Software app on the phone to install VIE-L09C432B180 from the SD Card. I am now all working with Android M using a C432 (eu) firmware on a New Zealand Huawei P9 Plus. I should be able to install Android N now OTF. Thanks for your detailed post.
Click to expand...
Click to collapse
can you give me a username and code,I'm in china,I cannot buy it use Alipay .and my phone is bricked,would help me,thx.

Hmm i think my phone is bricked, im unable to get into the menu to update the Update.app file from the dload folder on the SD card, i cant even get the phone to switch off it just keeps restarting itself and freezing on the 'your device has been unlocked and cant be trusted' screen....
{
"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"
}
if i try and turn the phone of it just turns itself back on and freezes on that screen again
Im able to get to the Fastboot & recovery mode screen if i hold volume down button.......
and if i hold down both the volume and power buttons i get this screen....
and not the firmware update screen i should be getting.
It has been suggested that i need to use DC Phoenix program to fix the phone but will this work seeings as i cant even get the phone to boot or even switch off??

BlockABoots said:
Hmm i think my phone is bricked, im unable to get into the menu to update the Update.app file from the dload folder on the SD card, i cant even get the phone to switch off it just keeps restarting itself and freezing on the 'your device has been unlocked and cant be trusted' screen....

if i try and turn the phone of it just turns itself back on and freezes on that screen again
Im able to get to the Fastboot & recovery mode screen if i hold volume down button.......

and if i hold down both the volume and power buttons i get this screen....
if i try and turn the phone of it just turns itself back on and freezes on that screen again
Im able to get to the Fastboot & recovery mode screen if i hold volume down button.......

and if i hold down both the volume and power buttons i get this screen....

and not the firmware update screen i should be getting.
It has been suggested that i need to use DC Phoenix program to fix the phone but will this work seeings as i cant even get the phone to boot or even switch off??
Click to expand...
Click to collapse
Install twrp through fastboot. Go into twrp. From there you can find a fix for your phone. You can install oeminfo and flash ROM. Good luck

rhodondendron said:
Install twrp through fastboot. Go into twrp. From there you can find a fix for your phone. You can install oeminfo and flash ROM. Good luck
Click to expand...
Click to collapse
Does twrp work with Nougat fw then, as i thought it didnt??

BlockABoots said:
Does twrp work with Nougat fw then, as i thought it didnt??
Click to expand...
Click to collapse
Yes...
But boot in dl mode with power +- and stay ....BUT REMOVE CABLE.....

rayman95 said:
Yes...
But boot in dl mode with power +- and stay ....BUT REMOVE CABLE.....
Click to expand...
Click to collapse
Holding the power and volume buttons doesnt boot me into the force update screen though, instead i get this screen....

Try to install twrp in fastboot and reboot immediately without the cable...

BlockABoots said:
Does twrp work with Nougat fw then, as i thought it didnt??
Click to expand...
Click to collapse
Twrp work fine with nougat. Find thread called twrp P9 with decryption support emui 5.x. Work like charn

rhodondendron said:
Twrp work fine with nougat. Find thread called twrp P9 with decryption support emui 5.x. Work like charn
Click to expand...
Click to collapse
Says its for the PLUS model only.
Im trying to use command lines via adb but keep getting 'FAILED (remote: Command not allowed)' responses, any ideas?

BlockABoots said:
Says its for the PLUS model only.
Im trying to use command lines via adb but keep getting 'FAILED (remote: Command not allowed)' responses, any ideas?
Click to expand...
Click to collapse
Just try this dude. https://forum.xda-developers.com/p9/development/twrp-t3565703/page1

same problem
where the same problem sir BlockABoots hows your p9?

Alfombra said:
where the same problem sir BlockABoots hows your p9?
Click to expand...
Click to collapse
Its still bricked atm
---------- Post added at 08:24 PM ---------- Previous post was at 08:20 PM ----------
rhodondendron said:
Just try this dude. https://forum.xda-developers.com/p9/development/twrp-t3565703/page1
Click to expand...
Click to collapse
The issue im having when trying to adb to the phone is i keep getting a message saying 'FAILED (remote: Command not allowed)'.
If i type adb devices its showing no devices, its as if the PC cant detect the phone, but when i plug it into the PC it makes the USB connection sound and also if i run HiSuite it says there is no device connected but if i select the recovery option it then detects the phone but after checking says there are no available packages for my model

BlockABoots said:
Its still bricked atm
---------- Post added at 08:24 PM ---------- Previous post was at 08:20 PM ----------
The issue im having when trying to adb to the phone is i keep getting a message saying 'FAILED (remote: Command not allowed)'.
If i type adb devices its showing no devices, its as if the PC cant detect the phone, but when i plug it into the PC it makes the USB connection sound and also if i run HiSuite it says there is no device connected but if i select the recovery option it then detects the phone but after checking says there are no available packages for my model
Click to expand...
Click to collapse
From what I get, you still can go to fastboot&rescue mode right? Just flash twrp through fastboot. No need for adb dude. (use fastboot command instead of adb command dude)
You can't connect adb if you can't boot. From the twrp you can try to fix your phone. Maybe change the oeminfo, or flash a rom, even shutdown your phone to do three button rom install. Do you get what I am saying?

rhodondendron said:
From what I get, you still can go to fastboot&rescue mode right? Just flash twrp through fastboot. No need for adb dude. (use fastboot command instead of adb command dude)
You can't connect adb if you can't boot. From the twrp you can try to fix your phone. Maybe change the oeminfo, or flash a rom, even shutdown your phone to do three button rom install. Do you get what I am saying?
Click to expand...
Click to collapse
fastboot commands dont appear to work either, i was trying early on with a recovery file.....

[GUIDE] Unbrick your device or recover from bootloop

Assalamu alaikum people,
Those on the telegram group know that I bugged you a lot about needing data partition. Because of my experience with unbricking and recovering the device, I can tell you a sureshot method that works to restore the device. Do not use this method if your device already works. There seems to be a lot of files inside the data partition which are necessary for the stock ROM to work. This method asks you to wipe data partition and so system update will not work. This should be a last resort. .
Many people seem to have come to the situation where they are in fastboot, and it says frp locked, so they cannot flash new twrp. And the system seems to be in bootloop and it does not work. What to do from there?
1. Download this file ->https://www.androidfilehost.com/?fid=673956719939832337.
2. In your SDCard, create a folder called TWRP and inside it, create a folder called BACKUPS (all in capitals). Inside this, create a folder called 7xtwrpbackup (small letters) and paste the contents of the zip that you have downloaded into this.
3. Boot to twrp in your device and go to restore. There you should see a folder 7xtwrpbackup. If you select it, you will get a checkbox below with recovery_ramdisk like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Select Yes and after restore complete, go back and select reboot and reboot to recovery.
5. Now, the new twrp will boot. In the new twrp, I want you to first go to wipe -> advanced wipe -> select dalvik/art cache, cache, data, internal storage and system.
6. Come back once again and select wipe, and this time, select format data. It will ask you to type yes. After that is done, come back once again.
7. Now select install and in that, install the openkirin RR image from telegram group or here -> https://forum.xda-developers.com/honor-view-10/development/rom-t3753555 (This step is optional because openkirin RR has a greater chance of booting than stock ROM. You can skip this step and directly boot stock)
8. Your system must boot now. If it boots, then all partitions are good. You can boot stock.
9. You can now can download stock from my post here and repeat from step 5-> https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569
If this does not work, then look at the second method in the next post

Second method
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.

Bricked my device Twrp doesn't work
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:

Oushal kDee said:
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:
Click to expand...
Click to collapse
Download vendor partition from here https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569

Hello i am siddharth, i have relocked my oem by fastboot oem relock -------- after that yes/no option came i click on yes. It starts factory formatting after completion of formatting when the phone starts its showing your device has failed verification and got stuck in it. When i press reboot option it will directly comes to erecovery mode wher the option came to download new recovery when i connect my phone with wifi it starts searching for some time after that system update failed.
When i starts mobile directly to fastboot mode by pressing volume down button and power button the white screen with android comes appear i.e fastboot mode screen. In that screen in green colour i found that
Phone Relock
FRP lock
When ever i m trying to find the device in fastboot mode by typing fastboot devices my device showing there but no other command is working such as fastboot oem unlock -------, fastboot flash system system.img, all the time it comes Failed.
I have downloaded many UPDATE.APP and tried to load that by dload method but every time after 5% it come Failed to install.
I have downloaded UPDATE.APP form ur given link also. This is only the image in which my phone comes upto 23% install after dat failed.
Nothing working for me. Kindly help me.
Mail me if there is any solution @
[email protected]

i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help

None of the method worked for me my device still bootloops no matter what system.img or rom zip file i flash. The emui recovery method didn't work for me as it loaded up to 5% and then failed instantly. Please help me unbrick my 9 lite bro. Could you provide me the boot.img? i think my phone got bricked because i tried to i install magisk on treble rom (i guess?). But anyway PLEASE HELP ME (

Try extracting kernel.img from an update and flash that. It fixed it for me.

hi twrp is bootlooping as well
cant access
---------- Post added at 07:15 PM ---------- Previous post was at 06:52 PM ----------
hey i used the twrp from the link made a backup restored it now a get bootloop cant get into twrp it goes in ti it then it fcs then am back to bootloader unlocked warning

hi anyone got custom.img and userdata.img from this LLDL31C432B130 800130 a need to restore my device

Same Problem
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem, if anyone has solution plz help.
---------- Post added at 10:15 AM ---------- Previous post was at 10:10 AM ----------
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem.

mine goes to 5% doesnt do anything and then it fails

aveemashfaq said:
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.
Click to expand...
Click to collapse
But this is for L31
---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------
My phone's frp and bootloader locked,and phone is booting to erecovery,what to do

need help with LLD-AL10C675 indian version
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you

sunny_deed said:
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you
Click to expand...
Click to collapse
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.

BS4388 said:
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.
Click to expand...
Click to collapse
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released

sunny_deed said:
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released
Click to expand...
Click to collapse
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/

Sparkrite said:
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/
Click to expand...
Click to collapse
there is no Fullota version in there

sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
Go:
https://forum.xda-developers.com/9-lite/development/stock-rom-indian-firmware-c675-t3813875

sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
My bad, I was only trying to help.............
Anyway you have it now (post above) thanks to @BS4388 and @VigneshS007 .

Bypass Pattern Lock in Honor 9 Lite without Data Loss

Dear friends,
my android device is Honor 9 Lite. Since I bought this phone, I was always able to get into the phone and access my data by using the touch sensor.
But nevertheless, I was forced to add a pattern lock as surrogate solution in case the touch sensor does not work for any reason.
Anyway, last week I hit on a serious problem! I did not know why the device dose not accept the first way (gaining access through fingerprint using the touch sensor) anymore.
It asks me all the time to enter the right pattern lock I set up 6 about months ago. And since I was not asked to enter the pattern lock before, unfortunately I just forgot it :crying:
Therefore, I cant access my device now and I do really have very important files and documents stored on the internal memory, which I do not want to lose by reset my device to factory settings and wiping all the data stored in the internal memory...
So I have searched the Internet - for long hours - for a proper solution that helps me to bypass the pattern lock without being forced to wipe my data.
But unfortunately, I could not find any effective way to gain access again to the internal storage of my phone.
One of the most important problems I hit on while searching the Internet was that there I could not find any way to enable USB Debugging in my locked device since I cannot access the settings....
Unlike some Samsung devices, it seems that there is no way to enter the known Download Mode in new honor devices. When I get to the Recovery Mode, I can see only three options, which are:
Reboot System now
Wipe data / factory reset
Wipe cache partition
The phone is still connected to my home network and my Gmail Account is still working on it. But I also could not find any way where my Gmail Account could be helpful in this case...
Is there any way to bypass the lock screen without losing data on this Honor device?
I hope you can help me to solve my problem and rescue my files...
Waiting for your suggestions :fingers-crossed:
Thank you very much in advance!
Kind regards

Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.

{
"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"
}
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59187
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59184
Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse
Dear Sparkrite,
thank you for your fast response !
I have attached two pictures which show both the EMUI Mode in addition to the Fastboot Mode on my Honor 9 Lite device...
I don´t quite know how to flash TWRP to e-recovery partition, since I cannot reach the device settings and thus I am not able to enable USB Debugging, which seems to be a necessary step to install or flash a new recovery environment on the device!
I also cannot enter the known recovery mode which we know on Samsung devices. I suppose that this has something to do with the operating system (EMUI) the phone is running.
Furthermore, I assume that the EMUI version which is installed on the device is EMUI 8.
I also would like to point out that the known Hisuite Software could´t connect to the device when I tried to connect the device to my Laptop using a USB cable.
Could you perhaps provide me with further information regarding flashing TWRP and gaining access to the data stored on the internal memory.
And is it possible to decrypt the internal data after extracting them from the internal memory?
A possible solution to my dilemma might be that I factory reset the phone and then try to recover the lost data using an Android Data Recovery Software. What would you say about following such a method?
I know that this will be very risky, but do you think that this would be a more effective and guaranteed way to rescue my data?
Thank you very much for your support!
Waiting for your response :good:
Sorry I could not upload the picture direclty from my computer, therefore I add here the links to the images in my album again:
Honor Lite 9 - EMUI Mode:
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59184
Honor Lite 9 - Fastboot Mode:
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59187
I don´t know why the images cannot be opened here. Sorry, this is my first experience on XDA-Developers
The EMUI Version is 8.
And on the fastboot screen there are two lines written in green:
The first line says: PHONE Locked
The second line says: FRP Lock
At the top of the screen I can see the following text:
Fastboot and Rescure Mode
Please connect USB cable to your computer and open HiSuite
Android reboot reason:
AP_S_COLDBOOT 0
NA
volumekey_down_press_process_func

Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse

[/IMG]
Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse

Ok, download and unzip the attached file.
Navigate to the directory 'platform-tools' where you have unzipped the downloaded file.
Open a command (DOS) window within that folder.
Make sure you are in the dir. 'platform-tools.
Enter fastboot mode on the phone and connect to PC,
Type :- fastboot oem get-build-number [ENTER]
Send me the result here and I'll tell you the best method..................

Sparkrite said:
Ok, download and unzip the attached file.
Navigate to the directory 'platform-tools' where you have unzipped the downloaded file.
Open a command (DOS) window within that folder.
Make sure you are in the dir. 'platform-tools.
Enter fastboot mode on the phone and connect to PC,
Type :- fastboot oem get-build-number [ENTER]
Send me the result here and I'll tell you the best method..................
Click to expand...
Click to collapse
Thank you for your support!
I followed the instructions and came to the following result about the build number:
(bootloader) :LLD-L31 8.0.0.144(C432)
OKAY [ 0.006s]
finished. total time: 0.007s
Waiting for your advice
Thank you!

golden.hunter said:
Thank you for your support!
I followed the instructions and came to the following result about the build number:
(bootloader) :LLD-L31 8.0.0.144(C432)
OKAY [ 0.006s]
finished. total time: 0.007s
Waiting for your advice
Thank you!
Click to expand...
Click to collapse
Ok, good, I'll get back to you shortly................
Do you know how to downgrade ?
Do you know how to flash a TWRP and boot to E-recovery ?
NB: e-recovery is a non protected partition and can be flashed with a locked bootloader.

Sparkrite said:
Ok, good, I'll get back to you shortly................
Do you know how to downgrade ?
Do you know how to flash a TWRP and boot to E-recovery ?
NB: e-recovery is a non protected partition and can be flashed with a locked bootloader.
Click to expand...
Click to collapse
Dear Sparkrite,
I have just searched the internet using the key words you have given to me.
It seems that the so called e-recovery is not a common issue for android users. I could barely find anything helpful in this field.
5 years ago, I was thrilled by working and solving problems of android devices. However, in the last 4 years time has changed and I have nearly stopped informing about such issues, since I had too much to do and I have forced too many obstacles with forced me to change my way of life.....
Moreover, my experiences with android devices were also done with Samsung devices. Except from this problem now, I had not worked with Honor devices in the past at all...
Anyway, I have just tried to flash a TWRP file on my Honor 9 Lite device using the known command window after entering the fastboot mode (of course without enabled USB Debugging). But it didn´t work and I have got the following error message:
PS D:\Android files\Honor 9 Lite\platform-tools>fastboot devices
FPMNW18924010946 fastboot
PS D:\Android files\Honor 9 Lite\platform-tools> fastboot flash recovery twrp_honor9_lite_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.650s
How can I flash TWRP on E-recovery without accessing the device settings? and what is the function of downgrading in this context?
What would you advice me to do?
I would be very thankful if you could make me aware on a good video or a helpful article for example, which can help me to get to my aim...
Thank you!

golden.hunter said:
Dear Sparkrite,
Anyway, I have just tried to flash a TWRP file on my Honor 9 Lite device using the known command window after entering the fastboot mode (of course without enabled USB Debugging). But it didn´t work and I have got the following error message:
PS D:\Android files\Honor 9 Lite\platform-tools>fastboot devices
FPMNW18924010946 fastboot
PS D:\Android files\Honor 9 Lite\platform-tools> fastboot flash recovery twrp_honor9_lite_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.650s
How can I flash TWRP on E-recovery without accessing the device settings? and what is the function of downgrading in this context?
Thank you!
Click to expand...
Click to collapse
Well that command is doomed to fail for two very good reasons:-
1. Locked Bootloader.
2. The H9L using Oreo doe NOT have a 'recovery' partition as such.
The command to flash a custom recovery is :- 'fastboot flash recovery_ramdisk twrp.img'.
But as your BL is locked this will not work, however you can flash it to e-recovery using :-
'fastboot flash erecovery_ramdisk twrp.img'.
The advantage of downgrading (to at least B132 you have b144) is twofold:-
1. You could use HCU to get your BL code to unlock. (€4
1a. Or you could get your 'Slock' code to flash to 'unlock' your BL for free.
But unfortunately this would also wipe your phone.
2. Downgrading, using the Dload (Google it) method may well bypass the pattern unlock screen and/or fingerprint working again.
Edit:
Flash a working TWRP and come back to me when you can boot to it.
I may just have a workaround for you.

Sparkrite said:
Well that command is doomed to fail for two very good reasons:-
1. Locked Bootloader.
2. The H9L using Oreo doe NOT have a 'recovery' partition as such.
The command to flash a custom recovery is :- 'fastboot flash recovery_ramdisk twrp.img'.
But as your BL is locked this will not work, however you can flash it to e-recovery using :-
'fastboot flash erecovery_ramdisk twrp.img'.
The advantage of downgrading (to at least B132 you have b144) is twofold:-
1. You could use HCU to get your BL code to unlock. (€4
1a. Or you could get your 'Slock' code to flash to 'unlock' your BL for free.
But unfortunately this would also wipe your phone.
2. Downgrading, using the Dload (Google it) method may well bypass the pattern unlock screen and/or fingerprint working again.
Edit:
Flash a working TWRP and come back to me when you can boot to it.
I may just have a workaround for you.
Click to expand...
Click to collapse
Well thank you for your response!
The locked bootloader on my phone seems to be the most important obstacle which prevents me from installing anything on the device
I have tried to flash the TWRP file to E-recovery using the command window in the file of platform-tools and a custom recovery for Honor 9 Lite. But this didn´t work either...
I always got the error message:
FAILED (remote: Command not allowed)
I know that this error occurs due to the locked bootloader, but I could not find any proper and effective way to unlock the bootloader on my honor device without access to my device settings....
I have also found out that my device belongs to the supported models on HCU-Client-Website. But as I have seen, the process of unlocking the bootloader using this method requires also a certain interaction with the device, which means that the internal files and settings of the phone must be accessible in order to get the code to unlock the bootloader...
Therefore, being unable to unlock the bootloader prevents me from flashing a TWRP. And being unable to unlock the bootloader prevents me also from downgrading the software and installing a custom rom on the device (see for example: https://forum.xda-developers.com/9-lite/development/kangvip-rom-emui-8-0-t3775904)
It is completely OK for me to buy HCU-tool to get the code to unlock the bootloader, if this can help me to gain access to the internal memory without data loss. But does this work in my case, without the ability to open the device.?! And if yes, how does this go or where can I find near instructions to achieve this mission?
And is there any way to downgrade the phone without unlocking the bootloader or flashing a custom recovery? If this was possible, then I would try to flash a custom recovery and delete the password file through a special file called aromafm and with the help of my SD-Card, which was a successful way five years ago when I was able to bypass the pattern lock on the device of my cousin without any data loss....
In the worst case, I would simply factory reset the phone and try to recover the important files using a good recovery software.....
I think, this may be the most appropriate method with minimal time exposure, since I must gird myself to start the new semester at the university...:good:
Waiting for your advice
Thank you once again :fingers-crossed::good:

As I said it is possible to flash TWRP to E-recovery even with a locked bootloader !!!
I have done it many times.
You will NOT unlock BL while on B144, without code.
HCU will NOT work with build numbers above 132.
ALL BL unlocking WILL re-set and wipe phone.
Downgrading using Dload method is possible with locked bootloader !!!
Search here:- https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=lld-l31&firmware_page=0
Make sure it is a Dload ROM, it will say so within instructions in zip.
If you re-set phone, data WILL be gone, remember it is encrypted so no recovery.
My Advice is:-
Persevere with flashing TWRP to Erecovery.
Erecovery_ramdisk is NOT protected.
" fastboot flash erecovery_ramdisk twrp.img "

Sparkrite said:
As I said it is possible to flash TWRP to E-recovery even with a locked bootloader !!!
I have done it many times.
You will NOT unlock BL while on B144, without code.
HCU will NOT work with build numbers above 132.
ALL BL unlocking WILL re-set and wipe phone.
Downgrading using Dload method is possible with locked bootloader !!!
Search here:- https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=lld-l31&firmware_page=0
Make sure it is a Dload ROM, it will say so within instructions in zip.
If you re-set phone, data WILL be gone, remember it is encrypted so no recovery.
My Advice is:-
Persevere with flashing TWRP to Erecovery.
Erecovery_ramdisk is NOT protected.
" fastboot flash erecovery_ramdisk twrp.img "
Click to expand...
Click to collapse
Dear Sparkite,
Thank you for your fast response!
I have been trying to downgrade and install TWRP Recovery on my device for almost three hours now, however, unfortunately without success
I have tried many times to flash TWRP to E-Recovery-Partition exactly as your have described in the last post, but I always got the same error message:
FAILED (remote: Command not allowed)
I have also tried to do the installation using different platforms and different TWRP files and sometimes with light changes in the code, but all my attempts failed...
My trials to downgrade the device to a version under 132 using my SD Card were also frustrating. I always got the same error, after the installation process reached 5%:
Software install failed!
Get help from: http://www.emui.com/emotiondownload.php?mod=restore
I tried to downgrade the device to the versions 8.0.0.0.127 and 8.0.0.0.131 and 8.0.0.0.129, which I downloaded from the website you have given to me. Also without success....
By the way, I could not find any instruction files in the zipped update files which I have downloaded from the website, therefore it was impossible for me to find out whether the downloaded Rom was compatible with the dload-method or not.
Also the program called "HuaweiUpdateExtractor", which I tried to use as an auxiliary means didn´t accept the UPDATE.APP and I always got the following error message:
ERECOVERY_VBMET.img: Invalid header crc - Expected: 33542 Got: 25244
It seems that there is no way out, right?
If there is a certain custom rom you can suggest for me, I would be very grateful.
Maybe I can succeed in flashing TWRP after downgrading the software installed. But I do not know if there is still a method that I didn´t try on this immune system....
Thank you in advanced!

I don't know what you are doing wrong.
It IS possible to flash TWRP to Erecovery as I have said many times before.
Try a different USB lead.
Try a different USB Port.
Try a different 'fastboot'/'ADB' version.
Try a different TWRP. (https://mega.nz/#!wotVWBQZ!ZO9DHD-HBMj-5LCxxW_74IYsDoSrVDeZsaQgMyIvuGQ)
Send me a screen shot of your command(s)
Send me a screenshot of your phone when you are trying to flash.

Sparkrite said:
I don't know what you are doing wrong.
It IS possible to flash TWRP to Erecovery as I have said many times before.
Try a different USB lead.
Try a different USB Port.
Try a different 'fastboot'/'ADB' version.
Try a different TWRP. (https://mega.nz/#!wotVWBQZ!ZO9DHD-HBMj-5LCxxW_74IYsDoSrVDeZsaQgMyIvuGQ)
Send me a screen shot of your command(s)
Send me a screenshot of your phone when you are trying to flash.
Click to expand...
Click to collapse
Dear Sparkite,
I have just tried all the alternative ways you suggested, unfortunately without success and I don´t know where the mistake in hiding
Again and again I hit on the same problem and I always got the same error message:
Command not allowed...
I have attached two pictures that show the fastboot screen of the device in addition to the commands I gave in the command window...
Thank you for your support!
View attachment 4806745
View attachment 4806753
View attachment 4806760

golden.hunter said:
Dear Sparkite,
I have just tried all the alternative ways you suggested, unfortunately without success and I don´t know where the mistake in hiding
Again and again I hit on the same problem and I always got the same error message:
Command not allowed...
I have attached two pictures that show the fastboot screen of the device in addition to the commands I gave in the command window...
Thank you for your support!
View attachment 4806745
View attachment 4806753
View attachment 4806760
Click to expand...
Click to collapse
Here the screenshot of the command window:
View attachment 4806761

golden.hunter said:
Here the screenshot of the command window:
View attachment 4806761
Click to expand...
Click to collapse
My bad, I'm so sorry to have put you through all this, I forgot that I had previously flashed 'slock' to any H9L to enable flashing to Erecovery. Apologies.
However in order to obtain a slock file for your phone you will HAVE to downgrade to at least B132.
Get a Dload firmware from here:- https://androidhost.ru/
When you have successfully downgraded we can go about getting a 'slock' file for you.
Or if you like you could go here on Telegram and join up to get your 'slock' :-
https://t.me/joinchat/I0ghclds9xtiC-5XLKIQrw
NB: Read the welcome message very carefully and follow it to the letter or you WILL get banned.

Installing twrp on Sprint v40 flashed to us pie

Recently downgraded from Verizon 10.0 to us pie in order to root / install custom ROM. I've followed all guides and Its not going good. To start, I've successfully unlocked my bootloader after 2 failed attempts. However, when I try to enter fastboot after installing my default abl_a/b, it just boots normally. To get back into fastboot, I have to load the v35 image first . Even after getting into fastboot, I am still unable to flash twrp. The flash says completed and the phone turns on but boots normally.
Does anyone have a solution for this ? Is this blocked and is there any bypass ?

kris597 said:
Recently downgraded from Verizon 10.0 to us pie in order to root / install custom ROM. I've followed all guides and Its not going good. To start, I've successfully unlocked my bootloader after 2 failed attempts. However, when I try to enter fastboot after installing my default abl_a/b, it just boots normally. To get back into fastboot, I have to load the v35 image first . Even after getting into fastboot, I am still unable to flash twrp. The flash says completed and the phone turns on but boots normally.
Does anyone have a solution for this ? Is this blocked and is there any bypass ?
Click to expand...
Click to collapse
First, the phone doesn't have fastboot, normally. So, after you flash the normal (stock) abl back, you should not be able to get to fastboot, so that's expected.
Second, getting twrp on the device has changed, you don't 'boot it', you need your boot partition with twrp 'injected' into it already (that's the easiest way). Which version of US Open Pie do u have? Can't seem to find a boot partition of it with twrp injected, but that's what u need.
Also, do u know what your current slot is? If u flash something to the other slot, it won't change anything. Use 'fastboot getvar all' and at the bottom of the output it will tell you what current slot is.
cheers

I tried injecting twrp directly into both my boot partitions and it just bootloops. I am also currently on active slot a . Prior to this, I was attempting to flash twrp using Verizon 10.0. However, after following countless guides, I was unsuccessful and tried to do it on this current version
{
"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"
}

kris597 said:
I tried injecting twrp directly into both my boot partitions and it just bootloops. I am also currently on active slot a . Prior to this, I was attempting to flash twrp using Verizon 10.0. However, after following countless guides, I was unsuccessful and tried to do it on this current version View attachment 5453895
Click to expand...
Click to collapse
So, from your previous post this is us Open 20a correct? Even though it says UA, it's actually QA right?
Also, how did u 'try injecting directly to your boot partition'? Did u use twrp? How did u do that?
Remember, once u have twrp in the boot partition, you should be going directly to twrp, not boot the system. Format data, reboot recovery, flash magisk and dm-verity, then boot system (not before).
Have you tried posting in the guide u followed? Usually you'll find answers there most often.
cheers

AsItLies said:
So, from your previous post this is us Open 20a correct? Even though it says UA, it's actually QA right?
Also, how did u 'try injecting directly to your boot partition'? Did u use twrp? How did u do that?
Remember, once u have twrp in the boot partition, you should be going directly to twrp, not boot the system. Format data, reboot recovery, flash magisk and dm-verity, then boot system (not before).
Have you tried posting in the guide u followed? Usually you'll find answers there most often.
cheers
Click to expand...
Click to collapse
I loaded judypn twrp image into boot a/b using qfill. It just boot loops. I have posted in the guide. Unfortunately no luck

kris597 said:
I loaded judypn twrp image into boot a/b using qfill. It just boot loops. I have posted in the guide. Unfortunately no luck
Click to expand...
Click to collapse
That's not the way it works, it's supposed to be 'injected' by twrp itself, in the advanced options of twrp, there's a selection called 'inject twrp', and you give it the name of the twrp image (on the sd card) and it then injects that image into the current boot loader of the device (the actual 64 meg image on the hard drive boot partition of the device).
Post in this thread your current boot image, and the twrp image. If your device is crossflashed by lgup, then both a and b boot images are the same. If your device is booting a carrier image, be sure to pull the boot image from the current boot slot (as boot a and boot b will be different).
I'll inject the twrp image into it for you. Then u use qfil and flash it, boot directly to recovery (now twrp) from qfil (use key combo), and follow what I mentioned in prev post.

AsItLies said:
That's not the way it works, it's supposed to be 'injected' by twrp itself, in the advanced options of twrp, there's a selection called 'inject twrp', and you give it the name of the twrp image (on the sd card) and it then injects that image into the current boot loader of the device (the actual 64 meg image on the hard drive boot partition of the device).
Post in this thread your current boot image, and the twrp image. If your device is crossflashed by lgup, then both a and b boot images are the same. If your device is booting a carrier image, be sure to pull the boot image from the current boot slot (as boot a and boot b will be different).
I'll inject the twrp image into it for you. Then u use qfil and flash it, boot directly to recovery (now twrp) from qfil (use key combo), and follow what I mentioned in prev post.
Click to expand...
Click to collapse
These are all the files i found / used. My device no longer has a carrier image as i crossflashed to global pie.
Im still a little confused. In all the guides i've followed, they've either used fastboot to booth twrp image and then install twrp after or load the twrp image straight into boot a/b.

kris597 said:
These are all the files i found / used. My device no longer has a carrier image as i crossflashed to global pie.
Im still a little confused. In all the guides i've followed, they've either used fastboot to booth twrp image and then install twrp after or load the twrp image straight into boot a/b.
Click to expand...
Click to collapse
I spoke too soon, my current device is LG G8, it has twrp, but unfortunately adb shell doesn't work on this twrp version. So I can't do this anymore.
I would suggest, in the guide you mention, I saw your last post but didn't know how to respond because you didn't say what command u used that resulted in:
downloading 'boot.img'... OKAY [ 2.124s]
booting... FAILED (remote: Failed to load/authenticate boot image: Load Error)
The version of twrp you have won't boot. twrp has to be 'injected' into the boot image, so you'll then have a boot image and twrp (recovery) will be in it.
Post again in that guide, so others can learn from it. But put in the exact command you were using to try to get to twrp, that would help a lot so others know what yer doing.
cheers

I should add, yes, this is confusing, sorry.
the guide you want to follow to get twrp is this one.
The reason(s) yer having trouble booting that version of twrp I believe it's because of 1) the engineering abl is Oreo, it won't boot anything that isn't Oreo based. 2) to be able to boot that version of twrp, follow the guide above and 'nuke laf' (back it up first, in case you need download mode - lgup, again).
so, as mentioned in the guide, in the 'nuke laf' section, you now get to fastboot by using the keys you'd normally use to get to lgup, but now u get a 'watered down' version of fastboot.
Pretty sure u can then use that version of fastboot to boot your version of twrp and then follow the directions in the guide to 'inject' it into ramdisk (the boot partition).
cheers

kris597 said:
These are all the files i found / used. My device no longer has a carrier image as i crossflashed to global pie.
Im still a little confused. In all the guides i've followed, they've either used fastboot to booth twrp image and then install twrp after or load the twrp image straight into boot a/b.
Click to expand...
Click to collapse
Managed to get a version of twrp that does what's needed, installed. The attached is your boot partition with twrp injected. Both a and b images were the same so it will work for both slots.
Flash it with qfil, then use key combo to go directly to recovery. Once in twrp, format data, reboot recovery, flash magisk (if wanted) and dm-verity-force... and you should be all set.
cheers

My phone is now unresponsize and stuck on a black screen. Was i supposed to boot a and b ?
I am unable to enter edl, download mode or any mode. It is completely unresponsize. Is it hard bricked ?
Edit: I was able to enter edl mode and restore my original boot partitions, however, im still stuck on a black screen and can only enter edl
AsItLies said:
Managed to get a version of twrp that does what's needed, installed. The attached is your boot partition with twrp injected. Both a and b images were the same so it will work for both slots.
Flash it with qfil, then use key combo to go directly to recovery. Once in twrp, format data, reboot recovery, flash magisk (if wanted) and dm-verity-force... and you should be all set.
cheers
Click to expand...
Click to collapse

kris597 said:
My phone is now unresponsize and stuck on a black screen. Was i supposed to boot a and b ?
I am unable to enter edl, download mode or any mode. It is completely unresponsize. Is it hard bricked ?
Edit: I was able to enter edl mode and restore my original boot partitions, however, im still stuck on a black screen and can only enter edl
Click to expand...
Click to collapse
wow what in the world did u do? You really need to say specifically the steps you did to get where u are now, I mean, telling me the results and saying 'what do I do' is assuming I expected this to happen?
this is totally unexpected. What, exactly, did u do?

AsItLies said:
wow what in the world did u do? You really need to say specifically the steps you did to get where u are now, I mean, telling me the results and saying 'what do I do' is assuming I expected this to happen?
this is totally unexpected. What, exactly, did u do?
Click to expand...
Click to collapse
I followed the steps correctly i believe. I have experience with rooting and flashing in the past but its entirely different with LG.
The steps i followed:
I entered EDL MODE, i flashed the boot_a_twrp to both my a & B slots and it was successful. After this, i tried to enter recovery mode and was left with a black screen, no vibration, screen or any form of life. Tried booting may times, holding down power + volume down for 4+ minutes but still no hope. I was then able to get back into edl where i flashed my original images back . Unfortunately, it is still not working. Sucks that i will have to buy a new phone now. I guess this is where i stop messing with my phone lol .

kris597 said:
I followed the steps correctly i believe. I have experience with rooting and flashing in the past but its entirely different with LG.
The steps i followed:
I entered EDL MODE, i flashed the boot_a_twrp to both my a & B slots and it was successful. After this, i tried to enter recovery mode and was left with a black screen, no vibration, screen or any form of life. Tried booting may times, holding down power + volume down for 4+ minutes but still no hope. I was then able to get back into edl where i flashed my original images back . Unfortunately, it is still not working. Sucks that i will have to buy a new phone now. I guess this is where i stop messing with my phone lol .
Click to expand...
Click to collapse
Wow, sorry to hear that. From what you're saying it sounds as though you did the right steps. To clarify, to exit edl mode is hold vol minus and power buttons until u hear the windows chime meaning 'disconnect' (usually only about 5 to 10 secs).
It is certain that newer phones are much more complicated, with dual slots and the challenge they present, and it's even worse with LG as they don't allow bl unlock and don't have fastboot, so getting those adds to the complexity.
You say you flashed the image to boot a and b, did u get a message about 'data overflow' by chance? (If so, that would explain the situation, but not how it happened). If an image was flashed to an incorrect partition (not that hard to make that mistake in qfil), and someone 'okays' the 'data overflow' message, it will **overwrite** nearby partition(s), resulting in a brick.
Assuming something like the above happened, there's an option, unfortunately it's a bit complicated also.

AsItLies said:
Wow, sorry to hear that. From what you're saying it sounds as though you did the right steps. To clarify, to exit edl mode is hold vol minus and power buttons until u hear the windows chime meaning 'disconnect' (usually only about 5 to 10 secs).
It is certain that newer phones are much more complicated, with dual slots and the challenge they present, and it's even worse with LG as they don't allow bl unlock and don't have fastboot, so getting those adds to the complexity.
You say you flashed the image to boot a and b, did u get a message about 'data overflow' by chance? (If so, that would explain the situation, but not how it happened). If an image was flashed to an incorrect partition (not that hard to make that mistake in qfil), and someone 'okays' the 'data overflow' message, it will **overwrite** nearby partition(s), resulting in a brick.
Assuming something like the above happened, there's an option, unfortunately it's a bit complicated also.
Click to expand...
Click to collapse
I believe i got a message similar to that
Edit: Cant be bothered to try any new methods. Will get a refurbished lg v60 from amazon. Had the v40 for 2 years. Its time to upgrade
cheers and thankyou for your help