Database Develop

[GUIDE]How unbrick your L5 from a softbrick

After my friends ask me so much for me to do this tutorial for the sake of L5, I decide to do.
If you see your L5 does not start the system, it is the LG logo, follow a tutorial below according to your case.
Note that this guide helps only in cases of softbrick. In cases of hardbrick, I recommend you go to a technical assistance.
If your device is in the boot animation forever:
Probably you should have modified the system and is very easy to recover. Just look for the ROM that you were using normally occur before it and reinstall.
If your device is not out of the LG logo and/or not go to recovery:
1 - Download the drivers here and install: http://depositfiles.org/files/8nbpilxsh
2 - Download the stock ROM here: http://lg-phone-firmware.com/index.php?id_mod=12
Download according to your device!
3 - Go to the download mode.
If the baseband is V10, remove the battery and insert it again (don’t turn it on!). Press and hold volume up button and volume down buttons and connect the device to your computer while holding the buttons.
If the baseband is V20, remove the battery and insert it again (don’t turn it on!). Press and hold volume down an connect the device to your computer while holding the buttons.
If it was not for the recovery, the stronger hold buttons! Worked with me
4 - Download the KDZ updater here http://www.unclenet.de/files/KDZ_FW_UPD_EN.7z
The file contains msxml.msi. Install it first before running the KDZ updater
5 - Start the program.
Leave the options as follows:
Type: 3GQCT
Phone Mode: DIAG
KDZ file: navigate to the file location. KDZ downloaded in step 2 and select.
6 - Click on "launch software update".
The process will take a while. No way, do not disconnect the device from your computer!!!
7 - If still not start, go to the recovery and format
To go to the recovery, will depend on the installed ROM. Each ROM is different. I do not know how to enter the recovery of all ROMs.
When you go to the stock recovery, will automatically format.
(Special case) If your screen looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do as if you were standing in the logo of LG. However, in this case, will not appear on the screen written this in download mode.
To go in download mode, you will have to have plenty of patience to get out of this situation.
Try:
Hold the volume up and connect the PC;
Hold the volume down and connect the PC;
Hold the volume down and up at the same time and connect to PC.
You should try one of these at a time and wait about 10 seconds. While the screen does not look like this, keep trying and holding the stronger buttons.
View attachment 3726726
Make sure it is connected. Go on the control panel, Hardware and Sound, Devices and Printers. If not appear, uninstall the drivers in the device manager and reinstall it.
After that, you just have to install the ROM on KDZ updater.

its a softbrick when it comes and its easy thats right,but whats when we have a real hardbrick?
--SIGNATURE--

-CALIBAN666- said:
its a softbrick when it comes and its easy thats right,but whats when we have a real hardbrick?
--SIGNATURE--
Click to expand...
Click to collapse
I don't know

Amazing man, I appreciate your work

Jonas Cardoso said:
Amazing man, I appreciate your work
Click to expand...
Click to collapse
thanks

Hard brick is when your device won't react to any of your actions.

n0b0dy666 said:
Hard brick is when your device won't react to any of your actions.
Click to expand...
Click to collapse
So all I said is to recover from a soft brick?

Antonio Almeida Filho said:
So all I said is to recover from a soft brick?
Click to expand...
Click to collapse
Yes.
Soft brick; bootloop etc.
Hard brick; phone wont turn on & can not access recovery/download mode.

rhystagram said:
Yes.
Soft brick; bootloop etc.
Hard brick; phone wont turn on & can not access recovery/download mode.
Click to expand...
Click to collapse
Therefore, I have nothing to say about hardbrick. In this case, I would recommend just taking the phone into a technical assistance.

Antonio Almeida Filho said:
Therefore, I have nothing to say about hardbrick. In this case, I would recommend just taking the phone into a technical assistance.
Click to expand...
Click to collapse
Btw... How did this thread ended in XDA Home Page??:silly:

