Database Develop

Maybe hard bricked? Android won't start without PW after 3.1.3 update....never set pw

hello all....sooo..I have been attempting to bring my op3 to stock...so, I unrooted, applied the 3.1.3 update and UNCHECKED "OEM Unlocking" in dev options (i think that is where i screwed up) and went to the "all in one tool kit" and clicked on "lock bootloader"...it all went well, but when the phone rebooted, it is saying "To start android, enter password"..but I never even set a password..is there a default password or something I should be entering? also, I have tried to relock bootloader, format the phone..and obviously it is saying that "flashing not allowed" or "oem unlock is not allowed".......what in the world do I do to get this phone working again? Thanks a lot.
oh, also, I can't reboot back into TWRP, which seems obvious since the bootloader is now locked.
I can run fastboot commands of course, but nothing seems to stinking work here!
Device is not showing up when I run "adb devices"
I really appreciate any help! This is frustrating. I should have just kept the "oem unlocking" checked in dev options
update 1: hmm, well got an update....I just kept entering random passwords and it finally said "phone will be wiped after next failed attempt"..I was fine with that, so i typed something in...and the phone rebooted and it booted back up to a screen that says "decryption unsuccessful" the password you entered is correct, but unfortunatley your data is corrupt. To resume using your phone, you need to perform a factory reset...and it has a button at the bottom that says "reset"...so, i hit the "reset" button and the phone reboots and tried to go into recovery and the "one plus" boot logo flashes VERY quickly and then the phone just seems to shut down, screen goes black..I wait a bit and power the phone back on and it goes back to that same "decryption unsuccessful" screen...
I can NOT get into stock recovery (that was replaced with TWRP, anyway) or TWRP.....if i try to fastboot into recovery the phone will reboot and the "one plus logo" will flash very fast and then just go to a blank screen.....
update 2: I got adb to work...gonna play with that and see if I can do anything.
update 3: Here is a link to a video showing what I am talking about when I say the "oneplus logo" just flashes...
Video starts out with me just pushing the power button..then it looks like it is going to boot up..then hits that decryption unsuccessful screen..so, I tap reset, at this point, it will reboot and attempt to go into the recovery partition and wipe data...but, you can see that it just reboots and the one plus logo flashes, screen goes black and eventually the notification LED turns solid white.
so, next in the video..I power the device off and try to manually enter recovery mode (vol- + pwr) and same thing, oneplus logo flashes and blank screen. Anyway, here is the link to the video.
https://goo.gl/photos/EU2ZSkFw1JrdExeQ8
update 4: Level 2 OnePlus Support did NOT fix the issue. He didn't even give me a reason when I asked what the issue was, however, I did see that it failed out when he attempted to use the MSM tool. he escalated to the next level of support.

I wonder it it has the oneplus one bug to where if u relock ur bootloader u can't unlock it, also I don't think u need to relock if u r flash an OTA just unroot and refresh stock recovery (which no one has pulled yetyet, that has been tested), u may want to contact oneplus and see if they will give u that stock OS to fastboot files, also with the pw issues, all u had to do was boot into twrp and goto file manager and delete the pw key, it's somewhere in this forum that shows u how to do it, i think it's in one of the 3 trwp threads

cms062407 said:
hello all....sooo..I have been attempting to bring my op3 to stock...so, I unrooted, applied the 3.1.3 update and UNCHECKED "OEM Unlocking" in dev options (i think that is where i screwed up) and went to the "all in one tool kit" and clicked on "lock bootloader"...it all went well, but when the phone rebooted, it is saying "To start android, enter password"..but I never even set a password..is there a default password or something I should be entering? also, I have tried to relock bootloader, format the phone..and obviously it is saying that "flashing not allowed" or "oem unlock is not allowed".......what in the world do I do to get this phone working again? Thanks a lot.
oh, also, I can't reboot back into TWRP, which seems obvious since the bootloader is now locked.
I can run fastboot commands of course, but nothing seems to stinking work here!
Device is not showing up when I run "adb devices"
I really appreciate any help! This is frustrating. I should have just kept the "oem unlocking" checked in dev options
Click to expand...
Click to collapse
Can you try and install the file via normal, recovery?

