Develop Bugs

Bootloader Unlock and Root Instruction - No Octoplus Box Required

Do you want to bootloader and unlock and root your V35? Do you want to do this yourself? Are you feeling the need for some adventure? If you answered yes to these questions, then you are at the right place. The goal with these instructions is to make the process as smooth and pain-free as possible. These instructions are based upon what I know works through firsthand experience and what I have gathered reading. My experience is with an AT&T branded V350AWM. Others also report success. That said, there can still be problems leading to bricked phone so don’t continue if you are not comfortable with the risk. An unavoidable side-effect of bootloader unlocking is that all data on your phone will be erased. Make a back up if you don’t want to lose it permanently.
This is what you will be doing in a nutshell.
Setting the phone into a baseline Oreo conditions
Extraction of abl, laf, and boot partititions
Installation of the engineering abl and erasing the laf's using QFIL
Unlocking the phone
Flashing to Pie and maybe Q in the future if you want to update from Oreo
Generation and installation of a magisk-patched boot image for root
Upon successful completion, you will have a fresh, bootloader unlocked and rooted phone that is otherwise stock.
Preparation and requirements:
On the hardware side, you will need a PC with MS Windows installed either directly or as a virtual machine and a high quality USB cable designed for data transfer. Older USB 2.0 hardware is preferred when working with LG phones. There is a long list of software to install.
Minimal adb and fastboot
Instructions: https://forum.xda-developers.com/showthread.php?t=2317790
Download: https://www.androidfilehost.com/?fid=746010030569952951
The LG mobile drivers, http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Dev-Patched LGUP
Instructions and warnings in post #6 with thanks to @ChazzMatt: https://forum.xda-developers.com/lg-v35/help/att-v35-unlocked-wont-verizon-t3958765
Download with thanks to @tecknight for the software: https://androidfilehost.com/?fid=11410963190603845019
9008 Port Driver:
https://raw.githubusercontent.com/g...alcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip
QPST with QFIIL
Some basic instructions: https://androidmtk.com/use-qpst-flash-tool
Download: https://qpsttool.com/qpst-tool-v2-7-480
Download and install each of these programs on your PC in the listed order.
You are also going to need some super important supporting files that make all of this magic possible.
The V35 engineering abl that will give you fastboot with thanks to @vlad48 for making it available: https://www.androidfilehost.com/?fid=1395089523397895796. Yes,it says V20, ignore it, it is fine. Extract abl_a and abl_b, and append a “.img” extension to each. Note the locations on your PC for future use.
The recently available emergency download (EDL) firehose that makes direct partition flashing possible released by Biao on Telegram. It is available here:
https://androidfilehost.com/?fid=4349826312261705871
or as an attachment in @Xsavi’s similar and earlier instructions for the V40: https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Note its location for later use.
Troubleshooting:
These instructions assume that your phone boots normally. Even with that there can still be issues due to software drivers and pc-hardware. They can be broadly summarized as a difficulty getting the computer to recognize and communicate with the phone and vice-versa. They arise frequently. If you encounter difficulties, review these troubleshooting tips compiled and written by @ChazzMatt and taken from his V30 WTF instructions.
Look in your ADB folder on your PC and confirm all known Windows file extensions enabled, https://goo.gl/YxLRG5.
Confirm all Windows hidden files and folders are visible, https://goo.gl/1jBKne.
Confirm USB debugging is on in Developer Options, and your PC has authorization for your phone, https://goo.gl/DgojL9.
Install another version of ADB. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
Re-install LG mobile drivers, https://is.gd/Jbrvx1.
Try another USB cable.
Installing this Windows driver found attached to this post, (Thanks @gazzacbr and @FZZF) https://goo.gl/CqqNZT.
Install Google USB driver, (Thanks @s0lidsneak) https://goo.gl/z2Tahw.
Try another USB port on your computer or try cheap USB 2.0 hub, https://is.gd/gM1mM0.
Reboot the computer.
Try another computer. (THIS usually solves the problem, https://goo.gl/x637H1. Kudos if you find an an old Win7 PC, https://goo.gl/EaGMhs.)
Master Reset (full reset of phone using hardware buttons), https://goo.gl/N4LcLD. Phone will be reset anyway after bootloader unlock. Doing it prior may fix something preventing the command from working.
Step 1: Setting an Oreo baseline:
The engineering files for bootloader unlock of the V35 phone are designed to work with Oreo. If you are an Pie or Q, it is highly recommended that you flash back to Oreo. For those of you with the common AT&T V350AWM model that is not on Oreo, there are a couple of points to consider
AT&T does not release flashable roms. If you are on AT&T Pie or eventually Q, there is no going back unless of course you take the time to make a backup of the rom itself. That is not covered in this guide nor am I aware of a guide on how to do this.
AT&T sim-locks its branded V35’s and the menu to unlock is specific to the AT&T rom. You should strongly consider purchasing of a sim-unlock code and applying it before flashing another rom!
To set the baseline:
If you are already on Oreo perform a master reset. To do this, start by turning the phone off. Then press and hold the power and volume - buttons at the same time until you see the LG logo appear. When the LG log appears, release the power button and then press and hold it again while continuing to press the volume – button. Follow the menus to perform the reset.
If you are on Pie or Q, you are going to flash or cross-flash back to Oreo. The kdz's are available for downloaded from https://lg-firmwares.com/lg-lmv350ulm-firmwares/#tab=firmwares. Reports are that roms can be cross-flashed across V35 models with the exception of the Korean V350N. If you are not familiar with the roms, the favored ones are the Google Fi / North American versions for the V350ULM. Down load the latest Oreo version
https://lg-firmwares.com/downloads-file/18971/V350ULM10i_00_NAO_US_OP_0221, md5sum: 64554877b692601d5906d2bdc9691712​To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 2: Partition Extraction, Modification and Bootloader Unlock
Enable “OEM Unlock”: Turn on the phone and go through a minimal set-up process. Next go to Settings→ System→ About Phone→ Software info. Repeatedly tap on “Build Number” until you receive a message that you are now a “Developer”. Next go to Next go to Settings→ System→Developer options. Look for “OEM unlock” and flip the switch to on. Exit the “Settings” menus.
Boot the phone in EDL 9008 mode: The “button dance” to put the phone into EDL mode requires quick hands. To increase the likelihood of success, take the phone out of any case to expose the volume buttons. With the phone fully booted and turned on, connect it to your computer by USB. Press and hold the power and volume – keys at the same time. The phone will likely take a screenshoot, keep holding the buttons, afterwards it will bring up a reboot countdown message. With one second left, start pressing the volume + button while still keeping the power and volume – buttons pressed. The phone will show a black screen and windows with make its connection sound if you succeeded in reaching ECL mode. Release the button immediately. Look at your computer, you should also see an entry in the Windows Device Manager under “Ports” that reads:
“Qualcomm HS-USB QDLoader 9008 (COMXX)”
where XX is the port. The phone will just reboot if you didn’t click the volume + button sufficiently fast. Keep trying, you will eventually succeed. If the screen on the phone does go black and you don't see the phone listed in the Windows Device Manager, then you should check installation of 9008 port driver.
Start and configure QFIL: Go to the Start Menu or whatever passes for it on your Windows computer and fire up QFIL. Survey the screen:
You should see “Qualcomm HS-USB QDLoader 9008 XX” next to “Select Port…”.
There should be small text in the lower right corner that reads “Storage Type:”; Select “ufs”.
There is a subheading near the upper left that reads “Select Build Type”. Tick “Flat Build”.
Now using the “Browse…” button under the “Select Programmer", navigate to the folder that contains the firehose file, “prog_ufs_firehose_Sdm845_lgev40.elf” and select it.
Extract partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look for “abl_a”, “laf_a”, “abl_b”, and “laf_b”.
Right click on “abl_a”
Select “Manage Partition Data”
Select “Read Data…”
Open a folder and navigate to location where the extracted file is located. The QFIL “Status” output shows the location and filename. On my PC, it reads:
“C:\Users\whoiam\AppData\Roaming\Qualcomm\QFIIL\COMPORT_XX\ReadData_ufs_xxxxx.bin” where XX is the port number and the “xxxxx” are details about the partition name. Copy the file to a dedicated folder and rename it “abl_a.img”.
Repeat the this process for “laf_a”, “boot_a”, “abl_b”, “laf_b”, and “boot_b” partitions. Note the locations of these files as back-ups and also for the following section on rooting.
Use QFIL to get fastboot:
Write the engineering abl’s: In QFIL, do the following:
Right click on abl_a.
Select “Manage Partition Data”
Select “Load Image”
In the dialog, Navigate to the location of the engineering abl_a.img file you downloaded in the preparation section, select it, and click “Open”.
Repeat this same procedure for abl_b.
Erase laf’s: In QFIL, do the following:
Right click on “laf_a”
Select “Manage Partition Data”
Select “Erase”
Confirm that you want to erase
Repeat for laf_b.
Unplug the phone from USB
Press and hold the power and volume - buttons until the LG V35 boot logo appears. Allow the phone to reboot.
Turn the phone off.
Unlock the bootloader:
Enter fastboot mode: Hold the volume + button and plug in the USB cable. The phone will boot to a series of menus that include “Start” and “Power off”.
Run a command prompt as Administrator. If necessary navigate to the directory where you installed adb.exe and fastboot.exe.
Check that the phone communicates with fastboot: Type “fastboot devices” and press enter. It should return details about your device. It reads “LMV350AWMxxxxxxx fastboot” with my phone.
Bootloader unlock: Type “fastboot oem unlock”. Congratulations if it reports OK, your phone is now unlocked. If it reports failed then try another USB port on your PC, a better/different cable, and potentially even another PC.
Reboot the phone
Step 3: Restore download mode and flash to desired rom:
If the current version of Oreo is where you want to be then skip to Step 4.
If you want to upgrade to Pie or eventually Q, then you need to restore the laf_a, laf_b, abl_a, and abl_b partitions to recover download mode. It should be clear from what you have done above with QFIL how to do this.
Download the kdz of your desired rom. The Google/NAO version of Pie is recommended and available at this link, https://lg-firmwares.com/downloads-file/22230/V350ULM20f_00_NAO_US_OP_0218.
To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 4: Install Magisk for Root:
Re-enter EDL mode with the above button dance procedure
Extract boot_a and boot_b partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look "boot_a” and “boot_b”.
Generate a Magisk-patched booted image working directly with the phone:
Download a stable version of Magisk Manager from the official website: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445. It should be saved in the “Download” folder.
In Settings, navigate to Apps & Notifications→ Special access → Install unknown apps. Click on File Manager and set it to allowed.
Open the “File Manager” app and navigate to the Download folder.
Select and install the “MagiskManager-v7.5.1.apk” file keeping in mind that the version numbers may be different.
Connect the phone to USB and place it in file transfer mode.
Copy boot_a.img and boot_b.img to the phone Download folder
Start “MagiskManager” and select “Install”. When presented with the option, tap “Select and Patch a File”.
Navigate to the “Downloads” folder where and select boot_a.img.
There will now be a file named “magisk_patched.img” in the “Downloads” folder. Change its name to magisk_patched_a.img.
Repeat this process with boot_b.img.
Install the Magisk-patched boot images using the PC:
Copy the magisk_patched_a.img and magisk_patched_b to the windows computer.
Put the phone into 9008 EDL mode with the button dance described above.
Start QFIL, configure it as described above, and then click on “Tools” in the menu bar of QFIL and Select “Partition Manager”.
Scroll through the list of partitions and locate boot_a. Right click on it and select “Load Image”. Point it to the magisk_patched_a.img file.
Repeat the previous step for boot_b and load the magisk_patched_b.img file
Reboot your rooted phone.
Step 5: Remove Root Checker: (Added 20200409)
I say with sarcasm that another way that LG has made our lives better was to implement a root-check and monitoring system. Many here are familiar with the root check daemon from the V30. There is a root-check disable twrp package to fix this problem. Installation and use of TWRP for the V35 is tricky. Don't worry, there is another way.
Put the phone in USB debug mode
Connect to your computer
With adb from a command prompt on the computer do the following
adb devices <-- If your devices is properly connect and recognized, adb will respond
List of devices attached
LMV350XXXXXXXXX device
adb shell <-- If you have a shell into the phone you will now see
judyp:/ $
pm uninstall -k --user 0 com.lge.srtc <-- This command removes the root checker, if it succeeds you will get the response:
Success
pm uninstall -k --user 0 com.lge.mlt <-- This command removes the LG monitor, if it succeeds you will get the response:
Success
Happy Rooting!

Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?

THANK YOU for this. Seriously. Really well done. I can't wait to try it if I ever get my phone back into shape where I CAN try it. ?

There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse

cmrntnnr said:
There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
Click to expand...
Click to collapse
I was one of those who leaped to the Korean KDZ. Now I am running NAO firmware. Guide looks well written. I might wind up taking the leap. Good job bro!

Thanks, I follow your steps very carfully, and now I have a rooted v35.

Nicely done. Thank yoh for sharing the result.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse
vavoo said:
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Click to expand...
Click to collapse

So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?

I am stuck at Fastboot Mode. It says the "Device state - Unlocked", but when if I choose Start or Power off/on my phone it just goes back into fastboot everytime.
1. I installed and flashed the Pie rom you linked in step 1
2. I turned "Oem unlock" to On.
3. placed the phone in 9008 mode, backed up abl_a, laf_a, boot_a, abl_b, laf_b, and boot_b.
Loaded the img to abl_a and abl_b.
Finally, Erased laf_a and laf_b
4. within fastboot, unlocked bootloader
Any ideas ?

If the phone unlocked, go back into 9008 EDL mode and restore the laf and abl images using your backups. That should get you booting.

dave1567 said:
Any ideas ?
Click to expand...
Click to collapse
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.

vlad48 said:
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
Click to expand...
Click to collapse
I didn't use your bat since it looks like I can still boot into 9008 mode with the button dance method.
Unfortunately, still nothing!
I flashed my abl_a.img and abl_b.img backups I made to the abl_a/b partitions and flashed your FTM_BL.img to my FTM partition, but it didn't seem to do anything except cause some graphical glitches within fastboot menu (everything still functioned though)
Just in case, I re-locked my phone (fastboot oem lock) and started the QFIL process over (flashing with engineered abl_a and abl_b imgs)
Then within fastboot mode, I ran "fastboot oem unlock" a few times because it fails, but finally it went through
Now the phone is unlocked again, but still just always just boots into fastboot mode!

Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.

vlad48 said:
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
Click to expand...
Click to collapse
Unfortunately, I don't understand. Thanks for trying to help though.
Anyways, I managed to fix the problem and I'm all set.
- Restored my laf_a and laf_b partitions
- Booted into download mode and re-installed the pie image with LG Up.
- Was now able to boot normally
- Followed the instructions in the guide to get magisk installed and now I'm all set!
Thanks all and hope this helps someone

I scouted my way through these very same steps a couple weeks ago. Soft bricked my device a couple times ? but eventually got her there. Glad too see a dedicated guide is out now. Only problem I've run into is the ctsprofile:fail problem. Been able to fix with spoof pixel fingerprints but it's not ideal. Still looking for solutions if anyone knows anything.

Iantuition said:
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
Click to expand...
Click to collapse
What is the minimum needed for you to enter download mode? I have backups of most partitions i will be happy to share and you can use Qfil to flash those to get to download mode then use LGUP to flash a normal kdz? If so, let me know.

so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do

Sorry to hear that. The first time I tried to use QFIL I got a Sahara error and could not see partitions. It was resolved by reinstalling the 9008 port driver and then QPST in that order. It happened again later when windows tries to be helpful by automatically reinstalling drivers when the phone is plugged in but with a mode change.
Flowtron3000 said:
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Click to expand...
Click to collapse

Will this help me sim/carrier unlock my v35awm?

Can you lock the bootloader after this is done and keep root? Need it for banking apps.

Unbrick realme x

Hi it's me again
i've bicked my phone last week, it only shows the image of realme and then a text that says the boot/recovery image have been destroyed, the problem with this brick its THE BOOTLOADER ITS BLOCKED AND THE PHONE CANT START THE RECOVERY, so the options are pretty limited, plus my device is china version.
The things and tools that i've been trying are:
*ADB FASTBOOT (i know i already said that the bootloader it's blocked but i had to try)
*Qualcomm snapdragon flash tool QIFL
*Qualcomm premium tool
*XTM Inferno tool
*OPPO download tool
*MSMDownload tool
Yeah, i've tried a few things already (not too much to be honest), but with everyone theres a problem.
Adb dont recognice because its not in fastboot, QIFL needs a xml file but the roms don't have it, and i dont know how to program it, XTM inferno tool dont recognice the device, and oppo and msm download tool needs an account, if anyone knows what can i do now, please let me know, i'm a little bit sad cause i haven't made it to unbrick

So sad that you can't enter fastboot. It seems that means you can't send commands to your phone.
Recently, I saved my "soft brick" China version RMX. I also get "boot/recovery image have been destroyed" notification, but I can enter fastboot mode (power+Volume-), and my fastboot is unlocked. I used "fastboot flash recovery" cammand to flash TWRP and another command for vbmeta (https://forum.xda-developers.com/re...very-unofficial-twrp-realme-x-stable-t3959556). However, the response in "Windows Command Prompt" is "Failed unknown error".
So I decided to power off and charge my phone. After power off, there is thunder icon, a symbol for charging in powe off state, on the screen. Sunddenly, the phone boot into TWRP automaticly. I connected it to my laptop at once and find TWRP MTP service works which means I can copy the 2.6 GB stock Color OS zip (RMX1901CN_flashable_A17.zip, https://forum.xda-developers.com/realme-x/how-to/guide-to-stock-rom-stock-recovery-t3974607
, https://sourceforge.net/projects/rmx1901/files/custom_recovery_StockROM_flashable_files/) to internal storage (/sdcard), and I installed it successfully, though there was "Unmount to mount storage" error when I wiped Data in TWRP.
Reboot to system succesfully and showed Color OS setting guide, which showed at the first time you turn on the phone. Recovery changed to oppo stock Recovery, but the unlocked fastboot mode didn't change.
I am not sure wether the link is useful for cracked MSMDownload tool :https://www.techoxygen.com/msm-download-tool/

00002972 said:
So sad that you can't enter fastboot. It seems that means you can't send commands to your phone.
Recently, I saved my "soft brick" China version RMX. I also get "boot/recovery image have been destroyed" notification, but I can enter fastboot mode (power+Volume-), and my fastboot is unlocked. I used "fastboot flash recovery" cammand to flash TWRP and another command for vbmeta (https://forum.xda-developers.com/re...very-unofficial-twrp-realme-x-stable-t3959556). However, the response in "Windows Command Prompt" is "Failed unknown error".
So I decided to power off and charge my phone. After power off, there is thunder icon, a symbol for charging in powe off state, on the screen. Sunddenly, the phone boot into TWRP automaticly. I connected it to my laptop at once and find TWRP MTP service works which means I can copy the 2.6 GB stock Color OS zip (RMX1901CN_flashable_A17.zip, https://forum.xda-developers.com/realme-x/how-to/guide-to-stock-rom-stock-recovery-t3974607
, https://sourceforge.net/projects/rmx1901/files/custom_recovery_StockROM_flashable_files/) to internal storage (/sdcard), and I installed it successfully, though there was "Unmount to mount storage" error when I wiped Data in TWRP.
Reboot to system succesfully and showed Color OS setting guide, which showed at the first time you turn on the phone. Recovery changed to oppo stock Recovery, but the unlocked fastboot mode didn't change.
I am not sure wether the link is useful for cracked MSMDownload tool :https://www.techoxygen.com/msm-download-tool/
Click to expand...
Click to collapse
Thank you very much, i will keep looking, and will see the tool u shared, any step forward i make i will post it, and thanks again

Flash official ofp format stock ROM in EDL mode might be helpful. The links offer ofp ROM, guide & password for download tool. An XDA post also mentioned this link. But I'm still confused about the difference between RMX1901 and RMX1901EX model. Some custom ROM is universal for India and China variant on XDA .
https://boycracked.com/2019/05/06/official-realme-x-rmx1901-stock-rom/
https://forum.xda-developers.com/realme-x/how-to/color-os-stock-rom-redmi-x-rmx1901-t3952399/page2

00002972 said:
Flash official ofp format stock ROM in EDL mode might be helpful. The links offer ofp ROM, guide & password for download tool. An XDA post also mentioned this link. But I'm still confused about the difference between RMX1901 and RMX1901EX model. Some custom ROM is universal for India and China variant on XDA .
https://boycracked.com/2019/05/06/official-realme-x-rmx1901-stock-rom/
https://forum.xda-developers.com/realme-x/how-to/color-os-stock-rom-redmi-x-rmx1901-t3952399/page2
Click to expand...
Click to collapse
i can´t see the username and password, its what i need to open the msm download tool, i already have downloaded the files

hello bro.
i was having custom recovery and i tried to relock bootloader and now my device is bricked.
i am not able to go in fastboot mode.
please help

imteyajch said:
hello bro.
i was having custom recovery and i tried to relock bootloader and now my device is bricked.
i am not able to go in fastboot mode.
please help
Click to expand...
Click to collapse
Y
Hi dude, at this time I have not found a way to do it without realme tech support, or remote flash tool.
This device needs a “permission” of realme servers to get flashed. If your device is India version you can ask to boy cracker staff, if your device is China version maybe combine file staff can help.
If you have the option of send it to realme tech support, you should take it

Irvinukis said:
Y
Hi dude, at this time I have not found a way to do it without realme tech support, or remote flash tool.
This device needs a “permission” of realme servers to get flashed. If your device is India version you can ask to boy cracker staff, if your device is China version maybe combine file staff can help.
If you have the option of send it to realme tech support, you should take it
Click to expand...
Click to collapse
Its indian version. please help i did many things. i cannot go to booloader and fastboot mode

Bro yesterday I got an update from reami I updated to android 11 my bootloader was not unlocked and update was failed no recovery stuck on logo i Tryed to flash with msm but still no responce its indian version 1901 any solution please ?

But I can't tried ufs

[GUIDE]UNBRICK NOTE 8 PRO - NO Authorised Service Account - YES Fastboot

Hello everyone.
Yesterday I bricked my Xiaomi Redmi Note 8 Pro, and today I managed to unbrick it without requiring anything special (no need for a Authorized Service Account).
I use Linux, so the scripts inside the Stock ROM end with the .sh file extension. If you're using Windows, use the .bat files.
Phone:
Xiaomi Redmi Note 8 Pro 128GB - Begonia (with NFC).
Bricked state:
Constant boot loop;
No access to bootloader;
No access to system;
Access to fastboot.
Phone requirement:
You must be able to load fastboot mode.
PC requirements:
1. You'll need adb tools (SDK Platform-Tools) to communicate with your phone. Official link is below;
2. Download and unpack the Stock ROM linked below.
Instructions:
1. You need to make sure your phone has some power in it;
2. Unpack the Stock Rom and enter its folder (begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global);
3. Put your phone into fastboot mode (Key Combo: Hold the Power button + Volume Down button until the fastboot logo appears);
4. Connect your phone to your PC;
5. Run the flash_all.* scripts according to your operating system:
5.1. Linux: "./flash_all.sh";
5.2. Windows (untested; I'm not using Windows): Run "flash_all.bat" (How to Run a BAT File on Windows);
6. Wait something between 5min to 10min. It's quite fast, and the flashing process is verbose enough.
7. Profit.
F.A.Q.:
1. How did you find this?
Well, none of the unbrick methods in the forum were working, except for the Authorised Service Account one which I didn' t test. I desperately wanted to unbrick my phone by myself, and I thought that it couldn't get worse (it could with a completely blank screen, but I got away with it).
2. Where did you get the Stock ROM from?
I can't remember. It likely was from a xda forum post but I'm unsure. If I can find the original post containing the Stock ROM I used I'll write it here.
3. Which Miui and Android version did you have prior to the brick?
MIUI Global 11.x + Android 9.
4. Which Miui and Android version does the Stock ROM you installed have?
MIUI Global 10.4.2 + Android 9.
5. Can I install any Stock ROM?
As long as it's compatible with your phone version, yes. I recommend not installing a Android 10 Stock ROM because of this: https://forum.xda-developers.com/showpost.php?p=82743011&postcount=3
6. What if can't enter fastboot mode (phone screen in dead blank)?
You won't be able to unbrick your phone using this method. It is worth trying to enter fastboot mode even though your phone has a dead screen, because fastboot might be working anyway (you'll have to test this yourself, as in trying to load fastboot with a blank screen). Read the next question.
7. How can I test if fastboot mode is working?
"adb devices" returns nothing;
"fastboot devices" returns your device (proof it works). Since "fastboot devices" finds your device, you can run the appropriate scripts.
8. What about your Mi Unlock Status before and after the brick?
Before: Unlocked.
After: Unlocked (I thought it would lock the bootloader again, but it didn't).
9. My phone is bricked and I don't know how much battery my phone has left. What should I do?
You should let it turn off due to 0% battery and charge it fully. I do not recommend you flash like I did, without knowing how much battery I had (yes, I took my chances there). As far as I know, any phone in fastboot mode does not charge its battery.
10. Why is fastboot working in your case?
I don't know. I suspect flashing the preloader and the lk from this OP Redmi Note 8 Pro - The Megathread helped, but it's just a hunch.
11. Will you attempt to flash a Custom ROM again?
After taking a break, yes.
12. Is this phone now unbrickable?
As long as fastboot mode works, perhaps. More feedback is required.
Files:
SDK Platform-Tools (adb/fastboot): https://developer.android.com/studio/releases/platform-tools
Stock ROM used: http://bigota.d.miui.com/V10.4.2.0.PGGMIXM/begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global_270117fdb2.tgz
Feedback:
Due to my job I'm currently very short on time during the week to follow this thread, so it would be immensely helpful to have your feedback on this procedure.
Feedback from people who's phones are bricked with blank screens would be very appreciated, specifically if they can enter fastboot mode without any visual cues from their phones. If any bricked state allows fastboot mode, it seems this phone is easily unbrickable.
Thanks:
strongst for his understanding and in reopening this thread.
Compass.

Thread open again
strongst
Forum Moderator

Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?

andrewff2 said:
Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?
Click to expand...
Click to collapse
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.

Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device

andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device
Click to expand...
Click to collapse
That's a shame.
It's worth trying different USB ports, cables etc.
I usually enter fastboot mode first and only then I connect the phone to my PC.
Then "./fastboot devices" and my phone is listed.
Compass.

Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks

andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks
Click to expand...
Click to collapse
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.

Compass Linux said:
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.
Click to expand...
Click to collapse
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad

andrewff2 said:
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad
Click to expand...
Click to collapse
It seems the only solution for you is this (for now): [GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
Which you've probably read already.
I think you either do that or wait to see if another unbrick method appears.
Compass.

I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?

advan93 said:
I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?
Click to expand...
Click to collapse
That's not normal.
What you should see are various files being flashed along with their progress meter.
I'm assuming you're double clicking the .bat file. Instead of doing that, open a CMD Prompt and use that instead.
Compass.

LG G8 G820UM stuck unlocking bootloader plz help?

Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!

durrant111 said:
Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!
Click to expand...
Click to collapse
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.

you can fomat data : - and power before click power

durrant111 said:
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.
Click to expand...
Click to collapse
Boot to EDL mode by holding the vol - and power button while your G8 is plugged in your computer, after you hear a disconnection sound immediately press the vol + until you hear a connection sound from your computer.
Now, open QFIL then look for the abl a and b then flash your backed up abl_a nd abl_b accordingly and reboot. And you're good to go again.

I can help you. Do you fix problem ???

I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm

Anybody?

Ratty696 said:
Anybody?
Click to expand...
Click to collapse
.

Ratty696 said:
I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm
Click to expand...
Click to collapse
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?

armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
Used method in beginning of this thread. Tried flashing backup
armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either

Ratty696 said:
Used method in beginning of this thread. Tried flashing backup
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either
Click to expand...
Click to collapse
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.

armodons said:
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.
Click to expand...
Click to collapse
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.

Ratty696 said:
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.
Click to expand...
Click to collapse
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it

Nobody able to help me?

Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
I'm new to the G8 (not LG), so just now browsing these posts.
First and foremost, this thread shouldn't be in this forum. This forum is for roms, kernels, recoveries and other development.
This thread is a question about a guide (which is in guides forum). This 'question' is not development of a rom, kernel or recovery, it's a question.
I'd suggest, if you want people to respond that can help, ask the question in it's individual guide thread, that's where the people that know the most about it will be. If you get no response in that thread, then maybe think about posting the question in the questions forum.
but here? in dev forum? absolutely the wrong place for a question about a guide.
cheers

Thread moved to Q&A section.
Thanks!
woodman
Senior Moderator

@durrant111
So to the original OP; 2 things; If your device isn't recognized when in fastboot mode, that's because you don't have the right driver installed in WinBlows.
You have to download the LG USB drivers, install them, then in device manager select the "! Android" and install the driver (usually says ADB) and then 'fastboot devices' will see the phone.
Second; if you ever get a message telling you that 'Data Overflow' then you are absolutely making a big mistake. When you did the backup of your abl(s) (and other partitions), you should have renamed then one by one, that way you don't make the mistake of naming the laf_a partition as the abl_a partition (or any name other than what ti should be). If you flash the wrong partition you run the risk of overwriting the nearby partition, which would make the device essentially unusable except only to qfil.
Lastly, yer lucky the device is VZW, as they make their kdz available and you can use use lg up to get back to stock. If it was Sprint or At&t you'd be scrambling to find a qfil or bkerler backup someone luckily made that you come across (a much more unlikely scenario).
Good luck, you've probably already moved on from this, but just in case, thought I'd mention the above.
cheers

Ratty696 said:
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it
Click to expand...
Click to collapse
Unfortunately at&t doesn't make their kdz available. You can be 99.9% positive the only thing this person that wants to charge you 30$ is going to give you is the partitions backed up by qfil or bkerler edl stuff.
With both at&t and sprint, because no kdz, you can only restore (if you didn't back up the files yourself originally), with someone elses backup, and then you have to use qfil or bkerler edl utilities to restore. If you look around in the G8 forums (or the tele group), there's a decent chance someone has already make their backup available.
cheers and good luck.

Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader

Yarib said:
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader
Click to expand...
Click to collapse
Lol no still haven't solved my problem. I need the abl_a and abl_b files for a lg g8 at&t. My phone only goes in fastboot or qfil and Fastboot says its a lmg850um because I tried using the files from my lg g8x and it didn't work. I have also now bricked my lg g8x it only boots into qfil. Any help would be great. My g8x is canada version

Question Stuck in Fastboot, HELP needed

Okay, I messed up.
Device OP9Pro EU version.
Used Updater and updated to O12 and device went to Fastboot mode.
Tried:
to flash/boot twrp - no luck
found fastboot restore rom in 4PDA, flashed, restarted back to fastboot
manually fastboot flash - extracted Oxygen rom with payload dumper - back to fastboot.
Trying to find a way from fastboot to EDL to use msmtool.
HAS ANYONE IDEAS?

ptr21 said:
Okay, I messed up.
Device OP9Pro EU version.
Used Updater and updated to O12 and device went to Fastboot mode.
Tried:
to flash/boot twrp - no luck
found fastboot restore rom in 4PDA, flashed, restarted back to fastboot
manually fastboot flash - extracted Oxygen rom with payload dumper - back to fastboot.
Trying to find a way from fastboot to EDL to use msmtool.
HAS ANYONE IDEAS?
Click to expand...
Click to collapse
Use the MSM unbrick tool and bring it back to android 11!

herrieberry said:
Use the MSM unbrick tool and bring it back to android 11!
Click to expand...
Click to collapse
I cant enter edl mode. Key combinations are useless. Any time I connect phone to PC, it goes to fastboot mode.

It brings you back to android 11.2.2.2 (Razorcortex)

power of the phone
plug in the phone to pc
start msm tool
press vol up, vol down and power button together for a few seconds
tools starts updating the phone

herrieberry said:
It brings you back to android 11.2.2.2 (Razorcortex)
Click to expand...
Click to collapse
How to do - I'm stuck in fastboot, cant enter edl.

herrieberry said:
power of the phone
plug in the phone to pc
start msm tool
press vol up, vol down and power button together for a few seconds
tools starts updating the phone
Click to expand...
Click to collapse
The phone is off.
Any time I connect it ti PC fastboot boots up, no way to enter EDL.

Try to connect it first and then power of?

herrieberry said:
Try to connect it first and then power of?
Click to expand...
Click to collapse
No luck.
I can power off from fastboot menu, 3 seconds and it restarts in fastboot again.

fastboot erase userdata or
fastboot format userdata

MrSteelX said:
fastboot erase userdata or
fastboot format userdata
Click to expand...
Click to collapse
Did.
Back to fastboot again.

OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
that should help to msm phone to working order

MrSteelX said:
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
that should help to msm phone to working order
Click to expand...
Click to collapse
Thanks, but the phone is still stuck in fastboot mode.
I cant enter EDL.
I power off the phone and when I connect phone to PC, it still boots to FASTBOOT, whatever keycombination I use. Every time.

Get msm up and ready.. Click box to use "lite firehose." then power off ur phone from fastboot.. While holding vol buttons plug in and quickly click enum and soon as it says connected click start. I've had samw problem with msm constantly turning phone on. Eventually u will get it. Click box for firehose lite and u shld be good

Shooter7889 said:
Get msm up and ready.. Click box to use "lite firehose." then power off ur phone from fastboot.. While holding vol buttons plug in and quickly click enum and soon as it says connected click start. I've had samw problem with msm constantly turning phone on. Eventually u will get it. Click box for firehose lite and u shld be good
Click to expand...
Click to collapse
I got it... almost.
I established connection, started to flash and DEVICE NOT MATCH IMAGE error appeared.
I am sure I have EU device 2123, selected eu from droplist in MSMtools.
Now What?

Did u click box for "use firehose lite".? If so u either can try unchecking sha256 check or try to find msm for EU

lemonadep_22_E.05_210324.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

ptr21 said:
I got it... almost.
I established connection, started to flash and DEVICE NOT MATCH IMAGE error appeared.
I am sure I have EU device 2123, selected eu from droplist in MSMtools.
Now What?
Click to expand...
Click to collapse
With this options it' s working for me

Option Target select EU

Something I figured out on my 9Pro is that it would only stay in EDL mode for about 10 seconds if nothing was done. It would then boot into recovery or fastboot. Here's how I got mine to work, with the phone powered off I got the MSM tool all set up to go. If your phone is starting up as soon as you plug the cable in make sure you're holding vol up and down while plugging in, otherwise pwr+vol up+vol down. As SOON as the device connects hit the start button on msm tool (if you wait msm tool would not start because the phone was no longer in edl mode). The flash then went through and I was back to Android 11. Hope that helps.
It took a few tries but I got it to work.