Related
Hi there,
I've done this numerous times and various machines.
Unfortunately my devices on/off button is broken and when the battery is low and the phone shuts down I need a PC to reboot the device by using "fastboot reboot."
Works on 4 different machines, except for my homebase PC. *Sigh* :crying:
In a command window fastboot responds with "waiting for device"..... Opening the Flashtool, it recognizes the device and tells me that it is in the fastboot mode. To my surprise there is no button in Flashtool that says reboot or a chance to issue commands to the phone...... so frustrating.
Any idea of how I can get this to work? Here is what I will not do: Re-Install Windows.
Here is what I tried: Re-Installing the driver numerous times, Flashtool recognizes the device.
How can that be? Makes no sense to me at all....
Any input is appreciated.
Thanks
James
Andro1dism said:
Hi there,
I've done this numerous times and various machines.
Unfortunately my devices on/off button is broken and when the battery is low and the phone shuts down I need a PC to reboot the device by using "fastboot reboot."
Works on 4 different machines, except for my homebase PC. *Sigh* :crying:
In a command window fastboot responds with "waiting for device"..... Opening the Flashtool, it recognizes the device and tells me that it is in the fastboot mode. To my surprise there is no button in Flashtool that says reboot or a chance to issue commands to the phone...... so frustrating.
Any idea of how I can get this to work? Here is what I will not do: Re-Install Windows.
Here is what I tried: Re-Installing the driver numerous times, Flashtool recognizes the device.
How can that be? Makes no sense to me at all....
Any input is appreciated.
Thanks
James
Click to expand...
Click to collapse
Which driver install method do you use? I think Flash tool driver exe is best, and make sure to install fastboot, flash mode, and device specific, (Z1c is 'Rhine'). It's strange that Flash tool would recognize device in fastboot mode, but fastboot wouldn't...
Anyway, an alternative would be to mod system ui to include power button on navbar. Not hard to do. Let me know if you want to try.
Here's an example - https://forum.xda-developers.com/showpost.php?p=71219730&postcount=2212
I changed my on-off button. It's easier
levone1 said:
Which driver install method do you use? I think Flash tool driver exe is best, and make sure to install fastboot, flash mode, and device specific, (Z1c is 'Rhine'). It's strange that Flash tool would recognize device in fastboot mode, but fastboot wouldn't...
Anyway, an alternative would be to mod system ui to include power button on navbar. Not hard to do. Let me know if you want to try.
Here's an example - https://forum.xda-developers.com/showpost.php?p=71219730&postcount=2212
Click to expand...
Click to collapse
Hi Levone,
yeah, I did exacly that. Use Flashtool and then install fastboot, flash mode and the Z1C Drivers..... funny it workes smooth under Windows 7 but not at all under Windows 10 (different partition). I had the hope it goes smooth in Win10 which would suffice for me..... although I'd like to have it running in my home OS Win7x64.
Ur UI looks nice, although I dunno what help it would provide me if the phone is down
alf-endy said:
I changed my on-off button. It's easier
Click to expand...
Click to collapse
Yeah sure that would be no problem from the technical side, but I prefer the phone to be water proof :yay: #SonyForTheWin ^^
Andro1dism said:
Ur UI looks nice, although I dunno what help it would provide me if the phone is down
Click to expand...
Click to collapse
Right - I just thought that if you at least gave yourself a reboot option while phone was up, you could avoid some of the power-downs. I guess you could do thebsame with an app...
Also, might be possible to re-map and make a different button power.
levone1 said:
Right - I just thought that if you at least gave yourself a reboot option while phone was up, you could avoid some of the power-downs. I guess you could do thebsame with an app...
Also, might be possible to re-map and make a different button power.
Click to expand...
Click to collapse
Andro1dism said:
Ur UI looks nice, although I dunno what help it would provide me if the phone is down
#SonyForTheWin ^^
Click to expand...
Click to collapse
O looked into it for my own curiosity, and I wastable to remap my volume key to work for power, by modding /system/usr/key layout, but doesn't work from powered off. Doesn't seem possible...
levone1 said:
O looked into it for my own curiosity, and I wastable to remap my volume key to work for power, by modding /system/usr/key layout, but doesn't work from powered off. Doesn't seem possible...
Click to expand...
Click to collapse
Is there a way to re-calibrate the battery so that it at least shows 20% of power and not 50% ?
Besides: How can I "avoid some of the power-downs" with a reboot?!
But. . . . . . . There are buttons in Flashtool to do what you want
Andro1dism said:
Hi there,
I've done this numerous times and various machines.
Unfortunately my devices on/off button is broken and when the battery is low and the phone shuts down I need a PC to reboot the device by using "fastboot reboot."
Works on 4 different machines, except for my homebase PC. *Sigh* :crying:
In a command window fastboot responds with "waiting for device"..... Opening the Flashtool, it recognizes the device and tells me that it is in the fastboot mode. To my surprise there is no button in Flashtool that says reboot or a chance to issue commands to the phone...... so frustrating.
What about the Fastboot Toolbox in Flashtool ?
Just in case you didn't notice 9 buttons you can push with a mouse to make your xperia do just about anything fastboot can do without ever having to touch a keyboard or a button.
Picture with Sony D5503 Lineage CM12 min res 2mp
Click to expand...
Click to collapse
{
"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 was playing normally the phone discharged turned off, and when I connect it only shows the android one screen over and over, the led that shows that it's charging doesn't turns on, I have nothing weird installed, didn't even knew about fastboot or roms, or anything like that until 15 minutes ago, so the fastboot options are not and cannot be activated, does it have a solution? do I just let it be connected for a few hours and try again, or what, i'm a noob on this matters so I don't know what to do. Thanks
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
loop4444 said:
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
Click to expand...
Click to collapse
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
M4N4GM said:
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
Click to expand...
Click to collapse
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
pawelik said:
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
Click to expand...
Click to collapse
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
M4N4GM said:
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
Click to expand...
Click to collapse
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
SubwayChamp said:
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
Click to expand...
Click to collapse
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
M4N4GM said:
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
Click to expand...
Click to collapse
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
SubwayChamp said:
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
Click to expand...
Click to collapse
That option didn't work, volume up + power just tried to start the phone
M4N4GM said:
That option didn't work, volume up + power just tried to start the phone
Click to expand...
Click to collapse
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Thanks i'll try if it works
SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Little Hill said:
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Click to expand...
Click to collapse
Wrongly quoted.
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.