Edu616 said:
Can you try and install the file via normal, recovery?
Click to expand...
Click to collapse
hmm, well got an update....I just kept entering random passwords and it finally said "phone will be wiped after next failed attempt"..I was fine with that, so i typed something in...and the phone rebooted and it booted back up to a screen that says "decryption unsuccessful" the password you entered is correct, but unfortunatley your data is corrupt. To resume using your phone, you need to perform a factory reset...and it has a button at the bottom that says "reset"...so, i hit the "reset" button and the phone reboots and tried to go into recovery and the "one plus" boot logo flashes VERY quickly and then the phone just seems to shut down, screen goes black..I wait a bit and power the phone back on and it goes back to that same "decryption unsuccessful" screen...
I can NOT get into stock recovery (that was replaced with TWRP, anyway) or TWRP.....if i try to fastboot into recovery the phone will reboot and the "one plus logo" will flash very fast and then just go to a blank screen.....

Bradl79 said:
I wonder it it has the oneplus one bug to where if u relock ur bootloader u can't unlock it, also I don't think u need to relock if u r flash an OTA just unroot and refresh stock recovery (which no one has pulled yetyet, that has been tested), u may want to contact oneplus and see if they will give u that stock OS to fastboot files, also with the pw issues, all u had to do was boot into twrp and goto file manager and delete the pw key, it's somewhere in this forum that shows u how to do it, i think it's in one of the 3 trwp threads
Click to expand...
Click to collapse
Unfortunately, I can not boot into TWRP to do anything
I am pretty sure the problem is it won't boot into TWRP because the bootloader is now locked, again and I do not have stock recovery of course, since I installed TWRP.
Is there no way that you know of to relock the bootloader without having to actually go into the dev options and select "OEM unlocking"? any sort of command I can run? I can't seem to find any
Thanks, sir.

cms062407 said:
Unfortunately, I can not boot into TWRP to do anything
I am pretty sure the problem is it won't boot into TWRP because the bootloader is now locked, again and I do not have stock recovery of course, since I installed TWRP.
Is there no way that you know of to relock the bootloader without having to actually go into the dev options and select "OEM unlocking"? any sort of command I can run? I can't seem to find any
Thanks, sir.
Click to expand...
Click to collapse
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery

Bradl79 said:
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery
Click to expand...
Click to collapse
going to try now! will update in a couple of minutes.

cms062407 said:
going to try now! will update in a couple of minutes.
Click to expand...
Click to collapse
best of luck, i hope it does work out for u

Bradl79 said:
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery
Click to expand...
Click to collapse
well, didn't work...I feel as if something is up with the encryption of the phone here is a screenshot of what happens when I try to flash the recovery.img....it always says "partition flashing is not allowed" when i try to flash anything.
{
"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"
}

cms062407 said:
well, didn't work...I feel as if something is up with the encryption of the phone here is a screenshot of what happens when I try to flash the recovery.img....it always says "partition flashing is not allowed" when i try to flash anything.
Click to expand...
Click to collapse
what is the error u get when u try to unlock the bootloader via fastboot?

Bradl79 said:
what is the error u get when u try to unlock the bootloader via fastboot?
Click to expand...
Click to collapse
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..

cms062407 said:
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..
Click to expand...
Click to collapse
yeah i think u r right, so u have no recovery or no OS installed, correct, i wonder if someone who is smarter than me on here can show u how to flash OOS manually yet, i can try to pull the partitions and send them to u and see if u can flash via fastboot, it may take me a bit, but i will upload them and have u download 3.1.3 partitions, i don't think u can flash recovery with out BL unlocked but u may be able to other partitions.

Bradl79 said:
yeah i think u r right, so u have no recovery or no OS installed, correct, i wonder if someone who is smarter than me on here can show u how to flash OOS manually yet, i can try to pull the partitions and send them to u and see if u can flash via fastboot, it may take me a bit, but i will upload them and have u download 3.1.3 partitions, i don't think u can flash recovery with out BL unlocked but u may be able to other partitions.
Click to expand...
Click to collapse
sure, it wouldn't hurt to try to manually flash...but I bet we get the same error

cms062407 said:
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..
Click to expand...
Click to collapse
OEM unlock essentially opens up the system partitions to be writeable, so since your system is still locked, it makes sense that you can't flash anything. There are a number of OnePlus/Qualcomm unbricking tutorials that you can lookup, but you'll need the right files and I don't think anyone has made a full unbricking set of partitions with flash instructions for the OnePlus 3. I could be wrong though. I think there could be hope for your phone, just not quite right away.

thank u @tesherx that would make sense on why he can't, i'll still upload them anyway so if anyone needs them for whatever reason.