Hardbrick is relatively easy too (just one temporary pull down on eMMC data line, then emergency downloader from SoC is available over usb), though for writing guide/testing software i would need actual genuine hardbrick (mobo of l7 or enough of l5)
But even if i write guide, you will still need to have full eMMC backup, any other way while not impossible, violates xda rules. Otherwise you will have no IMEI (though that state could be still useful)

Unfortunately this sock doesn't support QDL 9008 from what I know. The title is just misleading. There is no hard-brick here.

It does since forever:
MSM7k ARMv7 - over USB
any before - over UART

Guys, I never said that this tutorial is about hardbrick. You probably should have seen it http://www.xda-developers.com/xda-external-link/unbrick-lg-optimus-l5-from-hard-brick/ . I think you should discuss it there, with the guy who spoke that it is a hardbrick guide.

neutrondev said:
Unfortunately this sock doesn't support QDL 9008 from what I know. The title is just misleading. There is no hard-brick here.
Click to expand...
Click to collapse
I DO NOT told at any time that was hardbrick. I'm going for the title which is softbrick. This so good?!

Antonio Almeida Filho said:
I DO NOT told at any time that was hardbrick. I'm going for the title which is softbrick. This so good?!
Click to expand...
Click to collapse
True. My bad mate.

Antonio Almeida Filho said:
Guys, I never said that this tutorial is about hardbrick. You probably should have seen it http://www.xda-developers.com/xda-external-link/unbrick-lg-optimus-l5-from-hard-brick/ . I think you should discuss it there, with the guy who spoke that it is a hardbrick guide.
Click to expand...
Click to collapse
Apologies for the inconvenience caused. I should try and work with more coffee. It was not my intention to cause such harm. The post has been removed.

a.cid said:
Apologies for the inconvenience caused. I should try and work with more coffee. It was not my intention to cause such harm. The post has been removed.
Click to expand...
Click to collapse
Do not get this message as irony, but thank you for that.

LG E 610 Softbrick tried everything MPT Driver fails to load
hi,
i have an LG Optimus L5 (LG-E610) here, it used to have a Stock Android 4.0.3 of nov 06-2012 on it and i tried to put a custom 4.4.4 ROM on it. i had root, Philz Recovery installed and flashed with it: 20 baseband, ROM, gapps, in that order. after it was finished-> reboot system. but the fon would not boot properly and show my a dizzy screeen. after i installed LGMobileDriver_WHQL_Ver_4.2.0.exe and tried flashing V10B_00.kdz with the KDZ_FW_UPD_EN.7z tool. ti said "phone not found" no matter in wich way i used it. after this the fon would not be properly recognised by the win7 x64 pc anymore. the "Android Net MTP device" driver fails to install. some mpt driver used to work before.
after this i also worked with the lg mobile tool und the lg 3.8 mobile driver. uninstalled drivers, used other pcs, virtual oss, lg pc suite. i tried every possible combination of push buttons (i believe) and did with and without battery in the fon. the problem remains. MTP device driver fails to install.
WHAT TO DO?

i have an old device, i cant access the download mode or recovery mode just a white screen, this happen after i was trying to flash a custom recovery (twrp). any have an idea? i just need to enter the download mode, and the kdz wont recognize the device

I can't flash my Xiaomi Mi A2, help me, please.

Hi, I hope you can help me, I tried to install twrp on my Xiaomi but I got an issue, after that issue Any PC recognize my device, I can enter to fastboot mode.
When I try to use miflash or CMD to flash the firmware it only says >waiting for device< even though if it is connected and I have all drivers, I uninstalled and install again but I got the same issue.
I hope Someone can help me, please.

Pictures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kevin2546 said:
Hi, I hope you can help me, I tried to install twrp on my Xiaomi but I got an issue, after that issue Any PC recognize my device, I can enter to fastboot mode.
When I try to use miflash or CMD to flash the firmware it only says >waiting for device< even though if it is connected and I have all drivers, I uninstalled and install again but I got the same issue.
I hope Someone can help me, please.
Click to expand...
Click to collapse
I had the same problem, how I solved it probably is not good to hear...
*Turn off your phone and conect it to PC, see if it's being recognized by your PC, check it out from *device manager* on Windows. If the PC shows something like QDLoader or at least something, your phone is probably auto booting into edl mode, if this is true you can try to flash using miflash
Try fastboot from a PC running Linux.
If these options don't help you, you are probably gonna need to open your phone and short pines, just like I did to revive mine xd
Good luck

