Hard Bricked my device, can someone help? - G Pad 8.3 Q&A, Help & Troubleshooting

I have been trying to get this thing upgraded to 5.0 for a day and half now, and i just flashed it for like the 10th time with lg flash tool to try to take it to stock. The rom i flashed that bricked the device I found in this thead: http://forum.xda-developers.com/show....php?t=2698267
All of a sudden it won't turn on, won't respond to adb or enter recovery with the volume down + power combo.
All i can see in device manager is qhsusb with an exclamation point. I struggled to update this and once i finally did, the device still isn't recognized by the computer in any lg programs like mobile support tool or flash tool or by adb and wont turn on what can/should i do at this point??

jazir said:
All of a sudden it won't turn on, won't respond to adb or enter recovery with the volume down + power combo.
Click to expand...
Click to collapse
So it won't enter download mode either? You didn't mention that one... If it does enter download mode you have several options, however based upon what you posted I'm guessing download mode is also not available?

muiriddin said:
So it won't enter download mode either? You didn't mention that one... If it does enter download mode you have several options, however based upon what you posted I'm guessing download mode is also not available?
Click to expand...
Click to collapse
I managed to find out that the phone is in something called bulk mode and even found a tool that gets lg phones out of bulk mode. The program located in this thread here: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830.
It has my chipset in it(The APQ8064) and can connect with the phone. It passes the first two tests (AP, and EMMC) and fails the SDRAM test. If i can figure how to fix the last test and make it succeed, the tablet won't be bricked anymore. Any ideas?

jazir said:
I managed to find out that the phone is in something called bulk mode and even found a tool that gets lg phones out of bulk mode. The program located in this thread here: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830.
It has my chipset in it(The APQ8064) and can connect with the phone. It passes the first two tests (AP, and EMMC) and fails the SDRAM test. If i can figure how to fix the last test and make it succeed, the tablet won't be bricked anymore. Any ideas?
Click to expand...
Click to collapse
Had a quick look at that bulk mode thing. It seems to refer to a TOT file.
That TOT file seems to be in this thread http://forum.xda-developers.com/showthread.php?t=2692505 and is still downloadable it seems. (https://drive.google.com/file/d/0B34qnFE3O_HbX2t6elg5UXZFNEk/edit)
Looking further at that unbrick thread it seems that SDRAM is checked in step 4 . Where do you get stuck?

lukesan said:
Had a quick look at that bulk mode thing. It seems to refer to a TOT file.
That TOT file seems to be in this thread http://forum.xda-developers.com/showthread.php?t=2692505 and is still downloadable it seems. (https://drive.google.com/file/d/0B34qnFE3O_HbX2t6elg5UXZFNEk/edit)
Looking further at that unbrick thread it seems that SDRAM is checked in step 4 . Where do you get stuck?
Click to expand...
Click to collapse
Well my phone doesn't work with that program anymore. After running into the sdram error for so long i ended up scanning that thread and running across QPST, which is the qualcomm manufacturer tool for flashing phones/tablets with Qualcomm. , which placed my phone into download mode for QPST.
I believe i can fix it using the process listed here: http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
However i need the correct hex and mbn files, which are generated from the 4.4.2 tot file for my gpad. The annoying part is this has to be done in linux. The guide i found of how to make the correct files is here: http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289 ,
Except i don't know how to work linux and that is just a little too complicated for me. If you have linux and can attempt to help me build the correct files that would be great. Unless i can somehow run a loopback mount command on windows like it mentions, i'm stuck

Related

[GUIDE] [E980] Fix soft bricks. Flash back to stock using LGFLashTools

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.

[REQUEST] Test points for EDL mode

Some of us are bound to "brick" our Max's at some point, we need a genius that knows the right test points to help us out!
Thanks!
Totally agree. I now manage to boot into EDL and Fastboot, but have a locked bootloader and don't know how to reset the phone
(the only thing I did was an update, then bootloop...)
Help Please..Same with me.
My phone was hardbrick i think.
No download mode, no fastboot mode and my device manager just only recognize as HS-USB Diagnostic 900E
How i can get back to life my phone
Thanks
This should work on Mi Max too:
http://en.miui.com/forum.php?mod=viewthread&tid=310325&extra=page%3D1&mobile=2
Check here: http://en.miui.com/thread-328371-1-1.html
panospc said:
Check here: http://en.miui.com/thread-328371-1-1.html
Click to expand...
Click to collapse
I also posted it here
I am everywhere
How do I put the phone into fastboot mode if it is hard bricked? It won't turn on, I get no responce from phone. When I use method connecting test point to metal cover on mother board of phone usb connects to PC and MiFlash recognizes phone. Try to flash though and I get an error message. No matter what ROM I use, zipped, unzipped or tgz file. Can my phone be unbricked? What am I doing wrong? I have a Mi Max 64GB and am using HELIUM Roms. Please help. I am using this method
http://en.miui.com/thread-328371-1-1.html
Everything is good up to when I click on flash. Then I always get the error message.
Error message is:
The filename, directory name, or volume label is incorrect.(0x8007007b: Open programmer "MPRG*.hex").
I have no clue. Not my first time flashing ROMs or unbricking a phone. It is my first time on a Xiaomi. Only done blackberry and samsung before.

Bricked Swift