Bradl79 said:
thank u @tesherx that would make sense on why he can't, i'll still upload them anyway so if anyone needs them for whatever reason.
Click to expand...
Click to collapse
I think those partitions will be part of the final solution, but there has to be flash maps with them as well to correctly identify the sizes,locations, etc. Considering the OnePlus 3's level of developer support so far, I think a complete unbricking tutorial won't be far away.

@cms062407 - sorry that you're going through this, this is a little weird though, oneplus should have given priority to unlock bootloader even when the os doesnt work.. i mean what will people do if their phone soft bricks ? its a dead phone since you cant flash files, enter recovery or factory reset !! this is just stupid of oneplus.. but then again if this was the case anyone would steal a oneplus3 and use it as their own... damn this is messed up.

Thanks. But, there will be a fix, right?

Have you tried to just erase your userdata partition to remove encryption with the command
Code:
fastboot format userdata
Hope you'll get through.

cms062407 said:
Thanks. But, there will be a fix, right?
Click to expand...
Click to collapse
Even if bootloader is locked, there should be some recovery, OnePlus or twrp. Isn't it there?

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.....

[ SOLVED ] Moto G5S Plus Stuck on Boot / Bootloader Giving Bad Key Error / Soft Brick

Moto G5S Plus Stuck on Boot / Bootloader Giving Bad Key Error / Soft Brick
{
"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"
}
My Assumptions
You have unlocked your BootLoader.
You have flashed TWRP Recovery.
You have rooted your Device (Not mandatory).
What's happening ?
You Flashed Something & now getting Bad key Error & Device not Booting.
You flashed Boot.img & stuck here now.
You flashed Custom Kernel & stuck.
You flashed Stock Firmware & Stuck here.
You Flashed Rom, everything went well, but still stuck here.
Solution
Connect your phone with your Computer.
Hold volume down button for 5 seconds & then simultaneously hold power button till it goes to bootloader, now release the buttons.
Use volume buttons to navigate to recovery & press power to boot to TWRP recovery.
You will see MTP Mode has been Enabled & you can see phone's internal memory.
Dowload Latest Magisk Zip & place it in your phone.
Now click on Install option of TWRP recovery & install Magisk Zip.
Wipe Cache/Dalvik Cache, go back & reboot system.
Voila, Now Bad Keyy will be replaced by N/A & your device will boot successfully.

brute-coder said:
Moto G5S Plus Stuck on Boot / Bootloader Giving Bad Key Error / Soft Brick
My Assumptions
You have unlocked your BootLoader.
You have flashed TWRP Recovery.
You have rooted your Device (Not mandatory).
What's happening ?
You Flashed Something & now getting Bad key Error & Device not Booting.
You flashed Boot.img & stuck here now.
You flashed Custom Kernel & stuck.
You flashed Stock Firmware & Stuck here.
You Flashed Rom, everything went well, but still stuck here.
Solution
Connect your phone with your Computer.
Hold volume down button for 5 seconds & then simultaneously hold power button till it goes to bootloader, now release the buttons.
Use volume buttons to navigate to recovery & press power to boot to TWRP recovery.
You will see MTP Mode has been Enabled & you can see phone's internal memory.
Dowload Latest Magisk Zip & place it in your phone.
Now click on Install option of TWRP recovery & install Magisk Zip.
Wipe Cache/Dalvik Cache, go back & reboot system.
Voila, Now Bad Keyy will be replaced by N/A & your device will boot successfully.
Click to expand...
Click to collapse
N/a And bad key is same....
I had bad key after flashing stock And my phone booted correctly...
Sent from my Moto G5S Plus using XDA Labs

Adi5 said:
N/a And bad key is same....
I had bad key after flashing stock And my phone booted correctly...
Sent from my Moto G5S Plus using XDA Labs
Click to expand...
Click to collapse
For me, it got stuck at Bad keys. And it didn't boot whatever I tried. But after flashing Magisk it changes to N/A & booted instantly. It wasn't same in my case.

Where i can find latest magisk for moto g5s plus ? Thanks before
Edit founded.. thanks

brute-coder said:
Moto G5S Plus Stuck on Boot / Bootloader Giving Bad Key Error / Soft Brick
Click to expand...
Click to collapse
I made a big mistake,
Unlocked boot locker, Flashed TWRP.
yesterday i got oreo update and i hit install update.
and now it it redirecting me to TWRP only. not allowing me to boot my device. please help me
I am in different city with stranger's laptop, dont have pen drive and OTG cable, just give me quick guide, i just want to start my phone, I have set up everything in my laptop, i dont have it right now, so please guide me necessary Drivers software also
I want Stock Oreo or nougat
I think after installing stock Recovery it will work ? do you have link for stock recovery only ?
---------- Post added at 11:05 AM ---------- Previous post was at 10:53 AM ----------
brute-coder said:
Moto G5S Plus Stuck on Boot / Bootloader Giving Bad Key Error / Soft Brick
Click to expand...
Click to collapse