Tried
Adairo said:
I had the same problem, how I solved it probably is not good to hear...
*Turn off your phone and conect it to PC, see if it's being recognized by your PC, check it out from *device manager* on Windows. If the PC shows something like QDLoader or at least something, your phone is probably auto booting into edl mode, if this is true you can try to flash using miflash
Try fastboot from a PC running Linux.
If these options don't help you, you are probably gonna need to open your phone and short pines, just like I did to revive mine xd
Good luck
Click to expand...
Click to collapse
I tried to do that, the problem is when I connect my device to PC doesn't recognize, I try un 2 pc's and 1 laptop, always the same issue, I can enter to fastboot mode and that's all, I can't do anything else in the PC cause it couldn't recognize it

kevin2546 said:
I tried to do that, the problem is when I connect my device to PC doesn't recognize, I try un 2 pc's and 1 laptop, always the same issue, I can enter to fastboot mode and that's all, I can't do anything else in the PC cause it couldn't recognize it
Click to expand...
Click to collapse
Duplicated, please delete
---------- Post added at 10:27 AM ---------- Previous post was at 10:27 AM ----------
kevin2546 said:
I tried to do that, the problem is when I connect my device to PC doesn't recognize, I try un 2 pc's and 1 laptop, always the same issue, I can enter to fastboot mode and that's all, I can't do anything else in the PC cause it couldn't recognize it
Click to expand...
Click to collapse
that is exactly the same problem I had weeks ago... if there is no way to make the pc recognize your phone, you'll have to short those pines man, don't be afraid it's easier than it seems to be.

Adairo said:
Duplicated, please delete
---------- Post added at 10:27 AM ---------- Previous post was at 10:27 AM ----------
that is exactly the same problem I had weeks ago... if there is no way to make the pc recognize your phone, you'll have to short those pines man, don't be afraid it's easier than it seems to be.
Click to expand...
Click to collapse
I Understood, do you have a link to check How to do?
I don't want to lose my phone cause is the only one i have

kevin2546 said:
I Understood, do you have a link to check How to do?
I don't want to lose my phone cause is the only one i have
Click to expand...
Click to collapse
*Open your phone
*connect to your PC via USB while you short pines
*Flash stock rom using miflash
Search some pics and videos to watch how to open your device and find those pins
Good luck

[HELP] Phone is stuck at Linux Penguin Logo ( Bootloader, Recovery Not Responding)

Good Morning Guys,
I have Redmi 4X 64GB version. The phone has unlocked bootloader and was running on Havoc OS V2.5 and the phone was rooted.
About a week ago the phone is suddenly got into weird state. And i am unable to figure out what to do.
The phone is gotten into Linux Penguin Logo. I am attaching an image with that problem. And also phone in not responding to any physical power+volume button integration. Any combination just takes me to this Penguin Screen. Here are some thing i have already tried to do but not working at all. Although when i connect this device to computer with this Penguin Logo screen it does get detected as fastboot device but so far that isn't helping.
Some tricks that i have already tried but not working:-
1. I have booted my phone into edl mode and installed fastboot rom via miflash tool, and it is successfully installed but after pressing power+volume button it is the same screen as Penguin Logo. [so Not Working]
2. I have opened the phone disconnect the battery and tried some combinations but still no luck.
3. Used every combination with power button as well as connected to pc and used fastboot commands but not working out.
4. TWRP installation get failed. ( will attach the preview).
So, Please anyone has any clue or anyone has ever face this same problem please reach out to me. Any Honect answer will work.
Sorry i am new at writing thread. So if any mistake i am sorry.
Images:

If you still have custom recovery installed then try flashing latest firmware.
i've found this similar having issue video on youtube of Redmi 3S(Appears to be) and how it got solved, please check it here https://www.youtube.com/watch?v=oMZ08qQrqnc
i am not sure if those files are limited to Redmi 3S or can be use on other xiaomi devices but it gives some sort of idea what you should try. and video language i don't understand and maybe you understand maybe not but should be understandable by watching video.

