Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
UPDATE 2021-02-28
There has lately been discovered a method to flash begonia/begoniain without the need of an authorised Xiaomi account for flashing. Even if one had earlier not implemented the brick protection method (factory preloader + CFW). This means that CFW is not really needed anymore and that many custom roms are moving away from it. So, in case of brick one can follow this detailed guide in order to unbrick without the need for an authorised Xiaomi account for flashing. There is also an explanatory video that may be helpful for some.
UPDATE 2020-02-25
As of 24 Feb 2020 a new method has been found to help RN8p users avoid bricking their devices. It is a preventive measure and NOT a curative, as it cannot help users who haven't already flashed the specific preloader of the engineering ROM version prior to bricking. For more information see the xda thread by @Agent_fabulous.
ORIGINAL POST
I have created this thread in order to share my experience. I have a Redmi Note 8 Pro that was bricked after flashing a wrong boot.img with TWRP. No fastboot, no recovery, no vibration when pressing the power button. The phone was like dead.
The LED turned on when connected to PC with USB cable. The PC recognised the phone for 5 seconds when holding vol+ before connecting the USB cable. It was recognised as "Mediatek USB port " on Device Manager and after 5 seconds, the PC would lose the connection to the device.
It seems that when holding the vol+ button and connecting the phone to the PC with USB cable, the phone enters to DA mode and waits for a signal that is trying to flash the firmware to it. If the signal doesn't come in the first 5 seconds, the device just gets out of DA mode.
MiFlash does not recognise the phone in this state, as this program can be used only for fastboot flashing.
SP Flash tool recognises the device but returns an "ERROR: STATUS_BROM_CMD_FAIL". This is happening because one has to be logged in with an Authorised Service Account simultaneously when trying to flash with SP Flash Tool. If the authorisation passes, the program starts flashing the firmware to the device.
Requirements
1. MiFlashPro (v4.3.1106.23) downloaded on your pc. (It can be found here.)
2. The stock firmware of your device. (Warning! If you have a Chinese device you have to try with the Chinese firmware. Global device with Global firmware etc. Do not try with Global firmware on Chinese device!)
3. An authorised Service Xiaomi Acount.
The Procedure
0. Unzip your device's firmware.
1. Install MiFlashPro.
2. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool/mi and run "account_auth.exe" (Run as administrator). In the window that opens, log in with an authorized Xiaomi Account.
3. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool nad run "flash_tool.exe". The SP_Flash_Tool interface opens. Now you have to select the 3 files:
Download-Agent: (installation_directory)/MiFlashPro/SP_Flash_Tool/MTK_AllInOne_DA_mt6765_mt6785.bin
Scatter-loading File: You will find this one on your stock rom folder, especially on the folder called "images".
Authentication File: (installation_directory)/MiFlashPro/SP_Flash_Tool/auth_sv5.auth
4. Press the "Download" button.
5. Connect the USB cable to your PC but NOT YET to your phone.
6. Hold the vol+ button on your phone pressed and NOW connect the cable to it.
7. The program should now react and start the flashing process without giving an error.
8. Wait for the flashing process to end and enjoy!
Sidenote
You surely wonder where you can find an authorised Xiaomi account.
There are rumors that there are people who connect to your PC with remote-desktop programs and provide the log-in details just when they are needed during the flash process. And they get paid for it (~10-15 USD, maybe more).
Another solution would be some mobile-phone technician in you city. He/She may have an authorised account for fixing the phones locally at the store.
You may also be lucky to have a friend with an authorised account.
But I do not know of a valid way to get an authorised account for yourself at the time and age of writing.
Sidenote 2
If I remember correctly, on an older Xiaomi MTK phone, they managed to bypass the authorisation by using a modified DA file. If you don't want to pay for an authorisation service, you can wait for a while. But it is unknown if/when such a file is going to be released for Redmi Note 8 Pro.
polfrank said:
I have created this thread in order to share my experience. I have a Redmi Note 8 Pro that was bricked after flashing a wrong boot.img with TWRP. No fastboot, no recovery, no vibration when pressing the power button. the phone was like dead.
The LED turned on when connected to PC with USB cable. The PC recognised the phone for 5 seconds when holding vol+ before connecting the USB cable. It was recognised as "Mediatek USB port " on Device Manager and after 5 seconds, the PC would lose the connection to the device.
It seems that when holding the vol+ button and connecting the phone to the PC with USB cable, the phone enters to DA mode and waits for a signal that is trying to flash the firmware to it. If the signal doesn't come in the first 5 seconds, the device just gets out of DA mode.
MiFlash does not recognise the phone in this state, as this program can be used only for fastboot flashing.
SP Flash tool recognises the device but returns an "ERROR: STATUS_BROM_CMD_FAIL". This is happening because one has to be logged in with an Authorised Service Account simultaneously when trying to flash with SP Flash Tool. If the authorisation passes, the program starts flashing the firmware to the device.
Requirements
1. MiFlashPro (v4.3.1106.23) downloaded on your pc. (It can be found here.)
2. The stock firmware of your device. (Warning! If you have a Chinese device you have to try with the Chinese firmware. Global device with Global firmware etc. Do not try with Global firmware on Chinese device!)
3. An authorised Service Xiaomi Acount.
The Procedure
0. Unpack your device's firmware.
1. Install MiFlashPro.
2. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool/mi and run "account_auth.exe" (Run as administrator). In the window that opens, log in with your Xiaomi Account.
3. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool nad run "flash_tool.exe". The SP_Flash_Tool interface opens. Now you have to select the 3 files:
Download-Agent: (installation_directory)/MiFlashPro/SP_Flash_Tool/MTK_AllInOne_DA_mt6765_mt6785.bin
Scatter-loading File: You will find this one on your stock rom folder, especially on the folder called "images".
Authentication File: (installation_directory)/MiFlashPro/SP_Flash_Tool/auth_sv5.auth
4. Press the "Download" button.
5. Connect the USB cable to your PC but NOT YET to your phone.
6. Hold the vol+ button on your phone pressed and NOW connect the cable to it.
7. The program should now react and start the flashing process without giving an error.
8. Wait for the flashing process to end enjoy!
Sidenote
You surely wonder where you can find an authorised Xiaomi account.
There are rumors that there are people who connect to your PC with remote-desktop programs and provide the log-in details just when they are needed during the flash process. And they get paid for it (~10-15 USD, maybe more).
Another solution would be some mobile-phone technician in you city. He/She may have an authorised account for fixing the phones locally at the store.
You may also be lucky to have a friend with an authorised account.
But I do not know of a valid way to get an authorised account for yourself at the time and age of writing.
Sidenote 2
If I remember correctly, on an older Xiaomi MTK phone, they managed to bypass the authorisation by using a modified DA file. If you don't want to pay for an authorisation service, you can wait for a while. But it is unknown if/when such a file is going to be released for Redmi Note 8 Pro.
Click to expand...
Click to collapse
then you can from where for the official account if possible please help I will donate 15usd
itocogan said:
then you can from where for the official account if possible please help I will donate 15usd
Click to expand...
Click to collapse
I am sorry but I don't own an authorized Xiaomi account.
...
hi... my phone has same case with u ... so i try with your method. but at item 5 until 8 cant response with my laptop... can you suggest to me what i must do? ... sorry my english very bad
LepatUbi said:
hi... my phone has same case with u ... so i try with your method. but at item 5 until 8 cant response with my laptop... can you suggest to me what i must do? ... sorry my english very bad
Click to expand...
Click to collapse
Try connecting your phone to the PC with USB cable and then hold pwr+volup buttons for more than 5 seconds. Does it work this way?
polfrank said:
Try connecting your phone to the PC with USB cable and then hold pwr+volup buttons for more than 5 seconds. Does it work this way?
Click to expand...
Click to collapse
no.. dose not work .. i try with off phone >> Hold power + volUp >> connect usb .. it is correct?...
LepatUbi said:
no.. dose not work .. i try with off phone >> Hold power + volUp >> connect usb .. it is correct?...
Click to expand...
Click to collapse
1st way
1. Connect USB cable only to PC
2. Hold vol+ on phone
3. Connect USB cable to phone (while holding vol+)
2nd way
1. Connect USB cable to PC and phone
2. Hold pwr and vol+ for many seconds, until something happens (led turns on and off and phone is detected by the PC).
LepatUbi said:
no.. dose not work .. i try with off phone >> Hold power + volUp >> connect usb .. it is correct?...
Click to expand...
Click to collapse
have u install vcom mtk driver?
polfrank said:
1st way
1. Connect USB cable only to PC
2. Hold vol+ on phone
3. Connect USB cable to phone (while holding vol+)
2nd way
1. Connect USB cable to PC and phone
2. Hold pwr and vol+ for many seconds, until something happens (led turns on and off and phone is detected by the PC).
Click to expand...
Click to collapse
still no effect... do you have other methods?
LepatUbi said:
still no effect... do you have other methods?
Click to expand...
Click to collapse
Unfortunately, these are the only methods that worked for me. In your case I would check these things:
1. Have you installed the right MTK USB driver?
2. Try with another USB port.
3. Try with another USB cable.
polfrank said:
Unfortunately, these are the only methods that worked for me. In your case I would check these things:
1. Have you installed the right MTK USB driver?
2. Try with another USB port.
3. Try with another USB cable.
Click to expand...
Click to collapse
yes.. this link download: http://www.mediafire.com/file/b1xjnx3mj7b7f8y/MTK_USB_All_v1.0.8.zip/file
and i tried with another usb and cable but still cant effect.
All above replying "does not work",, do you all managed to get authorization file??
If so, then kindly do share with all of us.
coolvipcandy said:
All above replying "does not work",, do you all managed to get authorization file??
If so, then kindly do share with all of us.
Click to expand...
Click to collapse
The authorisation file is included in the installation folder of MiFlashPro. It is not the one that is going to make the difference though. The most important thing to do for the process to continue is to log in with an authorized Xiaomi account.
polfrank said:
The authorisation file is included in the installation folder of MiFlashPro. It is not the one that is going to make the difference though. The most important thing to do for the process to continue is to log in with an authorized Xiaomi account.
Click to expand...
Click to collapse
this situation in my computer
So i cant connect my phone with PC..
Your threat actually given me hope to make my redmi note 8 pro power again...
LepatUbi said:
this situation in my computer
So i cant connect my phone with PC..
Your threat actually given me hope to make my redmi note 8 pro power again...
Click to expand...
Click to collapse
Hmm, I really can't think of something else. It seems that you have set up the software as expected and now the only thing that remains is to connect the phone in DA more. But I don't know why it doesn't respond. Hope that you solve it somehow...
Edit: have you tried installing the USB driver with driver signature check disabled in Windows?
polfrank said:
Hmm, I really can't think of something else. It seems that you have set up the software as expected and now the only thing that remains is to connect the phone in DA more. But I don't know why it doesn't respond. Hope that you solve it somehow...
Edit: have you tried installing the USB driver with driver signature check disabled in Windows?
Click to expand...
Click to collapse
i will unistall everything about xiomi.. and will install again in mode driver signature check disabled in Windows. hope this method will success... TQvm my friend
polfrank said:
The authorisation file is included in the installation folder of MiFlashPro. It is not the one that is going to make the difference though. The most important thing to do for the process to continue is to log in with an authorized Xiaomi account.
Click to expand...
Click to collapse
Oh, so its not an either-or situation.
How the people charging for auth keys/ids , getting this from ?
Hi, please try this. Connect to PC then just press volume down button for a minute. If u can get to fastboot then flash or unlock your device again.
If that's not work try press 3 button at the same time for a minute to get to fastboot.
Any feedback is appreciated.
aisidetpipo said:
Hi, please try this. Connect to PC then just press volume down button for a minute. If u can get to fastboot then flash or unlock your device again.
If that's not work try press 3 button at the same time for a minute to get to fastboot.
Any feedback is appreciated.
Click to expand...
Click to collapse
cannot respond in my computer and another computer. it like the same case in first thread by polfrank..
LepatUbi said:
this situation in my computer
View attachment 4872989
So i cant connect my phone with PC..
Your threat actually given me hope to make my redmi note 8 pro power again...
Click to expand...
Click to collapse
when I only run "account_auth.exe" (Run as administrator) it looks like your pics
but when i connect i get this message
LOGIN sucessful
Unauthorized for this operation.
Related
{
"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"
}
UnBrick Leeco Phones - LeEco variants X720/X727 Instructions for X722, X720 and X727
First, yes there is another thread called Unbrick your Le Pro3, tested and working
Consider this thread to be a version 2.0, a companion to that existing thread, with alternative steps and better overall clarity.
The person who created that original thread is no longer active within the Leeco Pro 3 community and the original file links are mostly dead anyway. In addition, the original Qfil file on that thread OP was corrupted and lead to a lot of frustration via countless sahara errors and other issues.
I have tried to support the many people with bricked phones, and over a long period of time, and I made many of those posts on that original thread. It's way too hard to keep things updated on that thread when I can't even find my own original posts.
There is no question that this thread will help me keep relevant information for saving bricks organized, and will better serve people with bricked devices. and maybe help resolve the clutter issue caused by the weekly " Help I bricked my phone" threads that are created almost weekly.
TLDR: The original tested and working has good information, some really nice images to view along with the instructions. But its outdated, has bad links, and a corrupted Qfil. This is too confusing so here is the updated unbrick thread that this community needs.
Note
Before attempting any of these steps : first try just leaving the phone plugged in for a few hours and wait and see if it comes back to life. It is possible that the cable is bad, your battery stats are off, and the battery is simply on 0% Especially if you have a faint blue light, instead of a red light.
X722 Qfil
This thread was inspired by the new X722 Qfil by @F.L.V For the X722 Elite Owners : these instructions will be helpful for the returning X722 users ready to unbrick their devices with the new F.L.V Qfil
Note If you are new here: the X720/X727 models use a different Qfil than the X722
Modes
* Fastboot: * Press and hold the power button and the volume down (minus) to enter fastboot mode.*
* Recovery:* Press and hold the power button and the volume up (plus) to enter Recovery mode.
* Qualcomm FIL AKA "Emergency Download Mode ( Also called ËDL" Press and hold the power key and the volume up and down key ( at same time!) to enter EDL Note, you have to be in EDL mode to see Port 9008
If you can not get the computer to recognise the phone
Try another usb C cable
Try another usb port
Make sure antivirus is disable
Reinstall android drivers
Reboot the computer
Make sure that your user has admin rights
FLASHALL.bat Method
There are several ways to unbrick, flashall.bat is absolutely the easiest and fastest. Instructions and Rom posted on the post link below.
https://forum.xda-developers.com/showpost.php?p=79854585&postcount=90
Qualcomm EDL Mode
Manual Method
You need to press all 3 buttons Volume up and Volume down + the power button simultaneously
Turn*off and press and hold [*Volume button**+**Power button**] for about 10 seconds to enter*fastboot mode
plug in the data cable to connect the computer
ADB Method
Below are instructions to boot into EDL mode for both ADB and Fastboot method.
How to Boot into EDL Mode via ADB
Setup ADB and Fastboot on your Windows PC.
Enable USB debugging on your Android device.
Open a command window on PC and connect your device to PC via USB cable.
Issue the following command via the ADB command line
Code:
adb reboot edl
└ You may get a pop-up screen on your device to authorize ADB, accept it.
Here are the Files
Qfil and Flash 2.0 https://androidfilehost.com/?w=files&flid=244213
[Qualcomm Diag QD-Loader Windows 10 Drivers :https://www.androidbrick.com/downlo...mm-diag-qd-loader-windows-10-drivers-signed/#
Make sure you place and run Flash 2.0 from the root of your PC I.E : C:/
Do not unzip Qfil yet, when selecting it needs to stay a zip file ( you can unzip later if your computer does not extract the needed files)
Qualcomm Drivers: and QPST https://www.qpstflash.com/
Keep these files. In case you ever need them again and if it works for you.*
Alternate Files if links above are broken:
QPST_2.7.104 For Leeco .zip : https://www.androidfilehost.com/?fid=6006931924117912435
QDLoader HS-USB Driver For Leeco.zip : https://www.androidfilehost.com/?fid=6006931924117912434
FlashOne 2.0 For Leeco.zip: https://www.androidfilehost.com/?fid=6006931924117912440
X722 Owners Go Here Make sure you thank and if you can donate a coffee to @F.J.V
Instructions :
Install the "RELINK HS-USB QDLoader 9008" driver
Plug your phone USB cable into the back of your desktop ( those ports usually have more power)
QFIL mode: Press on vol+ and vol- simultaneously while holding power*
Alternate way to get into edit mode ( Press vol+ and vol- while plugging usb into pc. enter in edl mode.
[email protected] Place Qfil in Main Drive: I.E the C or D, etc primary system drive
Once there uncompress your Qfil.zip Note that your directory is now C:\Qfil, or D:\Qfil.
Launch Flash 2.0 main.exe from within the Qfil directory ( Again its: C:\Qfil, or D:\Qfil.)
To start Flash program : Open Flash 2.0 Folder and click "main.exe"
Within Flash app: Click "Flash Type" window select "Qualcomm - flash dead phone"
Refresh> then you will see that port 9008 is now available
Click "Select file and then choose the Leeco "Qfil" Firmware (The path cannot not contain spaces) If you have trouble selecting the file > Right click on file> click properties > then highlight the path and right click copy> Paste into select file window.
Click the "Flash" button at the bottom of the window.
Once completed, disconnect the phone and power on. To exit the Qualcomm Recovery mode, keep the Power Button pressed for about 1 minute or until the phone will vibrate and restart into system.
After restoring your device with Qfil, the phone memory will display the incorrect amount. The solution is to flash the original stock EUI firmware.
After you have performed all of the steps
* Your Le Pro 3 will have the technicians repair version of EUI.
* The phone may not boot automatically.
* Press and hold the Power Button for 30+ seconds and the phone will vibrate
* Release the power button, it will vibrate again after 10-20 seconds*
* The phone will leave the Qualcomm Repair Mode, and will vibrate continuously for 20 seconds or longer.
* In some cases the phone could take as long as 15 minutes to start. But usually it's faster.
* Immediately you will notice that part of your storage is missing, reformat storage to resolve
Repair Storage
Restore to Default Stock Software for your Device
Option 1: Flash your Zl1 Recovery or My Recovery
Option 2 Flash full stock X720 firmware.
Option 3: Push the latest TWRP Recovery and Root to the phone. > Use SuperSu at this stage, as Magisk will not work yet.
You can use the Leeco Official Rom Downloads
Le Pro 3 : http://bug.letv.com/cn/download/phone/56 ( X720/X727)
Elite : http://bug.letv.com/cn/download/phone/80 ( X722 - Use only with ADB )
Custom Rom Install: ( The All in One Tool provides quick easy options for Stock and Custom Rom installation
Once TWRP is installed,
Format storage and reboot to Recovery
Format.> Type yes. then immediately reboot to recovery > you may see a message that no OS is installed, ignore, check to install TWRP
Reboot to Recovery and place files in Storage via your Desktop or Better Yet: Use an OTG Flash Drive and install from it.
Now you are ready to flash a Compatible Rom, Gapps And Magisk
So that is how you unbrick.
If you would rather have a visual guide the embedded link may be easier for you to follow.
Although the link above is for the Leeco Max 2., the steps are identical!
It's not in English: so use Chrome and enable Google Translate
QPST Alternative Method
Go Here: https://forum.xda-developers.com/showpost.php?p=77723528&postcount=2
Remember to only use the files for the your device and the only Qfil that will work for the X720 /X727 is named : Qfil: le_zl1_qfil_ufs_fix
If you have an X722 go to the F.L.V thread linked above for your Qfil file then you can come back here for instructions if needed.
Good luck, be patient, the first time unbricking can be stressful and will sometimes take a while, mostly because you are not familiar with the steps yet. Otherwise it's usually a fast process.
P.S.
Please Do not spam my PM box, these are the only instructions that you need and there is nothing more that I can give you beyond these instructions.
This year I have received possibly hundreds of PM's concerning bricks. ( Not kidding!) Hundreds!
So I can not respond to PM's about bricks, its too much., especially when the majority of these people never read the basic instructions. So any questions or answers concerning unbricking needs to happen here on this thread I apologise, but I will have ignore PM's with questions about de-bricking your device. However, I myself an hopefully others will check this thread often.
Note : If all else fails and you still can't get it and you absolutely need my help: You can mail the phone to me to attempt to debrick it for you for a small nominal fee or it will make a beautiful paperweight.
Hey recently recovered bricked X722 survivors:
Your help is needed here : Please help with supporting people with bricked phones. It will be greatly appreciated, and since most of you guys recovered you phone for free! Why not help out? We should have a lot of experts! [/COLOR][/B]
It Failed : Start Over
Ensure that your antivirus software is turned off it will detect these tools as a malware and delete parts of the file making them useless.
Did I mention that you should turn off antivirus?
To reiterate: trust that nothing bad will happen, you are already bricked, so turn off antivirus or pay someone to unbrick your phone, for you.
Trust that the people who do these type of repairs for a living rarely use antivirus because most "exploits" can often be be removed manually with ease.
Don’t give up so easily if something goes wrong
Simply do a gut check by rethinking and rereading the steps:
Did you follow instructions?
Did you reboot the computer after installing the drivers?
Uninstall and reinstall the drivers then reboot your desktop.
Did you disable Antivirus?
Unless your phone has hardware issues these steps will eventually work.
To reiterate If you device refuses to unbrick
most likely You missed a step!
Its either your cable, your desktop computer, or the device hardware.
Some X727 owners will have success using Qfil and unbricking and still have a black screen > First check that the phone has actually restarted normally, and is not still in EDL repair mode.
If you checked everything and still have this issue, your LCD may likely need to be replaced.
However, there is a couple of other methods which will be added that may resolve this kind of issue.
Go to post #2 and # 3 on this thread for additional ways to unbrick
Hypothetical Hardware Damage repair for cheap steps listed at this post.
One Last thing:
I understand that you are upset about your phone, but I DO NOT want to read your whining and ranting about Leeco using bad parts or the rom had poor development. IT'S YOUR FAULT PERIOD. >>> YOU decided to use custom roms.
Next, If I am spending my time to help you : you should really click thanks or I might be likely ignore your plea's There is nothing more annoying than spending 20- 30 minutes on multiple occasions, attempting to help someone that can't even click a thank you button. I am not collecting likes...it's simply a matter of common courtesy.
Yay you are now un-bricked! If you want to courteous and buy me cup of coffee, for making things easy for you, it will be appreciated. Have a nice day.
tsongming said:
Alternate Way to Unbrick Using the QPST Method
tldr.
Click to expand...
Click to collapse
I finally was able to go through with 100% success on flashing the QPST package via Qfil.
My phone is still on black screen with a strong short vibration everytime i try to turn it on. That's the only sign of life. I can't get the display to show anything to me (it was used only for a month and still is brand new and I don't think that screen is suddenly dead).
Phone still boots into 9008 mode and thats pretty much it. Can't try anything as phone doesn't boot normally. Are there any extra pointers to try the revival?
Alternate Way to Unbrick Using the QPST Method
Keep in mind that issues that remain after using Flash 2.0 or QPST could be caused by your Desktop.
Make sure that antivirus and defender is disabled
Try right clicking on the unknown device listing in Device manager and choose update driver.
Afterwards use the All in One tool to update Android drivers, ADB and allow system wide privileges.
Try another computer if you have one nearby.
Make sure that you are in EDL Qualcomm mode :
QPST - Try Flash 2.0 first before attempting to use QPST. Most of the time Flash 2.0 is a fast and easy way to unbrick your device.
QPST Flash Tool: https://androidmtk.com/download-qpst-flash-tool
B]Update android Drivers on PC, and turn on test signing.[/B]
If your phone is not seen in Device manager:
* Go into QFIL mode: Press on vol+ and vol- simultaneously while holding power*
* Alternate way to get into EDL mode ( Press vol+ and vol- while plugging usb into pc. enter in edl mode. ( See OP for using ADB)
* Now you should be able to see the phone as 9008 Port .
* Install QPST.WIN.x.x installer
* Install Qcom Driver*
* Run Qfil main.exe and set the configuration to download configuration.
* Device Type: Set To UFS,
* Other Options Don't Change. *
* Press Ok To Confirm .
* Select Build Type – Flat Build
* Select Programmer *Choose "Prog _Ufs_Firehose_8996_Ddr.Efl"
* Load *Xml- Choose All Ramprogxxxx —Choose All Pathxxx
* Ensure that you are in EDL mode
* Connect The Usb Cable > Qualcomm Hs-Usb Qdloader 9008 "Port Appears at the top Press Download To Flash , If Flash Failure To Stop , You Need Press Three Key To Power Off Your Phone , And Do Up Step Again To Flash , Try again until successful.
If the steps from the OP and within this QPST post fail:
This link may have additional things to try: http://en.miui.com/thread-266598-1-1.html
If none of this works you unfortunately have a hardware based problem.
Once you have restored your phone, you will need to repair your storage space.. You can do repair several ways. I would suggest that you use one of the two options below:
You could flash my recovery: https://forum.xda-developers.com/le-...clean-t3727920
It has Magisk and Root, though it would need to be updated. But, it will restore you partitions. > From here you can quickly return to using custom roms.
Another Option is return to full stock with the stock Rom : http://ota.scloud.lfengmobile.com/ot...41S-5.9.02.zip
Note this needs to be flashed via ADB or by using the All In One Tool ; it will remove all data from phone and restore the phone as if it just came out of the box.
Edit :
Another version of Official Stock: http://bug.letv.com/cn/download/phone/56
Once the phone is restored by Qfil to the Technicians Repair copy
Boot into fastboot, You can push TWRP and SuperSU to your device as long as its unlocked
Another option
Download the stock Rom, change its name to "update.zip" then use Leeco's Recovery mode to install the software.
Unlock Bootloader and Flash Roms, Gapps and Magisk
HOW TO INSTALL TWRP
Enable developer options
Allow oem unlock
Power off
Hold Volume down + Power for Fastboot mode
fastboot oem unlock-go
fastboot boot twrp.img
adb push twrp.img /sdcard/
Choose "Install" and then "Install Image"
Select twrp.img
Select Partition "Recovery"
Confirm Flash
Reboot to recovery
One more method to try : Flash-all.bat
The .bat file It will automatically flash all of the boot images to the phone. Afterwards your device will be fully restored to stock.
Here is the file: https://androidfilehost.com/?fid=673956719939836266
i did the qfil flash everything went perfect but the eui is a dev version and it thinks my phone is x720 and its on 5.8.415d how do i go back to eui 5.8.21s
Coconut tree said:
i did the qfil flash everything went perfect but the eui is a dev version and it thinks my phone is x720 and its on 5.8.415d how do i go back to eui 5.8.21s
Click to expand...
Click to collapse
This is an edited duplicate post to ensure not only that you get the message, but to benefit others, by making a change to the reserved spot above
Follow instructions here: https://forum.xda-developers.com/showpost.php?p=77723530&postcount=3
After you have restored your phone to full stock : you would need to start from the beginning, to use custom Roms again : I.E, unlock the bootloader etc.
tsongming said:
This is a duplicate post to ensure that you see it, and for the benefit of others.
You could flash my recovery: https://forum.xda-developers.com/le-...clean-t3727920
It has Magisk and Root, though it would need to be updated. but, it will restore you partitions.
Another Option is full stock, http://ota.scloud.lfengmobile.com/ot...41S-5.9.02.zip
Note this needs to be flashed via ADB or the All In One Tool ; it will remove all data from phone and restorte the phone as if it just came out of the box.
To use custom Roms again you would need to start from the beginning.
Click to expand...
Click to collapse
Umm first thank you very much I followed your instructions on how to unbrick my phone it worked but I don't have TWRP and for some reason my phone won't connect to my PC can that file be flash via the stock recovery?
Coconut tree said:
Umm first thank you very much I followed your instructions on how to unbrick my phone it worked but I don't have TWRP and for some reason my phone won't connect to my PC can that file be flash via the stock recovery?
Click to expand...
Click to collapse
Okay,
While in fastboot, You can push TWRP and SuperSU to your device as long as its unlocked
Another option
Download the stock Rom, change its name to "update.zip" then use Leeco's Recovery mode to install the software.
Edit: I a made an Addendum to the post above, with steps you may find helpful
tsongming said:
Okay,
While in fastboot, You can push TWRP and SuperSU to your device as long as its unlocked
Another option
Download the stock Rom, change its name to "update.zip" then use Leeco's Recovery mode to install the software.
Edit: I a made an Addendum to the post above, with steps you may find helpful
Click to expand...
Click to collapse
I appreciate all of your help but I've been searching for the stock ROM for days and can't find it I'm only finding the eui 5.8.28s for the x720 model and I heard that update has lots of bug's with the playstore
Coconut tree said:
I appreciate all of your help but I've been searching for the stock ROM for days and can't find it I'm only finding the eui 5.8.28s for the x720 model and I heard that update has lots of bug's with the playstore
Click to expand...
Click to collapse
Use this thread
https://forum.xda-developers.com/le-pro3/development/le-eco-pro-3-x727-twrp-backup-clean-t3727920
andrew2401 said:
Use this thread
https://forum.xda-developers.com/le-pro3/development/le-eco-pro-3-x727-twrp-backup-clean-t3727920
Click to expand...
Click to collapse
I've read everything on the tread but sorry for the stupid question I'm a noob but it looks like that back up is from TWRP but I'm using leeco stock recovery where I live data is very expensive so I want to know if it will work before wasting my data downloading it??
Coconut tree said:
I've read everything on the tread but sorry for the stupid question I'm a noob but it looks like that back up is from TWRP but I'm using leeco stock recovery where I live data is very expensive so I want to know if it will work before wasting my data downloading it??
Click to expand...
Click to collapse
If your plan is to return to custom Roms, do what I mentioned earlier.
Push TWRP and SU to your device.
Then boot to TWRP, your storage folder will now be accessible by your desktop computer. If you do not own an OTG adapter, buy one it makes using custom Roms a thousand times easier. They usually cost $3, and you can buy them at Walmart.
Download my Recovery, and unzip the file inside the TWRP folder, in storage. ( This path can only be this deep: Sd/twrp/Brbxxxx/files here ( don't created and name any additional folders after Brbxxxx)
Next boot to Twrp recovery, and click restore, selecting everything.
Now you will have clean stock with TWRP, and Magisk.
From there flash you flash you the latest TWRP...Again yes, the Recovery overwrote TWRP.
Next flash your Rom, Gapps and the very latest Magisk.
If you would rather have stock, there are plenty of versions of stock all over the internet...Every version. When I return home, I will see if I can find a link, or you can just Google " Leeco X720 Stock firmware"
If you foliar stock of Lt flash from And or the AllinOne Tool.
Sent from my LeEco LEX727 using XDA Labs
Okay here is stock 5.8.26.
I added it to my personal mega drive.
Here is the link from my drive
https://mega.nz/#!xB5ggKbQ!OeJbUAGKmlk6AZlzfMjxSGK8OnBkiYsDvdeekTauRag
Yes, it for a X720. It doesn't matter, the X720 and X727 ate the same with the exception of the Sim card, simply flash the radio driver"firmware" from the x727 5.8.20s to remind the phone that it is a X727.
Reminder, I have an X727. My recovery is a X727 5.8.20s recovery.
Sent from my LeEco LEX727 using XDA Labs
tsongming said:
Okay here is stock 5.8.26.
I added it to my personal mega drive.
Here is the link from my drive
https://mega.nz/#!xB5ggKbQ!OeJbUAGKmlk6AZlzfMjxSGK8OnBkiYsDvdeekTauRag
Yes, it for a X720. It doesn't matter, the X720 and X727 ate the same with the exception of the Sim card, simply flash the radio driver"firmware" from the x727 5.8.20s to remind the phone that it is a X727.
Reminder, I have an X727. My recovery is a X727 5.8.20s recovery.
Click to expand...
Click to collapse
Thanks ? and I'm planning on staying on my stock recovery and ROM but I don't think you're noticing that I'm saying I don't have TWRP on my phone and my phone won't connect to my PC is there any way to update without a PC and TWRP?
Coconut tree said:
Thanks and I'm planning on staying on my stock recovery and ROM but I don't think you're noticing that I'm saying I don't have TWRP on my phone and my phone won't connect to my PC is there any way to update without a PC and TWRP?
Click to expand...
Click to collapse
First you can download the stock rom on the phone, then rename it to update.zip
Then boot to Leeco Recovery and install the stock Rom as a n update,.
If your computer is not seeing the phone, its either a driver issue ( Android USB driver) or the Firewall/Antivirus,
It could also be a corrupted user account. BTW, the account must have admin privileges. If all else fails use a different computer.
Since you restored the phone via Qfil,
Don't forget to enable developer options
Enable usb debugging,
set to MTP File transfer
OEM Unlock is selected.
The All in One tool should be able to show whether or not the bootloader is unlocked, while in fastboot mode.
Now that your phone is fixed read my signature.
Coconut tree said:
Thanks and I'm planning on staying on my stock recovery and ROM but I don't think you're noticing that I'm saying I don't have TWRP on my phone and my phone won't connect to my PC is there any way to update without a PC and TWRP?
Click to expand...
Click to collapse
no luck i downloaded the file change the name to update.zip and i got a error (failed to update cause:corrupted)
Coconut tree said:
no luck i downloaded the file change the name to update.zip and i got a error (failed to update cause:corrupted)
Click to expand...
Click to collapse
It is really beginning to sound like you skipped a step
Did you do this part?
After your phone boots, you will see that its storage is abnormally 9.71 GB, to fix this just factory reset your phone choosing the option “Format Virtual SD card”. File system will be restored to normal values.
Now there should be no reason why the phone is not seen by your computer, and you cannot install a factory Rom. Unless the phone has hardware damage. ( which would not make sense since you were able to unbrick the phone ) In addition, did you try another desktop user, removing the android drivers and reinstalling? Worst case scenario, if you can't get it PM me, you can mail the phone to me and I will fix it for you ( This happens alot )
tsongming said:
It is really beginning to sound like you skipped a step
Did you do this part?
After your phone boots, you will see that its storage is abnormally 9.71 GB, to fix this just factory reset your phone choosing the option “Format Virtual SD card”. File system will be restored to normal values.
Now there should be no reason why the phone is not seen by your computer, and you cannot install a factory Rom. Unless the phone has hardware damage. ( which would not make sense since you were able to unbrick the phone ) In addition, did you try another desktop user, removing the android drivers and reinstalling? Worst case scenario, if you can't get it PM me, you can mail the phone to me and I will fix it for you ( This happens alot )
Click to expand...
Click to collapse
Well yeah that's the weird part my phone would only charge when it's connected to my computer but windows 10 says it's damage but I did the qfil part without any problem and yes I factory reset my phone so that doesn't make any sense and I tried installing TWRP but no luck I ordered a USB port replacement hope that's the problem. And I would mail you my phone but I'm only 15 and I live in the Caribbean
Coconut tree said:
Well yeah that's the weird part my phone would only charge when it's connected to my computer but windows 10 says it's damage but I did the qfil part without any problem and yes I factory reset my phone so that doesn't make any sense and I tried installing TWRP but no luck I ordered a USB port replacement hope that's the problem. And I would mail you my phone but I'm only 15 and I live in the Caribbean
Click to expand...
Click to collapse
Okay no worries,
I am not totally convinced that there is an issue with the usb card, although it is possible.
Can you get access to another computer?
If so place all of your files ( All in One tool, Drivers, firmware, Rom, Gapps, Root etc) on a flash drive and take them with you..
If you can simply get a computer to see the phone again, you will be good to go> A computer with Linux would be a great option for testing the connectivity and proving that the issue lies with the Windows drivers or something that is blocking the connection ( Antivirus, etc)
On Windows: Go to the Control Manager> System > Device manager > then go to where it has USB and see if it lists the phone as a unknown device.or by name
If it does, that is the issue. Just uninstall flash 2.0, the qualcomm drivers, and te android usb driver and then reinstall, it could resolve the issue for good.
If you order the card it can be tricky because some of those card come with the option of two flex cable options such as this : You want this one Yellow Flex Cable
In fact, most of the time the issue is just the cable and not the card, those cables, have been known to go bad.
tsongming said:
Okay no worries,
I am not totally convinced that there is an issue with the usb card, although it is possible.
Can you get access to another computer?
If so place all of your files ( All in One tool, Drivers, firmware, Rom, Gapps, Root etc) on a flash drive and take them with you..
If you can simply get a computer to see the phone again, you will be good to go> A computer with Linux would be a great option for testing the connectivity and proving that the issue lies with the Windows drivers or something that is blocking the connection ( Antivirus, etc)
On Windows: Go to the Control Manager> System > Device manager > then go to where it has USB and see if it lists the phone as a unknown device.or by name
If it does, that is the issue. Just uninstall flash 2.0, the qualcomm drivers, and te android usb driver and then reinstall, it could resolve the issue for good.
If you order the card it can be tricky because some of those card come with the option of two flex cable options such as this : You want this one Yellow Flex Cable
In fact, most of the time the issue is just the cable and not the card, those cables, have been known to go bad.
Click to expand...
Click to collapse
I tried it on a different PC still no luck even after uninstalling those you mentioned the weird part is i got my phone to put up in fastboot mode but it was giving me a weird error failed (command write failed (no error))..... I was using the dev rom for a few hours it's pretty stable (but constant red light flashing on the screen "strick mode off in developer options" and phone constantly loosing signal I'm planning on giving up ??? all i want to do is get back to eui 19,20,21s for the American version but it's impossible to find the stock rom online
Coconut tree said:
I tried it on a different PC still no luck even after uninstalling those you mentioned the weird part is i got my phone to put up in fastboot mode but it was giving me a weird error failed (command write failed (no error))..... I was using the dev rom for a few hours it's pretty stable (but constant red light flashing on the screen "strick mode off in developer options" and phone constantly loosing signal I'm planning on giving up ? all i want to do is get back to eui 19,20,21s for the American version but it's impossible to find the stock rom online
Click to expand...
Click to collapse
Le Pro 3 : http://bug.letv.com/cn/download/phone/56 ( X720/X727)
Edit the link above is the current Official stock : Remember that I gave you the link to an earlier version in Post 2 : https://forum.xda-developers.com/showpost.php?p=77723530&postcount=3
I'm only using all caps in hopes that more people will see what i write while in sp flash tools if you hold down ctrl alt plus v it will enter into an advanced mode which gives you considerably more flashing options plus recognition options for the device and computer i've never seen anyone mention this advanced mode before it baffles me using this method of advanced mode is what got my phone to flash without an authorized account i hope this helps other people thank you
Sherfield41 said:
I'm only using all caps in hopes that more people will see what i write while in sp flash tools if you hold down ctrl alt plus v it will enter into an advanced mode which gives you considerably more flashing options plus recognition options for the device and computer i've never seen anyone mention this advanced mode before it baffles me using this method of advanced mode is what got my phone to flash without an authorized account i hope this helps other people thank you
Click to expand...
Click to collapse
What version of my flash?
Geison Bourne said:
What version of my flash?
Click to expand...
Click to collapse
I used file "SP_Flash_Tool-5.1924_Win.zip"
And once I ran the file using administrator privileges I press Ctrl alt + v to enter advanced mode be advised that yes my phone was hard bricked, no fastboot no recovery no vibration when holding power plus volume or minus volume I only had LED light when hooked up to computer I had to remove battery but it did flash completely without the need for activated or upgraded deep flash xiaomi account or whatever you call the account
Bro, my pc can't detect my phone without battery
Sherfield41 said:
I'm only using all caps in hopes that more people will see what i write while in sp flash tools if you hold down ctrl alt plus v it will enter into an advanced mode which gives you considerably more flashing options plus recognition options for the device and computer i've never seen anyone mention this advanced mode before it baffles me using this method of advanced mode is what got my phone to flash without an authorized account i hope this helps other people thank you
Click to expand...
Click to collapse
Ok Bro I just entered that advanced mode in MiFlash Pro / SP Flash tool but what next, can you give us some little tutorial?
adrian1234a said:
Bro, my pc can't detect my phone without battery
Click to expand...
Click to collapse
what version of windows are you using? Try not to get frustrated or offended from the questions I ask I'm just trying to figure out where you are and where your computer is as far as preparedness. What drivers did you install for detection of the phone? when you installed those drivers did you install them while your computer was booted into disable driver signature verification mode? When you have SP flash tools open also open device manager and move it to the side so you can see actions in real time. What happens when you plug in the phone while holding button combinations? Do you see any changes in the device manager? If so what com's come up? There should be at least 2 variantes each with a different port number/com possibly up to 4.
As far as what should be selected once you're in advanced mode for the SP flash tools that's impossible for me to give definite answer for every single computer due to setup variance, hardware implications, and even computer brand names that treat different devices unfairly. But obviously under configuration go to connection if your battery is connected then check with battery if you have disconnected the battery then check without battery sometimes USB 3 can cause issues with flashing if you only have USB 3 then try the full speed option instead of high speed.
kamyk70 said:
Ok Bro I just entered that advanced mode in MiFlash Pro / SP Flash tool but what next, can you give us some little tutorial?
Click to expand...
Click to collapse
please be more specific with your questions and requests because I would be here all your long trying to type out every possible scenario with my own mind making the scenario so I'm happy to answer any questions but just please try to be more to the point don't be offended by that comment I'm just an a****** when it comes to trying to figure out how to say things politely.
what version of windows are you using? Try not to get frustrated or offended from the questions I ask I'm just trying to figure out where you are and where your computer is as far as preparedness. What drivers did you install for detection of the phone? when you installed those drivers did you install them while your computer was booted into disable driver signature verification mode? When you have SP flash tools open also open device manager and move it to the side so you can see actions in real time. What happens when you plug in the phone while holding button combinations? Do you see any changes in the device manager? If so what com's come up? There should be at least 2 variantes each with a different port number/com possibly up to 4.
As far as what should be selected once you're in advanced mode for the SP flash tools that's impossible for me to give definite answer for every single computer due to setup variance, hardware implications, and even computer brand names that treat different devices unfairly. But obviously under configuration go to connection if your battery is connected then check with battery if you have disconnected the battery then check without battery sometimes USB 3 can cause issues with flashing if you only have USB 3 then try the full speed option instead of high speed.
It won't work without an approved account ... absolutely ...
Hey all,
So i've unlocked by bootloader, flashed a custom recovery to then proceed with LineageOS flashing. However it went completely wrong as on reboot i'm stuck with the bootloader unlocked warning and then a blackscreen.
I still have access to fastboot mode however it's impossible to flash a customer recovery ("No Such Partition") and also impossible to directly "fastboot boot recovery.img" as the phone simply reboots on the warning and then blackscreen.
The only solution seems to get the device to qualcomm EDL mode and reflash all with the MSM tool (which I have as well as all the drivers) however I cannot get my Oneplus 9 pro to EDL mode...
I've tried all the fastboot commands (fastboot oem EDL, fastboot reboot EDL, none of them work) as well as the combination volume UP + volume DOWN + plugging the cable (it just boots the fastboot mode.
Honestly would greatly appreciate any help as it is the first time in a decade I hard bricked a phone like this as it seems all the partitions are broken.
Make sure you have it unplugged when you do the button combos, as it will just start to boot while it's plugged in. Also, if you can reach fastboot, you can almost definitely reach EDL. Try unplugging and holding power+vol up for a bit which forces it to completely power off. Then try getting into EDL through the normal button combo/plugging. This is what I had to do since once it got into the booting/no-booting cycle I couldn't get to EDL.
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Good advice above.
Last time I couldn't reach EDL with my previous phone, it turned out to be an issue with the drivers I had installed. I uninstalled all Android-related drivers including some generic thing that showed up in device manager when plugging in the phone, then reinstalled the latest Qualcomm drivers.
Also possibly try a different USB cable if you have one. My OP9P didn't show up when the cable it came with was plugged into my USB-C port for some reason, but it worked fine with a generic Type-A to C cable I had sitting around.
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Tornadeur said:
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Click to expand...
Click to collapse
I can fix it bro pm me telegram .. @Hunar71
Hunar999 said:
I can fix it bro pm me telegram .. @Hunar71
Click to expand...
Click to collapse
Can you help me too, I have exactly the same problem…
If you use Windows, you need to see "QDLOADER 9008" in Device Manager > Portable Devices.
When you got this it will work, 100% .
It worked for me a few days ago. My laptop runs on Windows 11 x64. And only have usb 3.0. NO usb 2.0.
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Alberhasky said:
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Click to expand...
Click to collapse
Yeah make sure it's exactly the same name of that driver - worked for me on oneplus 9
If you have access to fastboot still. Try switching slots. Then going into EDL
For anyone looking for help, please DM me.
djsubterrain said:
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Click to expand...
Click to collapse
Thanks a lot man. Saved my Day. First 9Pro successfully restored ;-) Thank you and merry Christmas to all.
Guys I do not need to use the MSM Tool Anywhere until I reach the step where my device is being successfully detected as "QDLOADER 9008" in my windows device manager correct?
Or does the MSM Application need to be running when I reboot to EDL mode?
I am following this guide.
Please help
I always have phone powered off, and while holding both volume keys I plug it into USB cord(that is already plugged to pc) and then click on enum(button in msm screen) until it says connected then hurry and click start. Once it starts I can let go of volume keys.. Also more than likely u will need to click the box to "use lite firehose" or "Sahara communicaion" will keep failing.
make sure you have oneplus 9 pro drivers and " qaulcomm incorporated - Ports" Driver) and ("qaulcomm communications inc-Net" Driver) so your phone in edl which will be already most likely be running before you plug it in. just hold down both volume buttons and plug in to the usb port to your pc and release once plugged in and start the msm tool and hit enum it should say connect provided that you have all the necessary drivers above so the pc usb port will be able to communicate/recognize you device. its never usually A 1 and done type of thing. everytime i brick my phone its always the 100th try before i get a com port connected and the software communicating successfully, so just be patient and take your time. you will get it back up and running,
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
can't get into edl mode
how can I get oneplus 9 pro into edl mode while it's refusing to turn off? keep in mind that I can't use adb. but was able get fastboot devices command to work and I did not use any third party roms, didn't unlock the bootloader, and do not have...
forum.xda-developers.com
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
Well you have a corrupted boot.img or you would not be trying to edl. Also you probably are holding down multiple buttons to power off to your phone and your either not remembering or forgot that these combination of buttons are booting you into other modes fastboot, recovery or system.
Before you guys jump on me to refer to threads like this one. Just know, I've tried. Seen people say they found success after about 2-3 hours online and I can say I've topped that.
Unfortunately, I am not able to boot into TWRP and am just stuck on the FastBoot screen with my phones status being:
-----------------------------------------------
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
-----------------------------------------------
Can anyone point in the right direction on what steps I should take to remediate this? I've downloaded the proper apk tools (thats how I was able to get the above info using the fastboot binary), to include the MsmDownloadTool for Global, and India; even checking the "Use Lite Firehose" option.
I cannot load into TWRP, nor try flash recovery on an online one as it continues to say the device is in a locked state. Googling that just brings me back to Msm...
I am to the point where I don't care for simply resetting my phone entirely, losing all data, starting brand new, but only using my PC. Anyone familiar on how to do so?
If u can not use any fastboot commands bcux ur BL is locked...only option is going to be msm.. And like u mentioned above, clicking the box for "use lite firehose" and also my OP9pro would never connect for me with my usb-c to usb-c cable, I always have to my old oneplus cable from my OP7pro(old style cord with USB to USB-c, for some reason msm does not connect for me with newer style). Make sure u power off phone, then connect USB cable while holding vol+- buttons and click on enum until u see "connected" in column the click on start.. Once it starts running u can release vol buttons
Shooter7889 said:
If u can not use any fastboot commands bcux ur BL is locked...only option is going to be msm.. And like u mentioned above, clicking the box for "use lite firehose" and also my OP9pro would never connect for me with my usb-c to usb-c cable, I always have to my old oneplus cable from my OP7pro(old style cord with USB to USB-c, for some reason msm does not connect for me with newer style). Make sure u power off phone, then connect USB cable while holding vol+- buttons and click on enum until u see "connected" in column the click on start.. Once it starts running u can release vol buttons
Click to expand...
Click to collapse
Hey man, thanks for the quick response. I will give that a shot but, should this be on the "global" Msm application, or should I be using India's? Probably should use both is gonna be my guess...
I have global OP9pro and I'm able to use the correct msm(global) as long as I click the box for lite firehose.. And all the other things I mentioned. I've read where other ppl had no choice but to use India's msm and then local update back to correct(or preferred OS)..
Just remember if, once u try plugging ur phone into ur pc, if it keeps rebooting immediately even while ur holding both vol buttons, it is prob ur charger cable, so try a different one, older style(not USB-c to USB-c). If it is in edl(black screen while holding vol keys) when u plug it into ur pc it shldnt try to boot up as long as ur still holding them. That is when u will be able to click "enum" until it stays connected then click "start." if all is correct and still not showing connection u need to download and install oneplus drivers and try again..
Shooter7889 said:
Just remember if, once u try plugging ur phone into ur pc, if it keeps rebooting immediately even while ur holding both vol buttons, it is prob ur charger cable, so try a different one, older style(not USB-c to USB-c). If it is in edl(black screen while holding vol keys) when u plug it into ur pc it shldnt try to boot up as long as ur still holding them. That is when u will be able to click "enum" until it stays connected then click "start." if all is correct and still not showing connection u need to download and install oneplus drivers and try again..
Click to expand...
Click to collapse
7 hours man. 7 friggin hours. Everything I read was that I had to be on the FastBoot menu in order for msm to work. That did it.
India's version worked.
1.) Powered Off Phone.
2.) Pressed down on both Volume Buttons (+ & -) (Didn't let go at all)
3.) Plugged in the phone (while still powered off)
- Used a USB to type C connector.
4.) Clicked Enum on the Msm Application (had the app open already)
5.) Checked "Use Lite Firehose".
- Satus of Connection read "Connnected"
6.) Clicked "Start"
7.) Let go of volume button(s)
- Downloading began.
- Downloading finished.
- Rebooted my Phone for me and loaded me to a new start.
Can't thank you enough, and please excuse the redundant instructions. Just wanted to make it as clear as possible for future readers.
Glad u fixed it.! I've been in the same shoes.. Reading over and over through all types of threads here trying to figure out why I cldnt get my phone to connect to msm..so I know how helpless it can feel when NOTHING seems to work the way u need it to. Ur welcome
All you man. If you got one of them BuyMeACoffee accounts, feel free to post it.
Honestly felt like I had tried everything. Even switched to bing searches lol countless articles and forums. Im just glad its functioning again.
I'm good.. pleased that I cld help.. I saw ur post and no comments on it and knew I cld maybe help. Have good night(if that's what time it is for u).
Sure is! Good night as well!
Zinala96 said:
7 hours man. 7 friggin hours. Everything I read was that I had to be on the FastBoot menu in order for msm to work. That did it.
India's version worked.
1.) Powered Off Phone.
2.) Pressed down on both Volume Buttons (+ & -) (Didn't let go at all)
3.) Plugged in the phone (while still powered off)
- Used a USB to type C connector.
4.) Clicked Enum on the Msm Application (had the app open already)
5.) Checked "Use Lite Firehose".
- Satus of Connection read "Connnected"
6.) Clicked "Start"
7.) Let go of volume button(s)
- Downloading began.
- Downloading finished.
- Rebooted my Phone for me and loaded me to a new start.
Can't thank you enough, and please excuse the redundant instructions. Just wanted to make it as clear as possible for future readers.
Click to expand...
Click to collapse
THANK YOU. I had been strugling with bootloop + unauthorized device for several hours and I couldn't boot to EDL because some how me pushing the volume buttons did not get me to EDL. Earlier when I needed to get to the EDL I just "adb reboot edl".
Hello
I need help here I have tried everything to fix my oppo reno 6 5g chinese version and now I am at a dead end can anybody give any suggestion.?
My phone is on black screen and its showing only for 2 second on device manager as some other version which made mtkclient tool to failed handshake and sp flash tool to give error.
like attached screen shots.
In device manager it is showing as V_1632 which is idk what.
I tried all combination but phone is at black screen now.
Device is not going into BROM mode.
Any help will be much appreciated.
hmmm, at least you didn't flash the wrong preloader, so we can save this pretty easily actually.
Just simply follow this guide:
Download VCOM drivers: Mega Link
Install LibUSB and filter your device driver after connecting it through USB while pressing on both vol + and vol - buttons.
Install Python and install it's requirements using the command `pip install pyusb pyserial json5` in CMD.
Extract MTK bypass util anywhere and run the command `python main.py` in the extracted folder through CMD while your device is connected (KEEP HOLDING VOL + AND VOL - DURING THE BYPASSING!!!).
Open SP and flash the scatter file of your stock ROM (PLEASE ONLY FLASH YOUR STOCK ROM) (ONLY USE DOWNLOAD MODE).
Then reboot your device and it should work.
If you face any issue or don't know how to do a step of those just reply to the thread. I'll try to attach some pictures, just be aware I'm only online at about this time.
XDHx86 said:
hmmm, at least you didn't flash the wrong preloader, so we can save this pretty easily actually.
Just simply follow this guide:
Download VCOM drivers: Mega Link
Install LibUSB and filter your device driver after connecting it through USB while pressing on both vol + and vol - buttons.
Install Python and install it's requirements using the command `pip install pyusb pyserial json5` in CMD.
Extract MTK bypass util anywhere and run the command `python main.py` in the extracted folder through CMD while your device is connected (KEEP HOLDING VOL + AND VOL - DURING THE BYPASSING!!!).
Open SP and flash the scatter file of your stock ROM (PLEASE ONLY FLASH YOUR STOCK ROM) (ONLY USE DOWNLOAD MODE).
Then reboot your device and it should work.
If you face any issue or don't know how to do a step of those just reply to the thread. I'll try to attach some pictures, just be aware I'm only online at about this time.
Click to expand...
Click to collapse
I did everything like you described step by step first 3 steps were installations so that went ok but in step 4 I followed your instructions but nothing happend.
I pressed VOL up+VOL down buttons but nothing happend for long time.
Here is screen shot of CMD
I think preloader is damaged or something because not its not going in BROM mode at all only black screen.
If i press VOL up+VOL down+PWR buttons then in device manager phone is shown as I shared screenshot in post but only for like 2 seconds.
like this
Also in SP flash tool detects the phone but when I hit the downlad button it gives error STATUS_ERR instantly not even start the process.
Most likely you didn't use LibUSB right, just open the app connect the device and when you see it in the list of devices highlight it and press install
XDHx86 said:
Most likely you didn't use LibUSB right, just open the app connect the device and when you see it in the list of devices highlight it and press install
Click to expand...
Click to collapse
I did exactly what you said but the problem is phone is like not responding to VOL+andVOL- buttons command, in LibUsb where it says waiting for devicec i pressed both volume buttons and connect and waited for 1 minute atleast but nothing attached screenshot for rfrence. its just empty.
But when i press all HW buttons then LibUsb shows a device then I select it and install and completes it but thats the problem it only shows for 2 second then gone.
like this
what should i do now?
I think you fried the preloader mate, you need to do a test point connection and force the device to connect to the cpu directly.
If you're unsure how to do that please send your device to a professional instead.
XDHx86 said:
I think you fried the preloader mate, you need to do a test point connection and force the device to connect to the cpu directly.
If you're unsure how to do that please send your device to a professional instead.
Click to expand...
Click to collapse
yeah im not sure how to do that. I think too much flashing may have resulted in that.
Thank you for your help.
but in case if they didnt take it then im afraid im gonna have to try that is there any tool or process or help where i can learn more abt this test connection process?
mamomia said:
yeah im not sure how to do that. I think too much flashing may have resulted in that.
Thank you for your help.
but in case if they didnt take it then im afraid im gonna have to try that is there any tool or process or help where i can learn more abt this test connection process?
Click to expand...
Click to collapse
It's device specific so I'll need to look into it and reply to you, but generally speaking you're going to connect a USB to the device through specific CPU pins on the motherboard.
XDHx86 said:
It's device specific so I'll need to look into it and reply to you, but generally speaking you're going to connect a USB to the device through specific CPU pins on the motherboard.
Click to expand...
Click to collapse
Oh it means I need to open up the phone.
That will be the problem because I dont have the tools to do that.
I guess first I have to try and find some professional then.