[LeEco Le Pro3 Questions & Answers] dr4stic:
I have what I needed, thanks!

Hi, I'm wondering if someone with a Le Pro3, either the CN or US model (or both) could please provide me with the output for dmesg and logcat.

Pre-requisites:

have adb installed and working for your device

Make sure adb debugging is on for your device, and your computer recognizes your device, and is authenticated for your device. (I don't know EUI, I've only ever dealt with western AOSP/CAF style roms, you'll have to understand and manage this all yourself).

PLEASE don't type the commands from memory, they have case sensitive options. Please copy and paste them. Thank you.

The following commands need to be executed shortly after reboots. Please don't run them if the device has been on longer than a minute. In fact, please don't stray far from the procedure, please.

Reboot device

Once booted run "adb shell dmesg > dmesg.txt"

Run "adb shell cat /proc/partitions > partitions.txt"

Run "adb shell df > df.txt"

Run "adb shell df -P > df-P.txt"

Run "adb shell mount > mount.txt"

Reboot the device and perform the next adb step once it's started to boot

run "adb logcat > logcat.txt"

Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network

Reboot the device and run the following once it's started booting back up

run "adb logcat -b radio > logcat-radio.txt"

Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network

Now, for some root-required tidbits (these commands could actually be dangerous!!! they will be running as root, please be very careful, you've been warned): You have two ways you can do this:

Run "adb root" to put adb in an automatic root mode (this requires that you have root and allow adb commands to be run as root)

Run "adb shell ls -la /dev/block/bootdevice/by-name > by-name.txt"

Run "adb shell ls -la /dev/block/bootdevice/by-num > by-num.txt"

Please check the files to verify that the contents are not an error. The other method, if switching adb to root mode doesn't work, would be to:

Run "adb shell"

Run "su" to put your shell into root mode, NOTE: BE VERY CAREFUL HERE (this requires that you have root and allow adb commands to be run as root)

Run "adb shell ls -la /dev/block/bootdevice/by-name" and then copy/paste the output into a file named "by-name.txt"

Run "adb shell ls -la /dev/block/bootdevice/by-num" and then copy/paste the output into a file named "by-num.txt"

Finally, if you are simply not able to achieve root on your device (either in general, or just for ADB), both of these tasks SHOULD be possible when you're booted into the TWRP recovery. If you don't have TWRP installed, then don't worry about it. I'm just assuming you do.

Note: None of these commands will produce empty files. If you get empty files, something went wrong. If only a few are empty and you can't seem to get them working properly, just send me what you do get.

Once you've done these things, zip up the files and send them to me in a private message. You don't want these posted here unless you want people knowing your phone number. The text files, especially for the logcat and radio output will be large, but they should compress down to something quite reasonable. Also, please make sure to include your model number so I know which I'm working with. Thanks much.

Thanks.