Thanks for replying. But that is the problem i am unable to reach anywhere not bootloader nor recovery. The phone is just showing the linux penguin logo whether you use power and volume combination or you do the same via connecting to pc.

I think he has that download link in description. But that link requires password for opening .rar file. And i do not trust that guy. That file may have some bloatware or virus or something. If you find same file that he has please share that file over here so that i can use it.
Thanks.

SafvanShaikh said:
I think he has that download link in description. But that link requires password for opening .rar file. And i do not trust that guy. That file may have some bloatware or virus or something. If you find same file that he has please share that file over here so that i can use it.
Thanks.
Click to expand...
Click to collapse
Did you solve the problem? I'm stuck in it and after trying all the things (including deciphering that rar file very doubtful, which I did not achieve) I'm empty of ideas

try to put the phone in edl mode...open the phone case and disconnect the battery wire..if u have tweezer then try touching it to testpoints and then plug the usb cable at the same time...a driver will install on ur computer named (qdloader9008)....open miflash tool then try flashing it via the tool...

Time to use Device as Paper Weight
::
victorkorp1999 said:
Did you solve the problem? I'm stuck in it and after trying all the things (including deciphering that rar file very doubtful, which I did not achieve) I'm empty of ideas
Click to expand...
Click to collapse
Sorry Bro, Nothing is working at all. I mean i am IT Engineer and i have tried all things but still no luck. So, my thinking is the boot loader is too much damaged so there is nothing that can be written on it, no TWRP or no any data partition, it's all out of option. I have started using the phone as Paper Weight.
I am still hoping that someone can solve this problem and get back to me. Fingers Crossed
Thank You.

Not Working, Already tried:
jerry.07 said:
try to put the phone in edl mode...open the phone case and disconnect the battery wire..if u have tweezer then try touching it to testpoints and then plug the usb cable at the same time...a driver will install on ur computer named (qdloader9008)....open miflash tool then try flashing it via the tool...
Click to expand...
Click to collapse
Sorry Bros, Already tried all things that you have mentioned in the post and its not working at all. If somehow we can change the memory storage chip on the phone that contains the bootloader then the phone can come back to its normal form.

Try to turn fastboot if you turn this on then you are on good situation . Boot TWRP and try installing rom again ( with wiping data, cache,vendor,system,dalvik,and might internal storage)

Your problem solved or still u r stuck?

To answer your question, yeah i got it done. Actually where i live, there is repair shop guy that i know he got it done for just 500rs. I don't know how he do that.

Here is my own tested solution for you !
In my case, when i try to install boot logo on Redmi 5 then this happened.
And yet last . i find the great solution by Miassistant
.1. Download Miassistant on PC
2. Download ADB Driver for your Pc
3. Download (Recovery Rom) not Fastboot Rom
5. press volume up + Power for (Miassistant mode)
6. Flash from Miassistant

Thanks for the solution. My device is already fixed, but i this solution can work. If something like this happens in future we can try this out. But i really wanna know what causes this thing to be happened?