Hello Everyone!
I recently tried to root my wileyfox swift but failed miserably. I did the following when fastbooting the recovery image -> fastboot flash system ****.img.
However, i realized my mistake too late, and now my phone is all messed up!
The phone doesnt show anything when i try to start it and i cant access fastboot again, to undo my mistake. My device manager recognizes my phone when its plugged in to my computer but i cant access any files.
Am i screwed or is there any solution to this?
Thanks in advance!!
Try to access the bootloader with the hardware button combo first (volume down + power / volume up + power). If you get into recovery, you will be able to get to the bootloader with adb or a menu entry. Depends on what recovery you have installed for the latter.
In case you have no access to the bootloader (proper soft brick), go for the QFIL method. Avoid using it unless there is no other option.
Here is the thread:
http://forum.xda-developers.com/wileyfox-swift/general/how-to-set-device-tampered-to-false-t3276317
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
Does the phone give any indication of being connected? Notification light, starting the display, etc?
If yes, make sure the phone is in the correct mode and check the drivers - some of the other forum members mentioned this and the gymnastics around the battery. This would be on my to-do list. The device might come up on the device manager as different one, so monitor the manager for any changes once you connect the device.
If you happen to have Windows 7 device laying at you house, you can try with it (if only not to worry about compatibility and sporadic Win10 behaviour).
It will be a good idea to check the turkish website for General Mobile 4G (one of the Android one derivatives of the hardware) where some people have faced similar problems using the same tool.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
If you need my help via TeamViewer then WhatsApp me at +27799261595 or pm me
Finally got my phone back on the device manager! However, I still get sahara error when trying the back to false method.
imgur.com/a/FsSX0
*It says no port available since i removed the phone*

UnBrick Leeco Phones - LeEco variants X720/X727* Updated with X722 instructions

{
"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

Question I am stuck in fastboot and can only boot into fastboot please help??

I can only accsess fastboot and cannot reboot into anything except fastboot.... I tried extracting the payload bin but can only flash a few lines then I am told to reboot into fastbootd but cannot access that either... I cannot access recoveries either and I have tried to flash them but still wont budge... any ideas??
Use MSM tool
I also have this problem and I can't get it to EDL mode nothing happens stuck in fastboot.
I just typed a whole guide on how I managed to solve this in detail and the tab got closed out... in short then, download Qualcomm drivers and not oneplus's. There are many drivers in the file, just extract the whole thing and point to the file on device manager and include subfolders. It should find which I think was the HS-USB QDloader 9008 driver then install. Make sure you download the correct MSM for your version. The latest for global (or O2) is only hosted on one server and was going to take 12 hours to download on highspeed internet so I used lemonadep_22_O.05_210324 being 11.2.2.2. Use the Win7 version. Even though you cannot use EDL, you can reference these key combinations to get it recognized. If you're having a completely black screen, use the all button press hold until it vibrates. Make sure you are shutdown all the way and if needed use fastboot to. With MSM opened, drivers installed, and phone off, hold both vol keys and connect to PC. Hit Enum to refresh connections and hopefully it shows up and you can get a successful download complete. I found that the black screen was actually the device being in recovery mode. It was possible to successfully enter recovery using boot with power and volume down at times, although all sideload OTA's (along with prior fastboot flash boot *.img, fastboot -w, fastboot update, fastboot reboot-edl, ect.) failed. There was a lot of trial and error where just repeating some things after they had failed almost magically started working or stopped however this process is what worked in my case.
xifo.0001 said:
I just typed a whole guide on how I managed to solve this in detail and the tab got closed out... in short then, download Qualcomm drivers and not oneplus's. There are many drivers in the file, just extract the whole thing and point to the file on device manager and include subfolders. It should find which I think was the HS-USB QDloader 9008 driver then install. Make sure you download the correct MSM for your version. The latest for global (or O2) is only hosted on one server and was going to take 12 hours to download on highspeed internet so I used lemonadep_22_O.05_210324 being 11.2.2.2. Use the Win7 version. Even though you cannot use EDL, you can reference these key combinations to get it recognized. If you're having a completely black screen, use the all button press hold until it vibrates. Make sure you are shutdown all the way and if needed use fastboot to. With MSM opened, drivers installed, and phone off, hold both vol keys and connect to PC. Hit Enum to refresh connections and hopefully it shows up and you can get a successful download complete. I found that the black screen was actually the device being in recovery mode. It was possible to successfully enter recovery using boot with power and volume down at times, although all sideload OTA's (along with prior fastboot flash boot *.img, fastboot -w, fastboot update, fastboot reboot-edl, ect.) failed. There was a lot of trial and error where just repeating some things after they had failed almost magically started working or stopped however this process is what worked in my case.
Click to expand...
Click to collapse
After hundreds of trys I finally got it scared ****less that I lost my phone.
holydemon said:
After hundreds of trys I finally got it scared ****less that I lost my phone.
Click to expand...
Click to collapse
lol same here, you say it's working now though?
xifo.0001 said:
lol same here, you say it's working now though?
Click to expand...
Click to collapse
Yeah but that was a hassle should've been easier to reach that interface. I was almost sending it to service for nothing but a stupid unreachable interface nonsense.
Also to note when I tried with original cable from the box was successful the other usb cable gave me problems.

Categories

Resources