Develop Bugs

I cannot downgrade my device... is it not allowed?

Hey guys, I have a Nexus 7 16gb 2013 wifi running 5.1.1 lollipop LMY48G.
I'm trying to downgrade it to kitkat so I can install some software the only works correctly on kitkat on it.
I follow this guide: laptopmag(.com)articles/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and whenever I finish, I get a green android laying down with a red caution symbol ontop of him.
But the weird thing is I'm able to install 5.1.1 no issues using the same method, but if I pick anything older... The green android shows up..
Right now I'm back on a fresh 5.1.1 install.
Is there something I'm missing? From all my googling it seems like I should be allowed to installed kitkat no issues on this device. What am I missing?

Diesel47 said:
Hey guys, I have a Nexus 7 16gb 2013 wifi running 5.1.1 lollipop LMY48G.
I'm trying to downgrade it to kitkat so I can install some software the only works correctly on kitkat on it.
I follow this guide: laptopmag(.com)articles/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and whenever I finish, I get a green android laying down with a red caution symbol ontop of him.
But the weird thing is I'm able to install 5.1.1 no issues using the same method, but if I pick anything older... The green android shows up..
Right now I'm back on a fresh 5.1.1 install.
Is there something I'm missing? From all my googling it seems like I should be allowed to installed kitkat no issues on this device. What am I missing?
Click to expand...
Click to collapse
Do you get that android after when you try to boot normally? If you turn it off and turn it back on again normally does it still show up? It is weird if it does because that sounds like the stock recovery, and shouldn't really show up unless you try to boot into it via the bootloader.
When you follow the guide, do you also do the last step, where you interrupt the reboot to lock the bootloader? If you do could you try to let it boot uninterrupted after the update?

theminikiller said:
Do you get that android after when you try to boot normally? If you turn it off and turn it back on again normally does it still show up? It is weird if it does because that sounds like the stock recovery, and shouldn't really show up unless you try to boot into it via the bootloader.
When you follow the guide, do you also do the last step, where you interrupt the reboot to lock the bootloader? If you do could you try to let it boot uninterrupted after the update?
Click to expand...
Click to collapse
Hello, Thank you for replying..
I ran the flash-all.bat from the 4.4.4 image files stock from google and it got this error:
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-04.05'.
Update requires 'FLO-04.02'.
I guess my bootloader is too recent? Google does not want us downgrading?
Update: I ran fastboot oem unlock and was able to run the flash-all.bat
Now i'm waiting on the device to boot up, its currently stuck on a black screen that has white text in the middle saying "google".
Update: It is permastuck on the google screen... I don't know what to do Also to answer your question, yeah I reboot it multiple times. It doesn't work. If I choose "start" from the bootloader it will be stuck on the black google page permanently.
Is there some way I can just wipe the device and install 4.4.4 on it? Kinda like a regular PC?

You need to flash the bootloader before executing the flash-all file. To do that boot into the bootloader then use the command
"fastboot flash bootloader 'bootloader file'"
where bootloader file is the file with bootloader in its name you got from your zip file. Then
"fastboot reboot-bootloader".
Then you can use the flash-all file.

My OnePlus 3 is a brick

Dear XDA Community,
in past 2 months i've been using CM13, constantly having some trouble with apps involving the camera, such as the camera app(surprise) and e.g. snapchat.
So yesterday I decided to update my CM Build, not knowing it would be to CM14 and with this Android 7.
So resulting from this I experienced a lot of issues with different apps, especially the google ones and for example Instagram. I DID NOT Upgrade my twrp, which was pretty stupid as I found out.
So this morning I checked again for CM Updates and Updated to Version Nightly...25 I think... but because I did not update my TWRP it did absolutely nothing except bricking my phone.
I already followed through the Guide for Hard Bricked OP3s (both steps) "http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700"
Though it sadly did not work for me. The Recovery tool and all works but when I want to boot my Phone the md5checksum pops up after the OP3 Logo and it tells me that everythings fine except "boot: failed".
I tried the procedure of the Hard Brick fix over and over again but nothing seems to work. I am fairly new to this whole Custom Rom stuff so I have absolutely no clue what do to.
Does anyone have any idea that could help?
Best Regards
Aliasalex