Xiaomi Mi 5s Plus stuck in Linux icon FIXED
SafvanShaikh said:
Thanks for the solution. My device is already fixed, but i this solution can work. If something like this happens in future we can try this out. But i really wanna know what causes this thing to be happened?
Click to expand...
Click to collapse
Sorry if this is not the place for post this, but I read a lot of cases that people have their phones stuck in Linux Icon, after a fail installing a ROM, this same case happened to me in a Xiaomi Mi 5 S Plus, one of the devices of Xiaomi, with less support because there were not to much units manufactered.
In mi case, after try to put the device in the fastboot mode, that was impossible I had to put the MI5 s Plus in EDL mode, using the 2 test points pins in the motherboard, and using Miflash for instal a fastboot rom.
I ll explain the steps;
A- Install MiFlash, in your computer, with all the drivers
B-Download a stable Fastboot ROM for your device, you can find it easily in the forums. ( In my case was the "natrium_global_images_V10.2.4.0.OBGMIXM_20190424.0000.00_8.0_global_07f157530a" with MIUI 10 for the Xiaomi MI5 S Plus (natrium) )
C- Put your device in EDL mode
Normally if you are stuck in the linux mode, this is your only solution for put the device in EDL mode, use the 2 test points in the motherboard of the phone.
Check in internet, where are located the test pins in your device, is different for every model. ( I attached a image of the 2 test points in Mi 5 S Plus)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For put the device in EDL mode:
1- Disassemble the back cover of your phone
2- Disconect the battery
3- Connect the usb cable to the phone, but not connect yet to the computer
4-Use something metallic, like a clip, wire, or tweezers, and touch the 2 Test points at the same time in the motherboard and while you re touching this 2 points connect the USB to the computer
5-You ll hear the sound in the computer that recognizes a new device conected, after that you can remove the clip or wire from touching the 2 points in the board of the phone
6-Open Miflash and have to appear a device connected like COM...., If don´t appear , you can make the process again (there is no problem if you make the steps with the MIflash open)
7- Select the option Flash all (clean all) in Miflash for install the fastboot rom
8- If some error appears during the installation, check the fastboot rom, I ll try 2 or 3 differents versions before one that was completely installed without error
9- If the installation is correct, your phone will be restart, and take some minutes for the first boot after the installation.
In my case, with this device and other Xiaomi devices, to put the phone in EDL mode, and install a stable official fastboot rom, was the only solution for this kind of software problems, I hope this post help someone

bro i have the same problem i need get my data how can i get back please help i have my grandmother lst pics in it

SafvanShaikh said:
To answer your question, yeah i got it done. Actually where i live, there is repair shop guy that i know he got it done for just 500rs. I don't know how he do that.
Click to expand...
Click to collapse
bro data recover hoaa ke nahi please tell me

SafvanShaikh said:
To answer your question, yeah i got it done. Actually where i live, there is repair shop guy that i know he got it done for just 500rs. I don't know how he do that.
Click to expand...
Click to collapse
without data loss..., please fast reply given my redmi 3s prime mobile this type problem I attached charging and show bird logo no any start... please contact me 9106142185

[OP7PRO][LATEST OOS 9.5.10 GM31CB] Newest version of T-Mobile MSM tool

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
This MSM tool is only meant for T-Mobile version of OnePlus 7 Pro.
The previous MSM tool shared by @slayerh4x in his thread restore to OOS 9.5.5 while the one I will share in this thread will restore your device to OOS 9.5.9/9.5.10 .
You can download 9.5.9 tool here and 9.5.10 tool here.
Instructions:
Power your device off
Maintain volume up and volume down keys to get into Qualcomm EDL mode.
Launch MsmDownloadTool V4.0.exe.
Click on Enum to be sure your device is detected and press Start.
Wait ~300 seconds
Enjoy your brand new device

FAQ:
My device isn't detected when I click on "Enum" button
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft...f-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
My device doesn't stay in EDL mode for more than 10 seconds
Some units can have this problem and there isn't a lot of things to do to fix that, except being fast after plugging your phone to your computer.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked in first part of this FAQ.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.

Reserved

Credits:
@Titokhan for inspiration in writing
@headsh0t95 for suggesting me to request an access to upload files on AndroidFileHost a few months ago for my previous threads
@AndroidFileHost for the hosting
OnePlus for the device and OS

Added 9.5.10 GM31CB unbrick tool

I used the 9.5.5 MDM tool and it worked fine. Then I got the OTAs for the updates from T-Mobile almost immediately. I believe it was 2 of them.
Thanks for putting this out there! I'll swap it out with the other tool.

Mine just stays asaram pre-processing, and it shows the right device in device mgr. I am on9.5.10 but wanted to go to the international version too. Oh well... Is there a way to check that the phone is in EDL mode?

T-Mobile variant, get stuck at Param preload. Device Manager shows Qualcomm HS-USB QDLoader 9008. See screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, am I missing something or is there no download for the driver OP linked in FAQ?

