Hi all,
After reading on letv.re that some people managed to brick their devices and were looking for a fix, I started to check more and more about the issue. What happened to some was that the phone would switch itself off and enter into Qualcomm Recovery Mode and would be seen when connected to a computer as “Qualcomm HS-USB QDLoader 9008”. For others, by flashing wrong files the phone would end up in the same state. Luckily a fix had been found, and it was shared by ParasiTe_RemiX.
DISCLAIMER
Given that maybe nothing will happen to your warranty and this is an unbricking tool, there are small chances that your device might get bricked for good, and I feel the need to say that I am not responsible for any damage caused by following these instructions. Any modification that you do to your phone you're doing at your OWN RISK.
Keep in mind that if your phone goes by itself in the QDLoader mode, it’s better to try some combinations below before flashing it using this method:
1) Keep the power button pressed for about 2 minutes, or
2) Keep the power button + Vol up pressed for about 2 minutes, or
3) Keep the power button while connecting the phone to a wall charger, or
4) Bring the phone into a bright light and press the power button (or power button + Vol up) for about 2 minutes, or
5) Keep the phone charging for more than 24 hours and repeat all the steps above.
If nothing works and you are willing to fix it and you’ll give up all your files, then this fix is for you. Or if you have flashed some wrong files and there is no Fastboot, nor Recovery, this is to be followed. Or if you want to reset your phone to a “factory state”, this is the way to go, and by that I mean if you want to check that your fingerprint sensor is working, or you have some other issues, it’s good to revert it this way.
What you will need:
a) A Windows computer
b) FlashOne program - the flashing program for the software
c) QFIL files for X820 (looks like some dev software dating April,2016)
IMPORTANT – YOU WILL LOSE ALL YOUR FILES ON THE PHONE, PHOTOS, MUSIC, APP DATA, INTERNAL STORAGE WILL BE WIPED.
So if your phone is in this Qualcomm Recovery mode, you can just connect it to the computer, and jump to step 3, if not, and you simply want to flash it, start from step 1.
1) To enter Qualcomm Recovery mode, first turn off the phone and go to step 2
2) Keep pressed Vol Up (+) and Vol Down (-) together and connect the phone by USB cable to the computer.
3) You will see that the computer will install drivers for "Qualcomm HS-USB QDLoader 9008".
4) Unzip FlashOne and start "main.exe". Once you've opened the flashtool you'll see "Flash Type". Here select "Qualcomm - flash dead phone".
5) Select your phone - "COM ..." from "Select device" - here should be the same COM ... as it shown in Device Manager under Ports (COM & LPT) > "Qualcomm HS-USB QDLoader 9008 (COM ...)"
6) Select File "LeMax2QFIL.zip" from the folder where it is saved
7) Press "Flash" in the lower part of the window
8) Once completed, disconnect the phone and power it up
9) Go to Settings – Storage format the internal storage.
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.
That's it. More info you will find in FlashOne program, actually it's almost like I've described it here.
You will be reverted to a "dev" version of the phone, somewhere with April build date. Keep in mind that it's EUI 5.6 and the kernel is different than EUI 5.8. Update it to latest EUI with stock recovery and then install the custom recovery of your choice.
Most of the guys install a recovery for 5.6 on EUI 5.8 or vice versa and then they get the blue LED. That's why you should read the instructions for each recovery and make sure you know which one you're flashing.
Download files:
Mega:
https://mega.nz/#F!0gwgxbxD!-iud2O-6uZ0F3Geofz-NyA
Google Drive:
FlashOne:
FlashOne1.9.zip
drive.google.com
QFIL:
Lemax2QFIL.zip
drive.google.com
TWRP: https://forum.xda-developers.com/le-max-2/development/twrp-root-14s-rom-x820-t3382221
https://mega.nz/#!Jl4DATLI!Z08l-0SWc98C1qUGDEOcTsj96DlY627B7nHtlKCp6qw
https://mega.nz/#!slYmEJ6K!Onc5pjb3teB9J6AunZnEe-k6mDJwQ2tQwUt0X51AudI
Stock Recovery (not tested) and needs an EUI ROM to be instaled as update.zip:
https://mega.nz/#!B0ZGgSQB!33UG9jpEL6b_zJm4M01yRpI0x4uHA4Q1XzaS0ntXVSI
Edit: Post updated.
Thanks
Hi
First of all I want to thank you for posting this solution. Yesterday I managed to solve it too but it took me a while to find all this info.
Now I have ran into annother problem, I am not able to flash any rom from the stock recovery, it says "file corrupted" every time.
Any solution to this?
rapiteu said:
Hi
First of all I want to thank you for posting this solution. Yesterday I managed to solve it too but it took me a while to find all this info.
Now I have ran into annother problem, I am not able to flash any rom from the stock recovery, it says "file corrupted" every time.
Any solution to this?
Click to expand...
Click to collapse
Honestly, I did this restoration of the phone about a month ago. I encountered some issues with the stock recovery but I can't remember what I did to fix it. I think I installed 017s at that time, directly from the dev software. Restarting the phone to recovery I think didn't work. I believe you should turn it off and then start it to recovery directly. I remember I wanted to download 015s, 016s, and even I gave up and wanted to install TWRP for 5.6 EUI but the stock recovery at some point worked. Try to turn off the phone (not restart) and then switch on in recovery. And check erase data as well.
valy_cta said:
1) To enter Qualcomm Recovery mode, turn off the phone. Keep pressed vol up and vol down and turn on the device by pushing the power button.
Click to expand...
Click to collapse
Hello, I just wanted how does it look to see the phone in its normal state but cannot switch it on againg form normal opration. Is there eny key combination. It looks like bricked just now
regard Filozof71
OK, it works. Need press power button ober one minute. Uff
Leeco X910 brick
Hello, my leeco x910 is bricked...
Black screen, no led, no sound nothing just usb connection is ok for flashing 9008 mode..
Is possible to obtain the good .mbn file for flashing?
Please help me
Best regards
valy_cta;69439085
1) To enter Qualcomm Recovery mode said:
Hello, I'm on Windows 7, I enter #3 point above but I can see only QUSB_BULK device under devices manager but Windows 7 does not have any drivers for it. I tried to dwonload some but withous success. Has anybody runover rhis instruction? Uder which Windows version?
OK. Under Windows 10 it works means it installs the phone as Qualcomm HS-USB QDLoader 9008 and its visible in FlashOne program.
Great appreciation to valy_cta!
regards Filozof71
Click to expand...
Click to collapse
Problem
My phablet give me problem.
Log:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_ddr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
what am I doing wrong?
slawin wynterz said:
My phablet give me problem.
Log:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_ddr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
what am I doing wrong?
Click to expand...
Click to collapse
The link of this file is corrupted, you could post the site link. where the file is. I'm grateful.
link
bruno araujo said:
The link of this file is corrupted, you could post the site link. where the file is. I'm grateful.
Click to expand...
Click to collapse
drive.google.com/drive/folders/0BzteXVVFgQLpZndPRmhDNDJiXzg
UP
UP
slawin wynterz said:
drive.google.com/drive/folders/0BzteXVVFgQLpZndPRmhDNDJiXzg
Click to expand...
Click to collapse
slawin wynterz said:
UP
Click to expand...
Click to collapse
He fixed his phone finally.
OP updated.
slawin wynterz said:
drive.google.com/drive/folders/0BzteXVVFgQLpZndPRmhDNDJiXzg[/QUOTE
thank you, now I could install clean ROM
Click to expand...
Click to collapse
hard brick LeEco Le Max 2
hello,
thanks for the guide,
I installed the Lemax2QFIL but then
I can not istall any rom.
I renamed the various rom in update but the system responds file corrupted every time.
beachboys1970 said:
hello,
thanks for the guide,
I installed the Lemax2QFIL but then
I can not istall any rom.
I renamed the various rom in update but the system responds file corrupted every time.
Click to expand...
Click to collapse
Reboot phone, after power on one time flash it.
Did you find a fix for this? I am struggling with Lemax x910
slawin wynterz said:
My phablet give me problem.
Log:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_ddr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
what am I doing wrong?
Click to expand...
Click to collapse
Hi,
Did you find a fix for this? It seems like you resolved the error somehow. Would you be willing to share how you did that please? I would be extremely grateful. I continue to see the above errors as well.
---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------
valy_cta said:
He fixed his phone finally.
OP updated.
Click to expand...
Click to collapse
Do you know how he fixed it? I also continue to see the exact same error on the lemax pro x910 and I have pretty much exhausted my options at this point in time. Your help would be extremely appreciated.
the error that I see is as follows:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_d dr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
bil20 said:
Hi,
Did you find a fix for this? It seems like you resolved the error somehow. Would you be willing to share how you did that please? I would be extremely grateful. I continue to see the above errors as well.
---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------
Do you know how he fixed it? I also continue to see the exact same error on the lemax pro x910 and I have pretty much exhausted my options at this point in time. Your help would be extremely appreciated.
the error that I see is as follows:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_d dr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Reboot phone (long press volume "-"), after power on (long press volume "+" "-" and power) and just one time flash it.
bil20 said:
Hi,
Did you find a fix for this? It seems like you resolved the error somehow. Would you be willing to share how you did that please? I would be extremely grateful. I continue to see the above errors as well.
---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------
Do you know how he fixed it? I also continue to see the exact same error on the lemax pro x910 and I have pretty much exhausted my options at this point in time. Your help would be extremely appreciated.
the error that I see is as follows:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_d dr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
I don't think that you can flash a X910 with X820 files, although I never tried and never heard someone to do so, the results might not be too good.
That error was due to the fact that he was not pressing the buttons properly before connecting to computer. Keep Vol up and Vol down and connect the phone. It should be switched off before.
Good luck!
Thanks very much
How would I switch off a hard bricked device? Every time I connect the device, the device manager shows that it's been connected "Qualcomm ------ 90008" so how would I turn it off , especially if the battery is embedded?
Can you press the power button for at least 1 minute?
If you have it connected and it shows in computer as Qualcomm... 9008, it's ok. Maybe the files are detected as not being for your phone.
If you suddenly found the phone in such way and you didn't flash something that broke it, try to restart it as shown in the op. If not, try to discharge the battery fully that to flash something that it doesn't belong.
bil20 said:
How would I switch off a hard bricked device? Every time I connect the device, the device manager shows that it's been connected "Qualcomm ------ 90008" so how would I turn it off , especially if the battery is embedded?
Click to expand...
Click to collapse
I just long press button "-" and it diconnected after 15-20 sec.
Felt slight stupid as I saw my s5 going round the washing machine, thought I'd have a play after it's dried out.... I like learning but don't really know phones.
It was encrypted but was stock firmware.
Currently:
- It powers on
- I can get to the download in boot ok (vol. down)
- It resets when trying to get into recovery mode
- Kies see's something trying to connect but times out. Heimdall detects it but throws errors upon trying to flash , I'm yet to try Odin, just getting stock firmware as I write this.
(Heimdall error - libusbx: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] Th
e device does not recognize the command.)
I've got some more playing around to do but it feels like, at least, the storage is screwed but that's a complete guess.
1) I was hoping someone would know if it's worth playing further?
2) Whether anyone could take a guess of whether replacing the mother/logic board would be a *possible* fix
3) Could anyone point me to any resources explaining the how the phone works- I'm initially trying to understand what components sit on the logic board and the boot sequence. e.g. could the CPU/ storage be fried but it still boot this far?
Many thanks in advance for any help.
OK, I'm a little further along with this now.
I'm using various versions of odin (3.0.7,9,12.3). Various computers (all windows 10 now but did try heimdal on a 2 nix machines) and a whole lot of leads. Just getting Odin to recognise the phone was fun.
Tried using the AP part to install the BTU UK version of firmware from sammobile
Tried getting the hidden .img.tar from it and flashing that
Tried flashing a twrp recovery
But all come up with
Code:
GetPIT for Mapping
There is no PIT Partition
So I got a couple of Pit files for and tried them with the Re-partition ticked
Code:
Set PIT file...
DO NOT TURN OFF TARGET!!
Complete (Write) Operation failed
OSM All threads completed (succed 0/ failed 1)
So a few questions:
1) How do I uploda photos here? Or do they have to be inserted links. May be my low post count? Or I'm blind
2) Is it normal that odin stops recognising the phone the moment there's an error like the one's I'm having. Odin's ID:COM part goes blank and I have to remove/ insert the USB again.
I just want to check that's not some other reason.
3) Is there anyway to test whether the NAND's working/ can be accessed without pressing that scary NAND erase all button?
Many thanks
Why not just get it fixed from service center?
beardedfool said:
OK, I'm a little further along with this now.
I'm using various versions of odin (3.0.7,9,12.3). Various computers (all windows 10 now but did try heimdal on a 2 nix machines) and a whole lot of leads. Just getting Odin to recognise the phone was fun.
Tried using the AP part to install the BTU UK version of firmware from sammobile
Tried getting the hidden .img.tar from it and flashing that
Tried flashing a twrp recovery
But all come up with
Code:
GetPIT for Mapping
There is no PIT Partition
So I got a couple of Pit files for and tried them with the Re-partition ticked
Code:
Set PIT file...
DO NOT TURN OFF TARGET!!
Complete (Write) Operation failed
OSM All threads completed (succed 0/ failed 1)
So a few questions:
1) How do I uploda photos here? Or do they have to be inserted links. May be my low post count? Or I'm blind
2) Is it normal that odin stops recognising the phone the moment there's an error like the one's I'm having. Odin's ID:COM part goes blank and I have to remove/ insert the USB again.
I just want to check that's not some other reason.
3) Is there anyway to test whether the NAND's working/ can be accessed without pressing that scary NAND erase all button?
Many thanks
Click to expand...
Click to collapse
Yeah that sounds like water damage alright. I'm sorry to tell you it sounds like your NAND is semi-corrupted in that part of the BL seems to have survived but basically everything else is kaput.
If the PIT partition is missing that is a flag right there to a likely NAND corruption.
Sorry to be the one to have to tell you this but at this point you're best bet is to take it as a total loss and try to sell any undamaged parts (ex. Digitizer, LCD) to raise the cash for a new phone.
Hello guys, I have this weird A3000-H problem.
So the tablet boots normally, it loads in one particular state every time, like it's booting an image. After a while or if you try to do something, running a program, uninstalling, changing settings it's starts the cascade of pretty much "every has stopped working" and it's like that until you restart it and it's all over the same again.
So far I've tried everything I could scour from the internet, XDA forums included.
• I've tried to flash new stock rom 4.2.2, then I tried the 4.4.2 from Hesham.
If I use an older, version 3 SP Flash Tools it gives me this error at the end:
imgur com a5oKTLw.png
If I use version 5+ of SP Flash Tools it gives me an "OK" download or upgrade, but when I disconnect and turn on the tablet it's in it's same previous state, it didn't change anything.
• I tried full format - it did absolutely nothing despite SPFT giving me the okay
SPFT memory test returns this error : .imgur com / jbSUwV5.png
• I tried writing memories - nothing changes despite getting on OK message.
• I tried to fastboot CWM - I can't make the tablet to enter the mode, it just restarts and boots in it's previous state.
• I've tried to connect it to PC and delete folders manually, despite windows saying the folders are deleted and not showing them anymore, as soon as I reconnect the tablet again they show up as they were. It's like the on board memory is locked to writing anything on it.
• Of course I tried manually resetting to factory settings, uninstalling software from the tablet and so on, but that just makes the errors of "stopped working" to pop and restart to same condition.
I would appreciate any help at this point, I'm about to give up on it.
P.S.: I can't post whole links yet so I had to improvise a bit.
Hi all. If anyone could help me out I"d greatly appreciate your time and any advice.
So I got this tablet from my brother, working and all, but Google FRP was on it and he couldn't remember the credentials from when he first set it up. "No worries," I proclaimed like some advanced Android tech, lol, "I'll get it running" First thing, I downloaded the "stock.img" firmware from the only other ONN tablet page. Then SPFLASH tools. Then I plugged in the tablet; holy crap theres instant connection (this is better than ODIN haha). I immediately click the Download tab, load the scatter file, the stock directory, etc and hit "Download" after only a couple of minutes, SUCCESS.
So it reboots.
Oh, wait wait, I did nothing to format the tablet and so I'm just back at FRP.
Back to fastboot.
Open SPFlash Tools and goto format, formal all except bootloader, Start. Now though, as I'm waiting, I look over and my niece is pressing buttons on it, nothing seemed to have happened tho on my PC except I noticed moments before, likely when my niece started pressing buttons out of my view, that the little red bar that normally shows progress turned completely red and filled from 0 to 100 in a split second. I left the device and PC alone, only to get a notification after just a couple of minutes reading:
"ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] ENABLE DRAM FAILED!
[HINT]:
Please check your load which matches to your target which is to be downloaded"
**I'm noticing that my PC, for whatever reason, is bouncing between seeing the device as USB Serial COM5 and "MK6***" So when the device bounces is when the connection seems to be losing. I'd be happy to share my output for format if this makes sense to anyone.
The only thing is, I cannot get any screen whatsoever to show up on this tablet. I've tried holding down power, power+vol down, power+vol up+vol down, for up to 30 seconds and yet nothing comes up. It's almost like I don't have a bootloader or anything anymore as the device just kind of seems stuck. Even if I try using the DOWNLOAD tab, I still get the message as above. If I try to do READBACK I get a slightly different message. The READBACK will start and the red bar doesn't fill up instantly but after a couple of minutes I get:
"ERROR : S_COM_PORT_OPEN_FAIL (1013)
[COM] FAILED TO OPEN COM PORT
[HINT]:
1.retry a new COM port (tried switching to another USB with no success);
2.retry a new cable;
3.retry a new device;
4.restart the computer and try again.
Am I missing drivers? I communicate with my MOTO on this laptop just fine because of the google usb_driver, but maybe I'm missing a driver? Or maybe the device is bricked in just a tiny instant of someone tapping a button?
Any help would be much appreciate. Thanks a lot!
Please help me unbrick the phone if possible.
I was using TWRP to flash a backup (of stock image) but it gave me error (I don't remember the error message).
Then the phone discharged and I cant turn it on. No screen, no vibration, but the empty battery image appears if the battery is low. I can charge it and red led light up (blinks in three stages).
If I connect to pc green light appears (flash mode).
Xperia Flashtool gives error when I try to flash stock rom:
ERROR - Processing of *.sin finished with errors.
All .sin files give the same error, but the .ta files can be written to device.
In console (I use linux on pc) there are error messages too:
org.flashtool.flashsystem.X10FlashException: S1 Data CRC32 Error
at org.flashtool.flashsystem.S1Packet.validate(S1Packet.java:84)
at org.flashtool.flashsystem.io.USBFlash.readS1Reply(USBFlash.java:86)
at org.flashtool.flashsystem.io.USBFlash.writeS1(USBFlash.java:61)
at org.flashtool.flashsystem.S1Command.writeCommand(S1Command.java:77)
at org.flashtool.flashsystem.S1Command.send(S1Command.java:97)
at org.flashtool.flashsystem.S1Flasher.processHeader(S1Flasher.java:278)
at org.flashtool.flashsystem.S1Flasher.uploadImage(S1Flasher.java:289)
at org.flashtool.flashsystem.S1Flasher.runScript(S1Flasher.java:642)
at org.flashtool.flashsystem.S1Flasher.flash(S1Flasher.java:704)
at org.flashtool.gui.tools.FlashJob.run(FlashJob.java:50)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Does it mean that the phone is dead?
Thank you.
Ok. I know the problem. I flashed wrong backup with twrp. I have two of this type of phone and that wasn't the right one's backup. So I cant use it anymore because the trim area is overwritten and I don't have a backup.