Try fastboot flashing the whole rom.

how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum

try the 1st method you mentioned in the OP but flash https://www.androidfilehost.com/?fid=24591020540821926 . from what I understand, you need to full write all your partitions since they seems corrupted.

aliasalex said:
how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum
Click to expand...
Click to collapse
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.

Demian3112 said:
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.
Click to expand...
Click to collapse
Yes a Kedacom USB Device "Android ADB Interface" is listed.

aliasalex said:
Yes a Kedacom USB Device "Android ADB Interface" is listed.
Click to expand...
Click to collapse
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk

Demian3112 said:
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk
Click to expand...
Click to collapse
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own

aliasalex said:
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own
Click to expand...
Click to collapse
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.

Demian3112 said:
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.
Click to expand...
Click to collapse
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.

aliasalex said:
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.
Click to expand...
Click to collapse
Nice, whdn you boot you still get those errors in red letter something with "failed boot". Then manually flash the boot. Img provided in the folder where you ran the Unbrick tool from. Command for Fastboot "fastboot devices", then "fastboot flash boot boot.img". Make sure that Kedacom is not in device manager when you are accessing Fastboot.

Oneplus 3 Bricked - Unbrick doesn't work...

Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!

Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.

Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.

min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?

I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...

Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.

drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.

min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...

If recovery, boot or system partition is modified. There's no harm in re locking otherwise..

Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off

Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)

SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?

Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload

SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?

Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working

Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP

SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it

Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.

Moto G6 Play Boot Loop

I'm an idiot and didn't back my stuff up properly. My phone is now stuck in a boot loop with the "hello moto" screen. I tried flashing the stock boot, recovery, and logo img but now it just stays at the moto screen. I have the boost mobile version. How can I fix this?

keznip said:
I'm an idiot and didn't back my stuff up properly. My phone is now stuck in a boot loop with the "hello moto" screen. I tried flashing the stock boot, recovery, and logo img but now it just stays at the moto screen. I have the boost mobile version. How can I fix this?
Click to expand...
Click to collapse
Flash the entire firmware. Not just the certain files. At the least flash the system.img. Those files likley wouldn't need fixed but you Def need system.
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
Flash the entire firmware. Not just the certain files. At the least flash the system.img. Those files likley wouldn't need fixed but you Def need system.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Well I'm new to this and I have no idea how to get the system.img or the firmware. I went by the guide and I got stuck in a boot loop. I've been looking for a fix for an hour now lol

https://r.tapatalk.com/shareLink?ur...share_tid=3792868&share_fid=3793&share_type=t
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
https://r.tapatalk.com/shareLink?ur...share_tid=3792868&share_fid=3793&share_type=t
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
It won't work for some reason. I can't use the command because there are no adb devices found.
Using the command, I get "no suitable package" "remote failure"

keznip said:
It won't work for some reason. I can't use the command because there are no adb devices found.
Using the command, I get "no suitable package" "remote failure"
Click to expand...
Click to collapse
In the bootloader or fastboot as some say the command in cmd starts as "fastboot" without quotes. For example "fastboot devices"

Give more details on how you ended up in this situation. Have you unlocked your bootloader, and verified it unlocked successfully correct?

Xplorer4x4 said:
Give more details on how you ended up in this situation. Have you unlocked your bootloader, and verified it unlocked successfully correct?
Click to expand...
Click to collapse
I got that settled. I'm just trying to figure out how to downgrade to stock before the OTA update so that I can root my phone successfully

I got a boot loop too whie trying to root;
with Lenovo MOTO Smart Assistant I could install android new.
My Moto g6 play XT 1922-5 dual sim got updated to Android 9 even if I wanted Rescue only to get it usable again.
For rooting I could install TWRP; first I got hung with flashing "Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip" and
Magisk-v19.3.zip, then I tried from TWRP to install the files.
I had to format the system partition to get the files installed, then I got no error message during installation but i still got the boot loop.
Tried installing again, same result.
I guess something with the encryption did not work out but with only one phone I could not take screenshots to better document what was going on.
For anybody rooting Moto phones or looking for an android update, the moto smart assistant may be a rescue.