haroen88 said:
Where i can find latest magisk for moto g5s plus ? Thanks before
Edit founded.. thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

ashish_zarekar said:
I made a big mistake,
Unlocked boot locker, Flashed TWRP.
yesterday i got oreo update and i hit install update.
and now it it redirecting me to TWRP only. not allowing me to boot my device. please help me
I am in different city with stranger's laptop, dont have pen drive and OTG cable, just give me quick guide, i just want to start my phone, I have set up everything in my laptop, i dont have it right now, so please guide me necessary Drivers software also
I want Stock Oreo or nougat
I think after installing stock Recovery it will work ? do you have link for stock recovery only ?
---------- Post added at 11:05 AM ---------- Previous post was at 10:53 AM ----------
Click to expand...
Click to collapse
Hi, did you made any backup (TWRP Backup) of your device?

brute-coder said:
Hi, did you made any backup (TWRP Backup) of your device?
Click to expand...
Click to collapse
no dont have any backup

ashish_zarekar said:
I made a big mistake,
Unlocked boot locker, Flashed TWRP.
yesterday i got oreo update and i hit install update.
and now it it redirecting me to TWRP only. not allowing me to boot my device. please help me
I am in different city with stranger's laptop, dont have pen drive and OTG cable, just give me quick guide, i just want to start my phone, I have set up everything in my laptop, i dont have it right now, so please guide me necessary Drivers software also
I want Stock Oreo or nougat
I think after installing stock Recovery it will work ? do you have link for stock recovery only ?
---------- Post added at 11:05 AM ---------- Previous post was at 10:53 AM ----------
Click to expand...
Click to collapse
There are no quick guides
You need
Computer with fastboot
Stock images for your region/device
Try flashing stock recovery first. If it doesn't work, flash stock images

brute-coder said:
Hi, did you made any backup (TWRP Backup) of your device?
Click to expand...
Click to collapse
Calm down if you still have twrp installed
install this one by twrp
before leaving twrp install twrp.img because if you leave without installing will be with recovery of stock
I always do this with this rom when I'm in trouble
https://androidfilehost.com/?fid=3700668719832241125

jakson7474 said:
Calm down if you still have twrp installed
install this one by twrp
before leaving twrp install twrp.img because if you leave without installing will be with recovery of stock
I always do this with this rom when I'm in trouble
https://androidfilehost.com/?fid=3700668719832241125
Click to expand...
Click to collapse
So right now my xt1805 running official oreo build, but everytime I reboot it's always get to twrp, and to boot the system, I have to manually start it from bootloader, will flashing this solve my problem? Thanks

AdamKomang_noob said:
So right now my xt1805 running official oreo build, but everytime I reboot it's always get to twrp, and to boot the system, I have to manually start it from bootloader, will flashing this solve my problem? Thanks
Click to expand...
Click to collapse
Just go to bootloader mode n connect your phone at pc open fastboot type fastboot oem fb_mode_set and fastboot oem fb_mode_clear

i stuck in recovery mode
when i pressed volume down key and press power key on recovery mode, it showed bad key and then NO COMMAND with warning android logo and then stuck there even when I connect to pc

bad key/not able to go to flashmode/recovery mode
Hi there ,
I have moto g5 s plus with unlock bootloader and root access with stock rom .
I used to have id N/A but after trying to flash stock rom via LMSA id changed to bad key.
I was and still unable to go to flash mode because no it is not responding at all ...means no affect can be seen after flashboot menu plus after few seconds boot loop begin again thus making it difficult to keep connected with PC .
Please Help!

Hello, I already unlock the bootloader, flash custom ROM, and rooting. My problem is Both ROM and TWRP are not launching. Please anyone can help me?

Mi A2 - Failed to boot - after system update

Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"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"
}

You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".

Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.

Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?

HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?

pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.

pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.

HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.

nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....

Did you try the factory data reset?

1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...

Same thing happened to me. You should manually switch the active partition in fastboot.

Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....

@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.

Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....

try a "fastboot continue" in adb

hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks

pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".

Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!

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