{
"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
Related
I realized there aren't any guides [in English] around here to help rooted folks that soft bricked their LG PRO to restore it back to factory settings. This should be useful if you got your phone stuck on the AT&T or the LG logo. Especially now that we don't have an unlocked bootloader or a recovery to reocver our soft brick.
Anyway, to start, a little disclaimer: I hold no responsibility if this method renders your phone completely useless, or burns and makes some nice fireworks. I'm simply writing this to document the process that worked for me. Use at your own discretion.
Dislcimaer 2: this method will wipe out your internal sdcard, apps data, everything! It'll restore the phone back to the way you got it from AT&T. Might even lose your cell unlock status (not verified). so keep these unlock codes handy just in case.
Note to linux users like myself: get your a** on windows or run it from a VM. VirtualBox with Win7 works fine.
Steps:
Download
1. LGFlashTools v1.5. Anything less won't work. Mirror: HERE
2. DLL file for LGE980
3. Drivers
4. The stock image file
Thanks to IOMonster for hosting these biga** files.
Install
1. Install the LG drivers downloaded above.
2. Install LGFlashTools v1.5 (but don't run it)
3. Extract the DLL and the TOT files from above and put them in a nice tidy directory
Drivers initialization
1. Put the phone into download mode. (Turn off device, keep pressing volume down while plugging in the micro usb cable. If this doesn't work, try holding both volume keys instead)
2. Let the phone initialize and install the drivers. Once done, in Device manager, you should see the LG phone listed under COM ports (something along these lines).
3. Find that LG entry in Device Manager, click on Properties, Advanced and then change the COM port to COM41 and close/save.
4. Unplug your phone! Important step.
LGFlashTools
To get this tool to work, you'll need to do a few tricks.
1. Set the computer's date to some time in July 2012 or before.
2. Disconnect the internet
3. Find a serial number or register key from somewhere on the web (a google search for lgflashtools serial will yield some results). Can't help you here and please don't share any keys in this thread or get us in trouble.
4. Execute the LGFlashTools. It should ask you for a key, put it in. Now you should see a dialog where you can load the DLL file and the TOT files that you extracted earlier. Put them both in here. Click ok
Flashing
5. There is a yellow arrow on the top left. Click on it to initialize the process. Once done, it should say "ready/finished" or whatever.
6. Put the phone in download mode again, and plug it into the USB port. LG FLash Tools should start flashing it automatically. When it's done, it'll automatically reboot into your stock AT&T rom and all of your data and internal sdcard files are gone.
Profit
Thanks again Mac !
MrNa5ty said:
Thanks again Mac !
Click to expand...
Click to collapse
sure thing I'm probably going to refer to it myself someday.
madmack said:
sure thing I'm probably going to refer to it myself someday.
Click to expand...
Click to collapse
Thanks .... great info!!!!!
Nice. Hopefully they sticky this.
Welp, just bricked the phone again but was able to flash the tot... very simple and quick lol ur the man mac
this worked perfectly fine for me. i 1st tried it on w8 but after plugging in the e980 and letting the drivers and such install, it did not show up under com in the device manager. in fact, there was no com section. it did show up under devices and printers and i tried and could not find a com setting there. i went ahead and tried to flash but since i could not change to the proper port, the flash tool never found my e980.
so instead i just did it all on a w7 box, the device was listed under com, and i went along with the flashing.
thank you.
Think this will fix the bricks that are happening when they try to mess around with the bootloader?
Sent from my LG-E980 using Tapatalk 4 Beta
jprosek said:
Think this will fix the bricks that are happening when they try to mess around with the bootloader?
Sent from my LG-E980 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nope. Mess with the bootloader and you'll risk losing download mode.
nvm
This needs to be stickied!!!
Sent from my LG-E980 using xda app-developers app
My friend just bricked his and the wi9ed the system. I can get ir into download mode for him but thats it. I tried recovery mode but trying to do that or boot regularly it just shows lg the an android with the spinning symbol on it the lg again then lg 2 more times and just stays there. Can this be fixed with only download mode? Again I plugged it in and im not sure its being seen by the computer.
Make sure you have the drivers installed and use pc suite to get back the firmware
rob219 said:
My friend just bricked his and the wi9ed the system. I can get ir into download mode for him but thats it. I tried recovery mode but trying to do that or boot regularly it just shows lg the an android with the spinning symbol on it the lg again then lg 2 more times and just stays there. Can this be fixed with only download mode? Again I plugged it in and im not sure its being seen by the computer.
Click to expand...
Click to collapse
it doesn't hurt to try. I'll bet it will because I was left with something similar and this method got me back on stock.
smaybe said:
Make sure you have the drivers installed and use pc suite to get back the firmware
Click to expand...
Click to collapse
Pc suite? Do you mean lg flash tools? I downloaded it but it wants me to log in to use it. I havent found a log in for it yet.
Download lg pc suite it have lg flash tool in it
Then you search a little in menus for firmware urgence recovery something like that and if it don't work try update in the same menu
And if all of that didn't work I'll find you a link to flash a kdz
Deleted
I seem to have an issue with my E980, i cant get data my apn directory is empty and cant seem to add an apn it will just not save! anyone else have this issue or know what i can do? thanks!
Reboots to recovery only
Ok, I flashed the recovery in this post using the dd method http://forum.xda-developers.com/showpost.php?p=43460298&postcount=208
The value pack was trying to download on my phone and instead of cancel, I pressed install. Now the phone only boots into that recovery. I have everything from the op downloaded, but instead of download mode it only boots into the recovery, any ideas?
When it boots up, It says the following for a couple of seconds:
Code:
Secure booting error
Cause: Device Unlock, so boot success!!
Edit: Got it into download mode by holding down both volume keys and plugging into usb. Thanks!!
apascual89 said:
Ok, I flashed the recovery in this post using the dd method http://forum.xda-developers.com/showpost.php?p=43460298&postcount=208
The value pack was trying to download on my phone and instead of cancel, I pressed install. Now the phone only boots into that recovery. I have everything from the op downloaded, but instead of download mode it only boots into the recovery, any ideas?
When it boots up, It says the following for a couple of seconds:
Code:
Secure booting error
Cause: Device Unlock, so boot success!!
Edit: Got it into download mode by holding down both volume keys and plugging into usb. Thanks!!
Click to expand...
Click to collapse
I'm glad you got it resolved! I just edited the OP with this information.
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
audit13 said:
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Click to expand...
Click to collapse
timbernot said:
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
Click to expand...
Click to collapse
Thank you for your answers! Last hours been trying to flash the stock ROM back. However, when getting into bootloader, adb devices and fastboot devices don't show the device. Or it even freezes and gets into reboot loops again. So this is why I'm stuck, nothing seems to be working from all the guides and things I'm reading.
So precisely:
- Power off bootlooping device by holding power button
- Power on by holding PWR + VOL UP
- When vibrating: release PWR keep holding VOL UP
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
So what can I try to make connection?
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
timbernot said:
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
Click to expand...
Click to collapse
The bootloader in shows the following:
IFWI version: 0094.0173
SERIAL_NUMBER = F8AZFG0152** (couldn't read the last 2 digits as the device rebooted again). Also sometimes the SN shows 012345689ABCDEF.
I've much trouble keeping the device in bootloader. Last tryings it keeps shutting down after couple of seconds in the menu.
EDIT:
So far the device seems to stay in bootloader mode now. I can cycle through the options normal boot, recovery etc. Below the screen it shows Continue the fastboot process in blue text. I've inserted the USB cable but have been unable to get "fastboot devices" to show any device. ASUS Flashtool also doesn't do anything.
I'm going to try to find a micro SD adapter so I can try flashing stock rom in TWRP from the phone itself (would that be something that could work or is this phone fubar?)
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
timbernot said:
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
Click to expand...
Click to collapse
Thank you for your support! Will try again.
I have MM not LP.
I don't understand your reply correctly I think so here is what I think you say?:
I should obtain LP rom for ZE551ML
Next, enter bootloader via buttons PWR & VOL UP after 10 seconds being off !
When in the bootloader, - power and vol + (short press or long?) , when in bootloader ->
I connect USB to computer, flash the file using AFT if I make connection. -- flash raw (raw = LP ROM from ASUS) with AFT (asus flash tool )
Thanks again for your help
j4y_ha said:
Thank you for your support! Will try again.
I have MM not LP.
Thanks again for your help
Click to expand...
Click to collapse
IFWI version: 0094.0173 is LP, NOT M
follow my first reply:good:
---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------
No1
Hi there , in TWRP select reboot then power off .
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
no2
Enter bootloader via buttons after 10 seconds being off !
no3
When in bootloader you are on LP -- flash raw with AFT (asus flash tool )
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
j4y_ha said:
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
Click to expand...
Click to collapse
I'm taking wild guess here that you got wrong TWRP recovery installed somehow or something from M causing all these problems , when you get into bootloader again..Scroll to and select reboot bootloader and fastboot flash stock recovery for LP version you was on .
Then , I guess your problems will be over , where you will be able to flash raw in bootloader or in stock recovery , adb side load the firmware
Thanks for your quick anwer. Will try to get through it haha :good:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
j4y_ha said:
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
Click to expand...
Click to collapse
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Thank you for your thourough answer Ryankabir! Much appreciated. My answers are below. I will try your suggestions soon.
ryankabir said:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Click to expand...
Click to collapse
Yes I do know what I can do with it, but it just so complicating as there are different factors like the loops, not being able to get connections with USB. I mean, it is not totally bricked since sometimes I can get into TWRP or bootloader.
ryankabir said:
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
Click to expand...
Click to collapse
Well, since the phone worked fine before the battery issue, there is some sort of link between the issues I would think. Maybe I've broken some hardware during the battery removal or did the booting into charging mode and on/off continously corrupt some memory leaving me with weird crashes & loops.
ryankabir said:
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
Click to expand...
Click to collapse
Although I'm not sure if I have the correct TWRP, it did flash CM13 correctly back in FEB 2016 and haven't found a need to update it ever since as it worked fine during the occasional update...
ryankabir said:
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Click to expand...
Click to collapse
No, D2W is not there. The phone is totally unresponsive to the power button as well as D2W. When in TWRP the touchscreen functions fine until it freezes at some random moment.
ryankabir said:
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
Click to expand...
Click to collapse
Yes I know what drivers are :good: - I've tried IntelSoc, Intel ASUS etc... all drivers that are somewhere mentioned I have installed. Before the charging problem I was able to connect the phone and access files fine as well.
ryankabir said:
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Click to expand...
Click to collapse
Thanks, will try more!
ryankabir said:
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Click to expand...
Click to collapse
TWRP is indeed fine and stable! However, it freezes and reboots my phone so in my particular situation it is currently not stable. Therefore the need to completely wipe the phone and start from fresh.
ryankabir said:
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Click to expand...
Click to collapse
Appreciate your POV. I know how it feels like if people ask for help for something they could have read easily somewhere. I'm thankfull for all the guides that people have written on here! I'm asking for help because in my situation the guides are not working and would like to have a full clean wipe of my phone and fix all possible software issues before trowing away the phone because of hardware fault.
ryankabir said:
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
Click to expand...
Click to collapse
Thanks for the suggestion and will try this!
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
I've tried your guide but I still have been unable to get a connection with ASUS Flashtool. The phone does keep itself relatively stable in bootloader (don't know what fixed it) - I am able to cycle through normalboot, recovery options etc without it crashing. The bootloader shows "Continue the fastboot process". I have tried different drivers, while rebooting between install/uninstall of drivers.
Thanks again all for the help
@j4y_ha
Goodluck
timbernot said:
@j4y_ha
Goodluck
Click to expand...
Click to collapse
Right m8 , we gonna fix your phone .
Do not stray from this guide.
Stick to it and you will be more the wiser when you have finished .
1 boot to boot loader ...scroll to 'power off ' and select it.
2 Connect your phone to wall charger ...let it charge till full.
When that's done , we ready for next step
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Mmbl came about around July 16, he run cm 13 Feb 16.
.173 or .177 is unlocked or locked LP Boot loader.
xFSTK is to gain temp Boot loader.
He gets recognised in fastboot.
He can flash stock recovery .
He can sideload .
.
.
But
Can he ?
That's not sn ide btw
Well I'm not gonna dig too deep into the twrp touch issues (there could be conflicting drivers or even something weird i noticed in twrp302 anything below 20% batt (or if batstats corrupt) then the touch goes craycray.. so lets ignore that..
this thread is getting too heavy i won't have time - so - you can always backup ur data partition so no worries there.. nothing to lose..
one problem at a time.. as I said in first post my phone was bricked much worse i had mismatched fastdroidboot and bootimg and after pressing power on maybe 4-5 times.. it would only turn on once.. sometimes on and immediately off... sometimes on stuck on logo.. sometimes on and no logo but screen is black (corrupt splash)..
so lets just try to go baaaaaack to the futureeeeeee ... Ok I found the script I made (after 8 hours of trying EVERY combination from different guides I just took individual components and made my own.. ) -
I'm writing this in a hurry so please use my first reply to get the XFTS Ubrick Guide for the Files + get the LOLLIPOP One Click BL Unlock + Lollipop Raw image... Their Guide wants you to use Asus Flash but that program failed me every time... so I have got a differnt way to do it..
I'm copying this directly from my own script (so you can change if any paths/names different)... but do not change the order or sequence
Using OneClick (keep the unlock1234 files saved separately for later use)...
If you have these unlocked I just say do it again anyway - no harm...
Unlock Bootloader for LP Stock (even if you have MM you must downgrade by this same method)
Code:
#flash old droidboot for LP stock Bootloader
fastboot flash fastboot droidboot_2_20_40_197.img
fastboot reboot-bootloader
# must run reboot bootloader once with this droidboot before continuing - dn't skip this
# unlock bootloader (use files provided inside oneclick tool but instead of using their script, manually do it - more reliable)
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
#if you get failed/error at oem stop - reboot to Bootloader (VOLUP+Power long press -
Release power at Asus Logo or long vibration) and re-do the last step
#if all done so far
fastboot reboot-bootloader
#white Asus logo means unlocked loader
fastboot flash recovery twrp3.img
reboot-bootloader
#toggle Up to choose Recovery - quick tap VOLUP+Power
#twrp will start
install Custom_MM_Rom.zip
#likely it will fail giving IFW 7 error - (intentionally did NOT put MM BL here), so
install Asus_MM_WW_420_184.zip (stock on stock only)
#let it be fully done, verify working MM stock OS
#check if it works - *sign* test your touch screen quickly and in dev tools Keep Debugging ENabled
#then power off - or if you have more options directly choose reboot
#during reboot vibration hit VOLUP+P to Fastboot
####RE-DO Entire first half again
fastboot flash fastboot droidboot_2_20_40_184.img
fastboot reboot-bootloader
# must run once with this droidboot before continuing
# unlock bootloader
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
fastboot reboot-bootloader
#now only flash certain MM files (the rest should already be there from stock upgrade) - if you have different MM Img (if they release new one in future - all readers just need to ensure the TOKEN DNX IfW matching)
${FASTBOOTBINARY} flash splashscreen tools/splashscreen_551.img
fastboot flash token tools/bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
#should now see black splashscreen + little red error msg for 2 seconds
#entering twrp again by toggling Recovery-> VOLUP+P
install superuser.zip
wipe cache + data
install yourcustomROM.zip
ryankabir said:
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Click to expand...
Click to collapse
I have bricked lg e988 indonesia firmware rooted,updated to kitkat 4.4.2,cwm 6.4.0.4
Due to some issue I factory reset from settg menu and the phone rebooted to cwm recvry mode
I tried to rebootd to system but fail
I tried to flash stock rom via adb sideload but fail too so does with lg flash tool
So I thght smtg wth cwm then I tried to flash twrp loki 2.6 and then stuck to lg logo only until now
Pls help
You're still soft bricked, just force your device into download mode and use LG Flash Tool to return back to stock and start again.
ShadySquirrel said:
You're still soft bricked, just force your device into download mode and use LG Flash Tool to return back to stock and start again.
Click to expand...
Click to collapse
Thank you for the respond. Mind if you share me on how to force my device into download mode?
I have tried the power + volume keys combination but nothing happened, back and stop at lg logo
Before i flash the twrp, i tried the LG Flash Tool, but i wont recognize the phone, something like usb connection issue
hotmatua.parulian said:
Thank you for the respond. Mind if you share me on how to force my device into download mode?
I have tried the power + volume keys combination but nothing happened, back and stop at lg logo
Before i flash the twrp, i tried the LG Flash Tool, but i wont recognize the phone, something like usb connection issue
Click to expand...
Click to collapse
If I remember correctly (please check threads here, it's been a long time since I've used this device, so memories are fading), download mode is activated when you press Volume Up (or both of volume buttons) and insert USB cable. I know that E98x has some strange button sequences, like rebooting to recovery is a two step operation (Volume Up + Power until navbar blinks, then power button twice, that's the only way mine wanted to boot into recovery), so please check around.
As far as USB connection issues, don't use USB3+ ports and if you're on Windows 8.1+ and later, run with Administrator privileges. I never experienced that one (used LGFlashTools from inside VirtualBox running Win XP for all my needs, I'm not a Windows user), so can't really help much but forums are full with explanations how.
ShadySquirrel said:
If I remember correctly (please check threads here, it's been a long time since I've used this device, so memories are fading), download mode is activated when you press Volume Up (or both of volume buttons) and insert USB cable. I know that E98x has some strange button sequences, like rebooting to recovery is a two step operation (Volume Up + Power until navbar blinks, then power button twice, that's the only way mine wanted to boot into recovery), so please check around.
As far as USB connection issues, don't use USB3+ ports and if you're on Windows 8.1+ and later, run with Administrator privileges. I never experienced that one (used LGFlashTools from inside VirtualBox running Win XP for all my needs, I'm not a Windows user), so can't really help much but forums are full with explanations how.
Click to expand...
Click to collapse
Thank you very much...now the phone is back to initial state. This what i've done:
1. Download LG Flash tool from http://lgflashtool.com/
2. Download LG USB Drivers from http://lgflashtool.com/
3. Install LG flash tool and LG USB Drivers
4. Plug usb cable to phone
5. Hold volume buttons and then plug the usb cable to PC (i use win 10)
6. Voila, the Download Mode icon is showed up
7. Run LG Flash Tool (Administrator privilege) & follow the instruction (i use e988 v20c stock firmware)
8. Phone back to normal (only if you use the correct stock firmware)
A very big thanks to ShadySquirrel
Hopefully this thread can also be used as reference for anyone who has the same issue as i had
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Fredelbert said:
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Click to expand...
Click to collapse
You tried xdadevelopers search box ?
RuedasLocas said:
You tried xdadevelopers search box ?
Click to expand...
Click to collapse
Not yet actually . Can't find it under TOOLS . Is this available yet ?
RuedasLocas said:
You tried xdadevelopers search box ?
Click to expand...
Click to collapse
Sorry, I misunderstood your answer ...
Searching for related posts using the keywords 'boot loop' or 'recovery gone' really doesn't help me ...
As I said, I can't use
- Recovery
- adb
- FlashTool
- odin
anymore in any way . All posts I've found suggest things related to them ...
Most bootloop topics recommend using one of them in different ways ...
Is there a tool not mentioned yet that will help me with my problem ?
As I said, thre search function does'nt bring me to a clue
Fredelbert said:
Sorry, I misunderstood your answer ...
Searching for related posts using the keywords 'boot loop' or 'recovery gone' really doesn't help me ...
As I said, I can't use
- Recovery
- adb
- FlashTool
- odin
anymore in any way . All posts I've found suggest things related to them ...
Most bootloop topics recommend using one of them in different ways ...
Is there a tool not mentioned yet that will help me with my problem ?
As I said, thre search function does'nt bring me to a clue
Click to expand...
Click to collapse
Connect your device to the computer and see how is detected by "Windows Device Manager".
If not as it should, try to uninstall all related hardware drivers, like modem, adb device, whatever...
Reinstall "LGMobileDriver_WHQL_Ver_4.2.0"
Reinstall "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All"
Reinstall "Minimal ADB and Fastboot"
Reboot your computer and reconnect yout device. It should work.
RuedasLocas said:
Connect your device to the computer and see how is detected by "Windows Device Manager".
If not as it should, try to uninstall all related hardware drivers, like modem, adb device, whatever...
Reinstall "LGMobileDriver_WHQL_Ver_4.2.0"
Reinstall "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All"
Reinstall "Minimal ADB and Fastboot"
Reboot your computer and reconnect yout device. It should work.
Click to expand...
Click to collapse
When I go to the download mode (the only one starting) it is shown as
LGE AndroidNet USB Serial Port (COM11)
My other LG G4 is working fine with all of the tools and the drivers on my PC (Win 10 64)
and also on my notebook (WIN 10 64) and so did the other one before my attempt of changing the recovery ...
Fredelbert said:
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Click to expand...
Click to collapse
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
ThePiGuy said:
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
Click to expand...
Click to collapse
OK, it will take some time downloading and trying it. I'll be back when having results
THANX
ThePiGuy said:
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
Click to expand...
Click to collapse
I've started it and also I've found SALT.
Starting SALT and connecting in Download Mode gives me following informations ( haven't found informations about bootloader stack) :
{
"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"
}
Fredelbert said:
I've started it and also I've found SALT.
Starting SALT and connecting in Download Mode gives me following informations ( haven't found informations about bootloader stack) :
Click to expand...
Click to collapse
Good enough for me
Look at the system one - It says v29a.
So what I want you to try now. Power off your phone. Then, hold power and volume up and hopefully it will boot into the bootloader (at which point you can reflash twrp from twrp.me - cwm is completely outdated)
Fredelbert said:
When I go to the download mode (the only one starting) it is shown as
LGE AndroidNet USB Serial Port (COM11)
My other LG G4 is working fine with all of the tools and the drivers on my PC (Win 10 64)
and also on my notebook (WIN 10 64) and so did the other one before my attempt of changing the recovery ...
Click to expand...
Click to collapse
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
If the phone had v29a installed, you need v20p.kdz and respective "8994.dll", you can extract it from the .kdz. Than you can use LGUP.
ThePiGuy said:
Good enough for me
Look at the system one - It says v29a.
So what I want you to try now. Power off your phone. Then, hold power and volume up and hopefully it will boot into the bootloader (at which point you can reflash twrp from twrp.me - cwm is completely outdated)
Click to expand...
Click to collapse
Unfortunately it doesn't ... Same as normal start :
I did
REMOVE / INSERT BATTERY
POWER / VOL UP same time
then
short flash of BOOTLOADER STATE : BOOTLOADER UNLOCKED including LG Logo, then immediate reboot
Fredelbert said:
Unfortunately it doesn't ... Same as normal start :
I did
REMOVE / INSERT BATTERY
POWER / VOL UP same time
then
short flash of BOOTLOADER STATE : BOOTLOADER UNLOCKED including LG Logo, then immediate reboot
Click to expand...
Click to collapse
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
ThePiGuy said:
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
Click to expand...
Click to collapse
Look at the firmware(laf): v20g
That's his bootloader stack
He flashed freedom ROM which has v29a as base that's why system shows v29a.
Sent from my LG-H815 using XDA Labs
ThePiGuy said:
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
Click to expand...
Click to collapse
That has no effect, same behaviour as before
RuedasLocas said:
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
If the phone had v29a installed, you need v20p.kdz and respective "8994.dll", you can extract it from the .kdz. Than you can use LGUP.
Click to expand...
Click to collapse
Sorry, as I mentioned, LGUP can't be used because the tool reject the phone selection because it's "unknown"
Fredelbert said:
Sorry, as I mentioned, LGUP can't be used because the tool reject the phone selection because it's "unknown"
Click to expand...
Click to collapse
Do you have the right "8994.dll" ???
Because to get out from v29a you need the v20p.kdz and the ""8994.dll"" from it. Thats probably why your phone is "unknown"
RuedasLocas said:
Do you have the right "8994.dll" ???
Because to get out from v29a you need the v20p.kdz and the ""8994.dll"" from it. Thats probably why your phone is "unknown"
Click to expand...
Click to collapse
That might be... But how can I make neccessary modifications, when I get no access to the phone at all...
Fredelbert said:
That might be... But how can I make neccessary modifications, when I get no access to the phone at all...
Click to expand...
Click to collapse
You just need the right "8994.dll" on the folder "C:\Program Files (x86)\LG Electronics\LGUP\model\8994", replace the one that you have there with the one extracted from the v20p.kdz.
After that run LGUP.
RuedasLocas said:
You just need the right "8994.dll" on the folder "C:\Program Files (x86)\LG Electronics\LGUP\model\8994", replace the one that you have there with the one extracted from the v20p.kdz.
After that run LGUP.
Click to expand...
Click to collapse
OK, then I will search for the mentioned Kdz file and download it. I will be able to continue tomorrow. Thanks to everybody so far. I will post the result as fast as I can
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.