dr.gunther said:
I got a boot loop too whie trying to root;
with Lenovo MOTO Smart Assistant I could install android new.
My Moto g6 play XT 1922-5 dual sim got updated to Android 9 even if I wanted Rescue only to get it usable again.
For rooting I could install TWRP; first I got hung with flashing "Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip" and
Magisk-v19.3.zip, then I tried from TWRP to install the files.
I had to format the system partition to get the files installed, then I got no error message during installation but i still got the boot loop.
Tried installing again, same result.
I guess something with the encryption did not work out but with only one phone I could not take screenshots to better document what was going on.
For anybody rooting Moto phones or looking for an android update, the moto smart assistant may be a rescue.
Click to expand...
Click to collapse
My guide for rooting is literally for your phone and it also comes with instructions for reflashing stock firmware. and there shouldn't be issues as long you READ THE GUIDE so do not skim it I'm sorry but you shouldn't have had these issues at all if you read my guide and followed it's directions. Since YOU are on Android 9 just use the twrp that is SPECIFICALLY made for Android 9 within my guide. As long as you have followed it down to a T it will work....

dr.gunther said:
I got a boot loop too whie trying to root;
with Lenovo MOTO Smart Assistant I could install android new.
My Moto g6 play XT 1922-5 dual sim got updated to Android 9 even if I wanted Rescue only to get it usable again.
For rooting I could install TWRP; first I got hung with flashing "Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip" and
Magisk-v19.3.zip, then I tried from TWRP to install the files.
I had to format the system partition to get the files installed, then I got no error message during installation but i still got the boot loop.
Tried installing again, same result.
I guess something with the encryption did not work out but with only one phone I could not take screenshots to better document what was going on.
For anybody rooting Moto phones or looking for an android update, the moto smart assistant may be a rescue.
Click to expand...
Click to collapse
Format data, not system.

keznip said:
I'm an idiot and didn't back my stuff up properly. My phone is now stuck in a boot loop with the "hello moto" screen. I tried flashing the stock boot, recovery, and logo img but now it just stays at the moto screen. I have the boost mobile version. How can I fix this?
Click to expand...
Click to collapse
Edit: Disregard. The majority of this thread wasn't showing up when I posted my reply.

Hello,
Hello,
thank you for the response.
I wanted to point out a different rescue method that seems to be fairly unknown and was very easy to use.
I will try again to root and log what I am doing.

G6 play root success
Finally I got the G6 (1922-5, with pie) rooted; your way works.
It was a bit more complicated then just trying to follow the steps as good and close as I understood them, compared to other instructions you expect a bit more experience.
I flashed TWRP, it worked the second attempt, but after rebooting I got pie starting again.
From then on I could not access the phone over usb and put Disable_Dm-Verity and Magisk on a microSD card and flashed from there.
The phone is up and running again with root as it should now.
Thank you for the guide and your help.

[Solved] Was updating to Lineage OS 17 but now I'm stuck on stock Android 8

I have the G710EMW variant. As the title states, I was trying to install Lineage OS following sirbow2's thread 'Lineage OS 16/17/GSI Install Guide for LG G7 ULM'. Using the universal unlock method, I unlocked my phone. Next step was installing 21d ULM firmware; this is where I am stuck. When I begin the installation using LGUP, the phone boots into the rooted fastboot mode instead of the download mode. I even tried switching slots but it still boots up in fastboot mode.
Also, when I am able to load the download mode, it stays at the download mode screen & doesn't actually proceed further & neither is the device detected in device manager when it is connected in the download mode.
I've rooted quite a few phones in the past but this one has troubled me a lot. It is very difficult to find time for all this when you're working a full-time job. Please help me fix this. I'm happy even just to return to the stock LG ROM (which reminds me that the same thing happens when I try using the LG Bridge tool).
Thank you!

use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.

sinkoo1979 said:
use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.
Click to expand...
Click to collapse
Already tried that method. Everything works fine until the phone boots to start installation. Ideally it should start in download mode but in my case, it boots into the rooted bootloader.

@Awesomeslayerg was kind enough to message me this link (https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841) which helped me fix my problem.
Not only was I able to revert to stock; I went ahead to install LineageOS 17 which is amazing!
Thank you, Awesomeslayerg.
This thread can be marked as fixed now.