Database Info

[HOWTO]Unlock bootloader/root for most G7's except T-Mo via EDL Mode (EASIER METHOD)

Hi everyone!!
IMPORTANT:NEVER SELECT ERASE OR FORMAT PARTITIONS IN LGUP. IT WILL MESS WITH YOUR IMEI
Im making a new guide to unlock your bootloader/root your device. Its easier to do a little bit risker but if you do it slowly you wont mess up your phone and in the event you do you can always recover it. Remember to FOLLOW ALL THE STEPS or you may end up messing up your phone, The best thing is, you dont need to downgrade to even unlock the bootloader!!
DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING THIS GUIDE AND ITS YOUR CHOICE TO DO IT OR NOT TO DO IT AND YOURE THE ONE DOING IT. I JUST WANT TO HELP OTHERS OUT.
If you cant for some reason access fastboot even flashing the v35 file, use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031 it says verizon but i think most of the models of the g7 cant acess fastboot so you can try this.
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
--The LG FIrehose file
- QPST/QFIL
-9008 drivers FOLLOW THIS GUIDE!! To install drivers properly IF WINDOWS DOESNT INSTALL THEM AUTOMATICALLY!!
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Steps.
Download the V35 abl,LG Fire house file, download and install qppst and install the 9008 drivers (WUNDOWS 10 should automatically do it for you) If not, download it and install them.
Boot into edl mode via connecting your phone to the pc then turning it off. Hold Vo- and power and keep pushing the vol+ button multiple times when it turns off.
Go into device manager and check if its detected. to check open up device manager and check Ports and it should say Some port 9009 Qualcomm or something like that (IF theres a question mark, exclamation mark or it says qhusb bulk even after you install the drivers, make sure you disable driver signature enforcment on windows and install the drivers again. Theres multiple ways to do it just google on how to disable driver signature enforcment windows 10. Same with windows 7/8,)
Run as administrator qfil and select flat build,.
--Programmer Type: Load the firehose file
-- On the top go to configuration and where it says Device type, make sure you change it to ufs.
-- Click ok to save and exit
At this point qfil should be detecting your port . If not there should be a select port button next to it on top.
Go to Tools then Partition Manager
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
Search for abl_a and right click on it. First do Read Data, it should take only a couple of seconds Then Load Image and load the v35 image. It should say GPT Finished or something like that at the log with no errors.
Reboot holding volume - and power for like 20-30 seconds until the lg logo comes up Then hold the down button to boot into fastboot or it will automatically boot into fastboot depending on what version of android you are on.
Open the folder where your adb tools are, then hold shift +Right Click in the folder and open powershell. Type and enter CMD
Enter: Fastboot oem unlock it should output with OKAY, If it gives you unknown command, try a USB 2.0 port and then turn off your phone and while its booting up enter the command before you boot into fastboot. Once thats done dont close the window yet!!
Once thats done you can now restore your other abl so you can boot back into android. To do that run %appdata% in the search bar or in the run window by holding the windows button and pressing the R button. Then you should be in C:\Users\{YOUR USERNAME}\AppData\Roaming
Open up the Qualcomm folder --> QFIL --> COMPORT#
There should be a ReadData Blah blah.bin in there. Drag and drop that in the folder where your adb tools are
then go back to the window i told you not to close (The powershell/cmd window) then do fastboot flash abl_a (The file name with ReadData) without the ( ).
Now you can turn off the phone vial holding volume - and power and then reboot into android!! You should get a bootloader unlocked or a cannot be checked for courrption message! Congrats your bootloader is unlocked!!
To root: Just back up your boot image via and then find it in %Appdata% put it in your phone then use magisk manager to patch the boot file and then take that boot file and then flash it to boot_a via edl.
I tried my best to write this guide and sorry for my grammatical mistakes. Ill be helping people unlock/root their bootloaders for free during this covid time as well. If you want to donate you can always tell me but its not necessary.
Ill try making a video as soon as i can.

Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks ?

nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Should be in theory

nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031

netookska05 said:
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031
Click to expand...
Click to collapse
Ill add your link to my thread.

Awesomeslayerg said:
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
-The LG FIrehose file
- QPST/QFIL
-9008 drivers
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Click to expand...
Click to collapse
All the links to files redirect to "Unbrick G7" file.

I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help

TigerV said:
I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help
Click to expand...
Click to collapse
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?

Awesomeslayerg said:
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?
Click to expand...
Click to collapse
Thanks for your update.
Yes I m using the same ELF file from zip.
The driver not installed automatically so I have installed it manually via device manager and thn no exclamation mark. But somehow its not work. Tried many time but the same issue