bobbarker2 said:
T-Mobile variant, get stuck at Param preload. Device Manager shows Qualcomm HS-USB QDLoader 9008. See screenshot below.
Also, am I missing something or is there no download for the driver OP linked in FAQ?
Click to expand...
Click to collapse
Fixed download link in FAQ (source https://www.catalog.update.microsoft.com/Search.aspx?q=Qualcomm Incorporated - Ports - )
Try removing any previous Qualcomm drivers and use the one I linked

CountryEd said:
Mine just stays asaram pre-processing, and it shows the right device in device mgr. I am on9.5.10 but wanted to go to the international version too. Oh well... Is there a way to check that the phone is in EDL mode?
Click to expand...
Click to collapse
Same as above, try using the Qualcomm drivers I linked in FAQ.
The way to check your device is in EDL mode is by looking at COM ports section in your device manager and search for "QDLOADER 9008" or "QHUSB_BULK" mentions.

Should we be able to extract a boot.img from this? Would love to be able to root the stock firmware.
Sent from my GM1915 using Tapatalk

Some_Random_Username said:
Fixed download link in FAQ (source https://www.catalog.update.microsoft.com/Search.aspx?q=Qualcomm Incorporated - Ports - )
Try removing any previous Qualcomm drivers and use the one I linked
Click to expand...
Click to collapse
Which driver? I see multiple drivers that apply to win10

Ok so the download you linked turned my computer from recognizing it QDLoader 9008 to Qualcomm HS-USB Diagnostics 900E. Whats wrong with the L2 Drivers from other threads?

Well thanks for the share I guess. Now I have to figure out how to get rid of the drivers you provided (Uninstall Driver doesn't remove them and cant update manually with L2 Drivers from other threads).

bobbarker2 said:
Ok so the download you linked turned my computer from recognizing it QDLoader 9008 to Qualcomm HS-USB Diagnostics 900E. Whats wrong with the L2 Drivers from other threads?
Click to expand...
Click to collapse
The L2 drivers from other threads can be outdated or not work for some persons, hence why I recommend the one present on Windows Update website (odd they didn't work for you though ...)
bobbarker2 said:
Well thanks for the share I guess. Now I have to figure out how to get rid of the drivers you provided (Uninstall Driver doesn't remove them and cant update manually with L2 Drivers from other threads).
Click to expand...
Click to collapse
Damn, really?
It should normally go away after right clicking on them, selecting Uninstall device and ticking "delete the driver software for this device"

mjdavis871 said:
Should we be able to extract a boot.img from this? Would love to be able to root the stock firmware.
Click to expand...
Click to collapse
I doubt it is possible to extract it from the OPS file itself.
There is however a hidden readback mode which should allow you to extract it from your device running T-Mo software

Some_Random_Username said:
I doubt it is possible to extract it from the OPS file itself.
There is however a hidden readback mode which should allow you to extract it from your device running T-Mo software
Click to expand...
Click to collapse
Where can I find info on that?
Sent from my GM1915 using Tapatalk

mjdavis871 said:
Where can I find info on that?
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
Press F8 while in tool, select the partitions you want to readback, input "oneplus" as password, press "ok" and click on Readback button.
Partitions you selected will be saved to the root of your system drive.
Note also that your device won't reboot automatically to OOS after a readback contrarily to upgrade mode, you will need to use power button to turn it back on.
Source https://forum.xda-developers.com/showpost.php?p=78226654&postcount=88

Some_Random_Username said:
The L2 drivers from other threads can be outdated or not work for some persons, hence why I recommend the one present on Windows Update website (odd they didn't work for you though ...)
Damn, really?
It should normally go away after right clicking on them, selecting Uninstall device and ticking "delete the driver software for this device"
Click to expand...
Click to collapse
I've done this countless times and that didn't work but i figured out a work around. So I got it back the QBLoader device but the driver version is 2.1.2.0. Can't seem to find 2.1.2.2 anywhere.

I'm really thankful you put this together for us, and the FAQ after the OP has some info in it I needed but hadn't seen anywhere else.
On the other hand, I may never get to see your work. I'm looking at a 12 hour download from Android File Host. I hope I don't need to reboot my laptop before tomorrow.

Question Bootloop redmi note 10, Don't get into edl mode

Hallo,
My phone has been in a bootloop for 3 weeks. Bootloader is closed and debugging is not enabled. I'm able to get into fastboot mode and join mode with miassistant. I tried to install the latest recovery firmware via miflash pro, but I always get an error message that the update could not be verified. To rule out that I didn't have the right drivers installed, I tried it with another working redmi note 10 pro, it works and the update is verified. I have tried with xiaomitoolv2, there is also an error message that no suitable recovery can be found. So I wanted to go into edl mode and flash through an authenticated account using Telegram. But I can't get into edl mode. I opened the back and short-circuited the test points, then connected the battery and then to the PC. Windwos only recognizes a "Linux file store gadget USB device" but not Qualcomm. Does it need other drivers than for miflash pro? Or can I assume that the drivers are sufficient because I could flash the cell phone with the test? Does it indicate a defective CPU that I cannot reach the edl mode?
Another question is if it's normal that after removing the midframe I can't turn on the phone with the buttons on the powervolume flex. It only works if I also plug in the power button, but then it doesn't really work well either, only hesitantly or not at all. As soon as the middle frame is back on, all the buttons work very well. Is this normal behavior?

Is
Oliena said:
Hallo,
My phone has been in a bootloop for 3 weeks. Bootloader is closed and debugging is not enabled. I'm able to get into fastboot mode and join mode with miassistant. I tried to install the latest recovery firmware via miflash pro, but I always get an error message that the update could not be verified. To rule out that I didn't have the right drivers installed, I tried it with another working redmi note 10 pro, it works and the update is verified. I have tried with xiaomitoolv2, there is also an error message that no suitable recovery can be found. So I wanted to go into edl mode and flash through an authenticated account using Telegram. But I can't get into edl mode. I opened the back and short-circuited the test points, then connected the battery and then to the PC. Windwos only recognizes a "Linux file store gadget USB device" but not Qualcomm. Does it need other drivers than for miflash pro? Or can I assume that the drivers are sufficient because I could flash the cell phone with the test? Does it indicate a defective CPU that I cannot reach the edl mode?
Another question is if it's normal that after removing the midframe I can't turn on the phone with the buttons on the powervolume flex. It only works if I also plug in the power button, but then it doesn't really work well either, only hesitantly or not at all. As soon as the middle frame is back on, all the buttons work very well. Is this normal behavior?
Click to expand...
Click to collapse
Is your device code named mojito? If it is Mojito it shall show up as Qualcomm Device in device manager given that you have all the drivers installed.
I have a tool which can flash your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

No, the device code is "sweet". No Qualcomm device is displayed in the device manager when I try edl. So I guess I'm not in edl mode. What is this tool that you have, In which mode does the cell phone have to be for the tool?

Oliena said:
No, the device code is "sweet". No Qualcomm device is displayed in the device manager when I try edl. So I guess I'm not in edl mode. What is this tool that you have, In which mode does the cell phone have to be for the tool?
Click to expand...
Click to collapse
Your phone must be in Qualcomm HS USB mode.
Fo your phone you will have to use Avatar Auth tool but this is a paid software and due to XDA policies I cannot provide much information about it.

Ok I understand. I would be willing to use a paid tool or pay someone for an auth account via telegram. But my problem is that I can't get into Qualcomm hs USB mode. Which is why I think it might be a hardware error.

Oliena said:
Ok I understand. I would be willing to use a paid tool or pay someone for an auth account via telegram. But my problem is that I can't get into Qualcomm hs USB mode. Which is why I think it might be a hardware error.
Click to expand...
Click to collapse
I can help you get it into Qualcomm mode.

mvikrant97 said:
I can help you get it into Qualcomm mode.
Click to expand...
Click to collapse
Your phone's EDL point. Please make sure you have Qualcomm drivers installed and also your computer drivers are updated.