[LeEco Le Pro3 Questions & Answers] tylerciggy:
Update 2.- It seems that the flashing I mentioned earlier didn't kill the phone and was just mere coincidence. For now, I'm still trying to find if there is a hardware damage issue.

By the way, currently if I try to charge the phone with my newest cables, it won't charge. The cables are fine, in fact, if I disconnect the battery the phone will demand 0.34amps, but when I connect the battery it instantly drops to 0s (Im using a power bank and an usbmeter, a cheap chinese one), but here is the curious thing... this doesn't happen with my usual cable. With my usual cable it will demand up to 1.4amp so this maybe be an issue of a damaged charging IC.

I bought an x820 and I can confirm some ways to go into EDL, although they may not have the exact same pattern in the X720s

I can confirm that the x820 does go into EDL mode from “vol+, vol-, power”

- It doesn’t need to be turned off to do that.

– It can go into EDL while still being connected to the PC.

– It does that in 9 seconds after the the keys combination.

– It can go into EDL with this method even if the phone is turned off and already connected by cable to the PC

** It doesn’t vibrate when going into EDL in neither case, neither of going from EDL to recovery/fastboot.

This part is curious, because my x722 when was in EDL could go into recovery/fastboot and had an specific vibrating pattern.

The power off + vol up, vol down + cable works too.

Update 1.-

Well, bad news. I did flash something, the devinfo.bin and devcfg.mbn in the flashallpackage... now the phone is "dead" again. It's as dead as it used to be before I installed the qualcomm recovery mode drivers. The thing is now I don't have neither EDL, neither Fastboot, neither recovery.

So pretty much I'm really now in serious big troubles, because now I realize that the one that kept my phone alive were the drivers.

Now I have to see how to extract that info and make the drivers to "see" again my phone, which I imagine won't be easy at all.

So if anyone knows how to force it to be in EDL again, will be much appreciated

(yeah, I already the "vol up + vol dwn + power + cable" )

-----

Hi.

I know there are a lot of threads about this, believe when I tell you that I had opened more than 20 threads and I still have on my browser 5 threads over 10 pages each one, but there is a lot of information (and a lot is repeated and sometimes it even has some issues about clarity of that information).

I had my phone over a year with stock rom and no problems at all, but when I installed lineage 16 (android 9), I got some suddens "deaths", but I was able to return to life by simply going into fastboot.... until last time, I connected my charger when I was 18% and the phone "died". It was warm until battery got drained. I believe the phone got automatically into 9008, although I'm not sure of that yet

(Update to this. I'm sure now that it wasnt on EDL mode at all if PC can't recognize it*)

The thing is, I can still access to my phone. (well, I could when I originally wrote this*)

When I installed the drivers to prepare for the Qfil flash via EDL, suddenly my PC was able to see my phone.

If I pressed Vol up + Power (over 12 seconds), the phone "turn on" into a very primitive recovery

If I pressed Vol dwn + Power (same time), the phone goes into fastboot mode.

It will vibrate once at second 6, then again at second 6.5 (so you can probably call this vibrate twice) and then again at second 12.

Every time the PC will make a notifying sound but you won't see it in device manager because those are not EDL.

You can confirm which mode you are by doing in msdos in your adb folder

adb devices

fastboot devices

In both cases the phone vibrates.

Two vibration for the reset (around the 6 seconds of pressing the buttons), and another vibration after "powering on" (around the 12 seconds), BUT I can't see a thing in the display.

If I just press power, it goes into EDL (or I guess so far)

The recovery is very very primitive. Mount /data, /system and /sdcard was really a pain. I managed to do it with the help of a friend and I recovered my info, so I can really just flash it and everything will be over in less than an hour, but I still want to bring it to life without flashing stock rom.

I tried to use screencap, screenrecord and settings, but they don't seem to be working under that recovery mode.

If I use:

adb reboot recovery

it reboots into recovery again, and unmounts everything that was mounted

adb reboot fastboot

it reboots into EDL mode I suppose (in device manager I can see the 9008 device, althogh I haven't rebooted my PC since the driver installation)

adb reboot

it reboots into EDL

fastboot reboot recovery

it reboots into EDL

fastboot reboot

it reboots into EDL

fastboot boot twrp.img

it boots into primitive recovery mode, and seems slightly different over the vol+up+power recovery mode, even that it is supposed to be the same recovery.

=======

I'm going to explain how to mount /data, /system and /sdcard

In ADB SHELL

-To mount storage-

#.- cd /dev/block/bootdevice

..#.- mount sda10 /sdcard

-To mount system-

#.- cd /dev/block/bootdevice

...#.- mount sde19 /system

-Alternative mode - mount data and/or system- (data has the storage as well)

This is a little bit more complicated, as I couldn't mount /data directly

#.- cd /dev/block/bootdevice

..#.- mount sde34 /sdcard (it can be to another folder)

..#.- cd /sdcard/etc

..#.- cp fstab.qcom /etc/fstab

..#.- mount /data

..#.- mount /system

If you want to copy data using pull, have in mind that mine stuck A LOT while trying to copy large folders containing thousands of pictures (I still can't backup the whatsapp folder, although I have a cloud backup of it, fortunatly)

Assuming you mounted /data, here is the MSDOS command to copy an example folder

---This is an example using the last method to mount /data, it is different if you mount sda10 into /sdcard--

(this is an example folder, you can create it in the windows explorer if you wish)

C:\ADB\md CameraPics

C:\ADB\adb.exe pull /data/media/0/DCIM/. CameraPics

(there is a space between DCIM/. and CameraPics)

=======

I tried "fastboot boot twrp3232.img" but still no image and I touch the screen but it never vibrates.

I tried "fastboot boot boot.img" (the boot.img that comes with the lineage16.zip)

I tried cleaning the dalvik-cache inside /data, but still nothing.

I tried to change some brightness value, but still nothing

I tried to change brightness settings through "settings" in adb shell, but it can't find the service.

I tried dumpsys battery in adb shell, but it can't find the service as well.

I want to try to reset battery value information.

I want to try to "reflash" or better said, "update" the lineage, but TWRP is not working (#.- TWRP does not appear to be running. Waiting for TWRP to start) and I can't find how to start it within adb shell.

Although I may probably be using tsonming flashall before someone may be responding (I will try to finish the other threads before flashing), but I will do it image by image and rebooting, to see which one "fix" the issue.

Thanks in advance and I hope this information can help people to recover their files before debricking the phone.