Can you please update the link of 9008 driver and guide? Its not working (may be bad link)

TigerV said:
Can you please update the link of 9008 driver and guide? Its not working (may be bad link)
Click to expand...
Click to collapse
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.

****.. Unlocked bootloader. Lost Widewine L1. Relocked bootloader again. but Widewine L3 is available. Anyway to get it back to L1. I remember My pixel and Op6 could get back Widewine L1 after relocking bootloader again.

Awesomeslayerg said:
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.
Click to expand...
Click to collapse
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.

TigerV said:
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.
Click to expand...
Click to collapse
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen

Hey op or whomever can help point me in the right direction: when looking at used/refurbished g7's which models should I ask sellers about or steer away from like the LMG710R (I know the LMG710TM is a no go, what about the Sprint unlocked for GSM and what's there code if I want to avoid them?)?
Thanks.

the v35abl file is not avaliable

wente said:
the v35abl file is not avaliable
Click to expand...
Click to collapse
here is the same link from main post (that link has some hyperlink issue)
https://androidfilehost.com/?fid=1899786940962574206

Would this work on LG710N (korean) ??

Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.

Awesomeslayerg said:
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen
Click to expand...
Click to collapse
have tried many many time and all possible way but no luck
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
coolrevi said:
Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.
Click to expand...
Click to collapse
re-lock and stock flash also not in bring back to L1? I can not even unlock my boot-loader. stuck at "fastboot oem unlock" and its not working, tried all possible way

Trying to restore my oneplus.

So i recently decided to update my Oneplus 7 Pro from the public stable release to the OxygenOS 11 Open Beta 3 on a whim. Tried to go back to the old stable release by flashing fastboot roms from Tool All In One and it somehow broke everything, even though I did it multiple times before.
Phone can't boot into anything -- even with stock roms installed. Simply shows the bootloader is unlocked screen and nothing after. I can get into recovery and edl and fastboot, but nothing else. I think I flashed an older version from TAIO's fastboot rom flasher, making it impossible (!) for my computer to interact with my phone.
MSM Tool also doesn't work. Param preload, even though I have the QC and OP drivers installed.
Anything I can do?

You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times

@soka said:
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
Click to expand...
Click to collapse
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).

VictimOfMagic said:
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
Thanks for replying
Click to expand...
Click to collapse
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com

@soka said:
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
Click to expand...
Click to collapse
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao

VictimOfMagic said:
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
Thanks for replying.
Click to expand...
Click to collapse
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.

md5hasher said:
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
Click to expand...
Click to collapse
Running TAIO as an admin? That still only downloads WinUSB.
Can you expand on what you mean?

Under windows 10 open CMD as admin and enter bcdedit /set testsigning on
now reboot. This resolved for me the driver issue and phone was then correctly seen by msm unbrick tool

Cannot get oem unlock token oneplus 8 tmobile (in2017)

So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.

Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml

if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk

PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind

d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp

d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface

DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!

SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?

nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.

FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!

nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.

How to go back to stock OxygenOS on OnePlus 7

So, I flashed LineageOS recovery and installed LineageOS.
This was very buggy for me so I want to go back to stock OxygenOS (11).
I cannot for the love of everything that is holy figure out how to do this.
I downloaded OOS ROMs but I cannot sideload them on the Lineage Recovery.
Also I tried MSM Tools, but this staight up just won't start.
Anyone has a tutorial for me or can tell me what I'm doing wrong?

Fuwlz said:
So, I flashed LineageOS recovery and installed LineageOS.
This was very buggy for me so I want to go back to stock OxygenOS (11).
I cannot for the love of everything that is holy figure out how to do this.
I downloaded OOS ROMs but I cannot sideload them on the Lineage Recovery.
Also I tried MSM Tools, but this staight up just won't start.
Anyone has a tutorial for me or can tell me what I'm doing wrong?
Click to expand...
Click to collapse
Hello, did you follow the instructions here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3954325/
?

Yes, MSM tools just doesn't work

Me too, I can't start this EDL mode, it just goes straight to fastboot.

I did it! I finally was able to use the EDL mode and MSM tool by using an old laptop that had USB2 ports! The laptop I was using had only USB3. After I've installed the Qualcomm drivers on the second laptop, EDL mode started as explained in the guide and MSM found it immediately.
Hope this helps.

WookieTookie said:
I did it! I finally was able to use the EDL mode and MSM tool by using an old laptop that had USB2 ports! The laptop I was using had only USB3. After I've installed the Qualcomm drivers on the second laptop, EDL mode started as explained in the guide and MSM found it immediately.
Hope this helps.
Click to expand...
Click to collapse
Hi,
Just experiencing the same. I would like some help pls !
Tried LineageOS. Not stable enough on OP7 so I want to go back to OOS.
Got OnePlus 7 - 1903 model EU, so I believe it's GM57BA that I have to deal with.
Tried fastboot methods, not successful. I followed this post. Tested this on linux.
Encountered "Flashing is not allowed for Critical Partitions" even though I got :
Code:
❯ fastboot flashing unlock
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
❯ fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Device was stuck during boot (left it about an hour to try, nothing happened).
At some point I faced Qualcomm Crashdump Mode Screen.
Now I think the only option is to go for MSM method but not available for linux, so I switched on windows.
Instructions on this post seem pretty clear but when I plug the phone on PC, device is not recognized, don't know why I can't install phone driver properly (but probably not important at this stage).
Qualcom drivers are installed but I can't get my phone to boot on "EDL mode" ?
vol - and vol + while shutting down/powering on the device, plugged/unplugged to PC (tried few combos).
So device is not recognized and I can't run MSM Enum.
I have probably missed something... if anyone could give a hint on how to do that, I would greatly appreciate it.

Ok so I finally found a way to solve my issue.
Followed instructions from this video.
Basically I had to disable driver signature enforcement on my pc. This allowed me to properly boot on EDL and detect the device using MSM.
Hope this will help

Question Noob who bricked phone trying to root here. Need help.

I didn't know what I was doing and now I'm paying the price (tbf the guides I found weren't very beginner friendly).
I tried installing Magisk on my device. The guides online told me to use a .img file patched by the app and flash it. I did that and now I'm stuck in fastboot mode.
Sorry if I need stuff explained. A lot of this goes over my head and evidence shows that I'm dumb, so bare with me.

You don't flash the boot image or you risk a brick, use fastboot boot boot.img instead. When it boots, open Magisk and do the direct install.
To fix it you'll need to get a stock copy of your boot image and try flashing that or just use the MSM Tool for your device.

karmazogs said:
I didn't know what I was doing and now I'm paying the price (tbf the guides I found weren't very beginner friendly).
I tried installing Magisk on my device. The guides online told me to use a .img file patched by the app and flash it. I did that and now I'm stuck in fastboot mode.
Sorry if I need stuff explained. A lot of this goes over my head and evidence shows that I'm dumb, so bare with me.
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
You can also find the variant for your particular device and MSM the device back to stock. Easy to do. This is how a OnePlus tech remotely fixes a device without being sent in.

mattie_49 said:
Index of /list/Unbrick_Tools
You can also find the variant for your particular device and MSM the device back to stock. Easy to do. This is how a OnePlus tech remotely fixes a device without being sent in.
Click to expand...
Click to collapse
I have the MSM downloader but it says I need a username and password?
EDIT: Nevermind I figured it out.

What does EDL mode look like btw? Is it just a black screen or does it tell you?

karmazogs said:
What does EDL mode look like btw? Is it just a black screen or does it tell you?
Click to expand...
Click to collapse
It's a black screen.

Power off device. Hold vol +/- while inserting usb cable. Should be in EDL mode. PC will make a sound or MSM will say "connected".

First off you could always extract the ROM that you're using by downloading ROM and payload.bin dumper, extract pay load takes a long time please wait till the window closes by itself. Make sure your bootloader is unlocked.
reflash the boot.img over your device through fastboot mode with the extracted boot.img.
Make sure you open command prompt inside the folder that contains the fastboot files and adb files to run fastboot in command prompt. Connect your phone in fastboot mode.
/Fastboot flash boot boot.img
Boot.img has to be located within your fastboot files that you have downloaded. Or if you internally installed with platform-tools then use that specified folder and insert your boot.img there. If you do not command prompt won't be able to locate the file and will fail.
If it does not boot after successfully flashing stock boot.img you will have to follow a tutorial to use MSMtool for OnePlus 9. Depending on what firmware you need download appropriate files,. Make a space on your computer for your files because there will be a lot. Or you could also format data and see if that was the problem before considering MSM tool
You need the correct drivers for EDL mode to function correctly, you also may want to install OnePlus drivers from there website.,
For EDL mode to be detected with OnePlus 9 you must download a driver called
Qualcomm HS-USB QDloader 9008
Anymore questions feel free to PM me I may be able to help and same with some of the other guys on here that have also commented above.