Database Users

[Q] phone won't boot, screen goes black in recovery mode

I've had my htc panache (canadian mytouch 4g) for just one day, and it blew its fuse at me. When I went to sleep, it worked fine, but when I woke up, the screen was black and nothing was working. I pulled the battery out and plugged it back in, and now the phone is stuck at the HTC boot screen. I can get into hboot, but some options just don't work, and hangs the phone:
-REBOOT BOOTLOADER (from FASTBOOT menu)
-FACTORY RESET
-IMAGE CRC (hangs on "Calculating... please wait")
-RECOVERY (shows an image of two curved arrows with a regular arrow within, over a tilted cellphone, then the image is reversed, and the screen goes black and the phone vibrates exactly 7 times.)
I tried using the RUU, but my computer won't detect my phone either in hboot or recovery (not that it has the time to detect my phone in recovery). Perhaps I am missing drivers? the device manager shows the phone as a generic "USB Device".
I've tried to get into download mode, but the only other button combination aside from volume down + power that did anything was power + back button, and that brought me to hboot into the fastboot menu.
I tried to update the phone by putting the latest pd15img file from the wiki onto the sd card but after it scans the file, the phone doesn't ask me if I want to update. it just goes back to hboot, and rebooting hboot does the same thing.
How can I get into download mode, anyway?
EDIT: just found hboot drivers. something that works, for once.

Adb maby?
Sent from my LG-P970 using xda premium

wouldn't have been able to use adb if the phone wasn't detected, now was it?
anyway, I found some hboot drivers that seem to work. I'll try the ruu first.

Correct me if I'm wrong, but if I remember correctly the 7 vibrations while trying to enter recovery signifies hardware failure...
Sent from my myTouch 4G using XDA Premium HD app

Ok so... I managed to get the phone charged, and yet RUU still tells me my phone battery is charged at less than 30%, and I can only exit. what gives? Is there a way to bypass that?
(By the way, the hboot drivers I used were from a website called unrEVOked. perhaps these were for another model? where could I get hboot drivers for my phone?)
As for the hardware failure thing, I'm not buying it. at least not yet. If it trully were a hardware failure, the phone wouldn't boot, eh? I can get to hboot and fastboot and fiddle around for a bit, and recovery works for around 10 seconds before it goes blank at me.

So ADB doesn't see my phone but fastboot does. seeing how switching my phone to the fastboot menu installed htc's own drivers right away, I'm not surprised.
Where are the adb drivers for the glacier/panache/mytouch 4g? the only ones I could find are for motorola phones.
EDIT: "C:\sdk-tools>fastboot -p SH16KRM01484 -w
erasing 'userdata'... FAILED (status malformed (1 bytes))
finished. total time: 0.016s"

Try this thread for adb setup:
http://forum.xda-developers.com/showthread.php?t=928370
Also, did you have (flash) a recovery installed? If I remember right, a triangle around a phone when you enter recovery from hboot means you didn't have one installed/flashed. I also remember reading that 7 vibrates mean hardware failure. There are lots of phones that had failed emmc's and would still boot but get stuck at the splash screen. Are you verifying the md5 when downloading ruu?

http://www.htc.com/us/support/htc-mytouch-4g-tmobile/software-updates
That link is to the HTC drivers you're looking for. Once you get it set, you should be able to flash the RUU and I would suggest making sure you have a recovery flashed as well...would help a lot right now if you could at least get there.

Chomanator said:
http://www.htc.com/us/support/htc-mytouch-4g-tmobile/software-updates
That link is to the HTC drivers you're looking for. Once you get it set, you should be able to flash the RUU and I would suggest making sure you have a recovery flashed as well...would help a lot right now if you could at least get there.
Click to expand...
Click to collapse
It's the third driver I download, one was called htcdriver.exe, the second one was the same with a version number, and the third, this one, and none work. nothing happens when I click on them. on the task manager I see the process starting and just quitting for no reason.
I'm starting to think technology as a whole is against me.
I'm gonna try the drivers included with pdanet.

So after getting the right adb drivers...
"C:\sdk-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\sdk-tools>"
nothing.

anyone?
(EDIT: fastboot started working. here's what getvar all gave me: )
C:\sdk-tools>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.89.0005
INFOversion-baseband: 26.09.04.26_M
INFOversion-cpld: None
INFOversion-microp: 0429
INFOversion-main: 2.10.1530.1
INFOserialno: SH16KRM01484
INFOimei: 357935045141682
INFOproduct: glacier
INFOplatform: HBOOT-7230
INFOmodelid: PD1510000
INFOcidnum: VIDEO001
INFObattery-status: good
INFObattery-voltage: 4183mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 6a4abc53
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s
I'm not sure if this can be helpful or not, but here.

It don't appear to be bricked...try flashing 4ext recovery.
Sent from my HTC Glacier

I tried to flash the phone using one of the pd15img.zip files, but I got the following error: "CID Incorrect!"
Does CID stand for Carrier ID?

So it shows you have s=on and latest gb hboot, so assuming you were running the stock rom. What was the last thing or things you did before plugging out in to go to sleep? Have you tried to select factory reset? If you only had the phone for 1 day, why don't you take it back to where you bought it?

ronin178 said:
So it shows you have s=on and latest gb hboot, so assuming you were running the stock rom. What was the last thing or things you did before plugging out in to go to sleep? Have you tried to select factory reset? If you only had the phone for 1 day, why don't you take it back to where you bought it?
Click to expand...
Click to collapse
Nothing. two hours before I went to sleep, I installed a few games and widgets, and everything went fine. I just quit what I was playing (some 3d racing game), put the phone on charge and went to bed.
Factory reset does nothing (the phone just hangs), and I can't return it because I got the phone from someone else (I doubt he's somehow responsible for this seeing how it's not the kind of defect you can just hide like that) and there was no warranty anymore on the phone, so I can't have it exchanged.
If I really can't do anything with that phone, I'll just sell it for parts on ebay I guess. but for now, I'm not giving up. I'm downloading the videotron ruu again, and will just put the zip file it extracts onto my sd card and rename it accordingly. Hopefully that will work.

I've downloaded the ruu, copied the rom.zip file from the temporary folder into my sd card, renamed it to pd15img.zip, and let it load in hboot. it asked me if I wanted to update, said yes, and it's stuck. I think it IS bricked, after all.
Parsing... [SD ZIP]
[1] BOOTLOADER -Updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] USERDATA
[7] TP
[8] TP
[9] RADIO_VZ
[10] RADIO_CUST
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Update is in progress...
Do not power off the device!
Click to expand...
Click to collapse
It's stuck at where -Updating is, next to BOOTLOADER. I've left it there for 20 minutes now, and it hasn't budged. and I know that bootloaders aren't that big, unless the update is doing something fancy that makes it super slow, so... ****.

Is there a way to switch the phone to download mode? not hboot or recovery, but download mode.

adb just won't detect my phone :c

will somebody tell me how to put that phone into download mode?

Which RUU are you using?
Sent from my myTouch 4G using XDA Premium HD app

been working 2 days many hours to resolve PLEASE HELP!

"Power On This Pops Up As A Black Screen"
ap fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 2:30:05)
eMMC Info: Size 8GB
Device is LOCKED, Status Code:0
Battery OK
Connect USB
Data Cable
Fastboot Reason: Sticky bit factory_fastboot
------------------------------------------------------------------------------------------------------------------
The Version Is 4.4.2 of the operating system
when i press the power button this happens, i can however hold the power button and both volume buttons to get into the operating system, by loading normally, I need to fix this issue so i can take another swing at trying to mod this razr-m xt907
the previous issue, before i made it to this issue was
Fastboot Reason: fastboot failure this happens if you mess up and try to towel root from your phone as in download the file onto your phone and then run the file from your phone, so any user out there trying to root their phone, that is not the way to go. Also I Am Dubbing This The Screen of Black Death!
As per Rooting the Phone, I tried Using "motofail2go" I press enter the App communicates with the phone then the dameon Starts, after that nothing at all happens i let it sit for 15-20 minutes and nothing happens
please help me figure this out, my goal is to put cmod on my phone, it is locked and unrooted at the moment, it has full charge and something has went wrong taking the above information walk me through it please, im on my knees begging. Ill even donate some money on the first of the month if we can get it working.

just_guy said:
"Power On This Pops Up As A Black Screen"
ap fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 2:30:05)
eMMC Info: Size 8GB
Device is LOCKED, Status Code:0
Battery OK
Connect USB
Data Cable
Fastboot Reason: Sticky bit factory_fastboot
------------------------------------------------------------------------------------------------------------------
The Version Is 4.4.2 of the operating system
when i press the power button this happens, i can however hold the power button and both volume buttons to get into the operating system, by loading normally, I need to fix this issue so i can take another swing at trying to mod this razr-m xt907
the previous issue, before i made it to this issue was
Fastboot Reason: fastboot failure this happens if you mess up and try to towel root from your phone as in download the file onto your phone and then run the file from your phone, so any user out there trying to root their phone, that is not the way to go. Also I Am Dubbing This The Screen of Black Death!
As per Rooting the Phone, I tried Using "motofail2go" I press enter the App communicates with the phone then the dameon Starts, after that nothing at all happens i let it sit for 15-20 minutes and nothing happens
please help me figure this out, my goal is to put cmod on my phone, it is locked and unrooted at the moment, it has full charge and something has went wrong taking the above information walk me through it please, im on my knees begging. Ill even donate some money on the first of the month if we can get it working.
Click to expand...
Click to collapse
You can fix the sticky bit issue pretty easily through another fastboot command. The command is: fastboot oem fb_mode_clear - Check out this thread for all the details. http://forum.xda-developers.com/showpost.php?p=41706009&postcount=2
Alternatively, a full reflash of the firmware generally fixes the issue.
Sent from my Moto X 2014 Pure Edition using Tapatalk

xKroniK13x said:
You can fix the sticky bit issue pretty easily through another fastboot command. The command is: fastboot oem fb_mode_clear - Check out this thread for all the details. http://forum.xda-developers.com/showpost.php?p=41706009&postcount=2
Alternatively, a full reflash of the firmware generally fixes the issue.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
I know its been a long time but um here is a belated thank you! I did in fact solve the issue thanks to xda and you, so truly thank you

!!!URGENT!!! Completely bricked after updating HELP!!!

last night i got the notification to say that i was able to update to 7.0 and i was so excited that i kinda forgot about xposed and stuff and now
the phone is completely useless it wont turn on it just does nothing, when its charging the white light flashes but still nothing Please help

Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?

echo92 said:
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
Click to expand...
Click to collapse
nope not seeing it

Hmm, so you're not getting anything showing up in Device Manager (like in this thread https://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943 )?
I am not familiar with the procedure of how to unbrick a device like this, vache has uploaded a blank flash file (https://forum.xda-developers.com/showpost.php?p=70701015&postcount=1975), I hope someone else can guide you on the procedure to unbrick your phone if you need such a file.

Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.

bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
thankyou it worked perfectly

The same here after update!
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?

alemangioni said:
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
Click to expand...
Click to collapse
If fastboot still works, perhaps try this fastboot Nougat image, see if that'll flash? https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
It requires you booting into bootloader (so power down your device, wait 5 seconds then hold the volume down and power button, should then boot into bootloader), so it might flash a working recovery and system onto your device.

bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
I believe there are two possible reasons...
Either 2-3 minutes forces a fully hard reset.
Or
If you have a really really flat battery sometimes as it charges and then boots up it gets stuck in repeated reboot since effort to boot drains more than it can charge in that time, so holding power button holds boot sequence long enough for battery to gain enough charge to allow boot to work..
Both are just my opinions so might be completely wrong

I think it's Option no1, because in my case the battery was nearly full charged.
Nevertheless... One guy happy to have helped, the other guy happy to have reanimated his phone:laugh:

Unknow P9 lite from a friend

Hi, many thank in advance for people making this forum alive and developer who working on it.
I received a P9 lite from a friend of mine and I dont realy know what he tried to do but. The phone show me warning about the unlock but can't boot on system and when i tried to flash TWRP on it, the phone show me multiples errors in terminal (when i tried to flash boot with a stock room)
Bref, I don't know the actual state of any partition and i have to back from scratch about everything on it. What could you suggest to do about ? Some verifications and others things ?
The only mode i can boot on is recovery fast boot (the white page) and showing me everything is unlocked. And when i let it boot for a while i finally boot on eRecovery.
I am all your to test and give you information about.
Many thanks in advance for any help.
(I'm not so bad in terminal things by the way)

Buy dc phoenix and force the update.app to it. Cost about 15~ $ saved my phone last day also

What error did you had when you tried to install TWRP?
Also, have you tried to put in the micro SD the stock UPDATE.APP in the dload folder and installing it pressing all the 3 buttons?
@Kcetin20 Using a paid service it's the last resource, before that I think it's better to try everything possible to restore the phone

quickly, cause it's late here in france,
Thanks for your reply.
 @Potato997 : I get no error when i flash, simply no boot when volume up and down simultaneous
terminal :
Code:
F:\PROJETS\huawei p9 lite\__OK>fastboot flash recovery "F:\PROJETS\huawei p9 lite\__OK\TWRP.img"
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.937s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.948s
what is this procedure ?
Also, have you tried to put in the micro SD the stock UPDATE.APP in the dload folder and installing it pressing all the 3 buttons?
Click to expand...
Click to collapse
@Kcetin20 : thanks, i'll try any free option before. But it's good to know there are software or solutions to force in last resort

@bumpshoveit try to see if you can force him in 2 buttons menu, shutdown phone > press volume + and volume - > press power key > if this leads you to a update menu you can flash the phone thought a SD card.

bumpshoveit said:
quickly, cause it's late here in france,
Thanks for your reply.
@Potato997 : I get no error when i flash, simply no boot when volume up and down simultaneous
terminal :
what is this procedure ?
@Kcetin20 : thanks, i'll try any free option before. But it's good to know there are software or solutions to force in last resort
Click to expand...
Click to collapse
Command not allowed when flashing in fastboot usually means the bootloader is locked.
So unlock your bootloader and try to flash TWRP again.

bumpshoveit said:
quickly, cause it's late here in france,
Thanks for your reply.
@Potato997 : I get no error when i flash, simply no boot when volume up and down simultaneous
terminal :
Code:
F:\PROJETS\huawei p9 lite\__OK>fastboot flash recovery "F:\PROJETS\huawei p9 lite\__OK\TWRP.img"
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.937s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.948s
what is this procedure ?
@Kcetin20 : thanks, i'll try any free option before. But it's good to know there are software or solutions to force in last resort
Click to expand...
Click to collapse
that procedure is you download a stock rom, extract update.app from it, put that file in a folder called "dload" on your sdcard (create the folder if it doesn't exist) and then reboot by holding volume up and down and power.
however, you need to know what localization it is (cXXX)

@Cetin20 @mjz2cool Thanks for procedure. I just took a quick look before go to work (yes i don't care, i got a nexus 5X working like a charm ME, hahaha). So I pulled out the SD card and i already found on it a fodler named dload and update.app inside. I don't remember any purpose of installation. The only I have is Huawei eRecovery trying to connect to Wifi and download but as you can imagine; nothing append
error : Getting package info failed (i got image but can't post now)
@zgomot : I think command are was allowed, cause I can upload and when I uploaded certains version of TWRP it boot up but but with multiples errors when trying to update. Now nothing work exepted eRecovery

bumpshoveit said:
@Cetin20 @mjz2cool Thanks for procedure. I just took a quick look before go to work (yes i don't care, i got a nexus 5X working like a charm ME, hahaha). So I pulled out the SD card and i already found on it a fodler named dload and update.app inside. I don't remember any purpose of installation. The only I have is Huawei eRecovery trying to connect to Wifi and download but as you can imagine; nothing append
error : Getting package info failed (i got image but can't post now)
@zgomot : I think command are was allowed, cause I can upload and when I uploaded certains version of TWRP it boot up but but with multiples errors when trying to update. Now nothing work exepted eRecovery
Click to expand...
Click to collapse
if erecovery boots up you didn't use the 3 buttons or the phone was connected to usb.
press and hold the 3 buttons until it says something about installing firmware, it should flash the update.app. if it doesn't work it will say it wasn't able to install the update. you have to do this while disconnected from usb

zgomot said:
Command not allowed when flashing in fastboot usually means the bootloader is locked.
So unlock your bootloader and try to flash TWRP again.
Click to expand...
Click to collapse
bootloader or that oem in develop settings fixed it whit dc phoenix ..

mjz2cool said:
if erecovery boots up you didn't use the 3 buttons.
press and hold the 3 buttons until it says something about installing firmware, it should flash the update.app. if it doesn't work it will say it wasn't able to install the update. you have to do this while disconnected from usb
Click to expand...
Click to collapse
i think if you do 3 button with USB connected it maybe goes to erecovery?

JimmyEatFood said:
i think if you do 3 button with USB connected it maybe goes to erecovery?
Click to expand...
Click to collapse
yeah, that's what i replied, i forgot to mention that as another option what could have caused that

Hello everyone,
First thing, thanks for your advices ! You were right, I had to press 3 button (vol up, down and power) at the same time while USB is disconnected. I finally found update.app and are actually installing it. What do suggest to me to do after ?
I would like to install TWRP, and android os nearest of google release as possible ! My friend said to me, i found tutorial and tried to follow it but nothing append like expected (don't play me guy ! Were do f**k up ?)
Any advise ?
By the way thank you again for your help ! I'll force my friend to make a donation tro XDA

Haha ! speaking to fast ! Installation seem to be ok, goes to 100% but now screen is black and nothing append ! This phone is damn

You have to unlock the bootloader first, then install Meticulus TWRP and then I suggest you CyanogenMod 13.
You can find the tutorial in the Guide section to unlock bootloader.

Lol, opened the back cover, disconnected battery. Nothing more. Screen stay black, no vibration. Nothing... is it that a bricked phone ?

bumpshoveit said:
Lol, opened the back cover, disconnected battery. Nothing more. Screen stay black, no vibration. Nothing... is it that a bricked phone ?
Click to expand...
Click to collapse
Does your pc detects the phone when you plugin ? if not dc phoenix is your last option...
Shutdown phone > volume - and put cable in see if he goes in fastboot..

My computer dit not detect the phone. Just after installation (via 3 button boot) screen goes black. And now just nothing. I pressed multiples times every possibility of button for a while and screen stay black with no backlight and nothing appear in device manager of windows. No vibration too !
It's like if battery disappear or something ! Obviously fastboot and adb does not detect anything !
So... I'll have to tell to my friend to buy a new phone ! I'll suggest to buy a Nexus... a bit less exotic phone
When I launched update from 3 buttons boot update.app were put there by my friend and i didn't know were it came from... I should have to check it before ! Damn !

bumpshoveit said:
My computer dit not detect the phone. Just after installation (via 3 button boot) screen goes black. And now just nothing. I pressed multiples times every possibility of button for a while and screen stay black with no backlight and nothing appear in device manager of windows. No vibration too !
It's like if battery disappear or something ! Obviously fastboot and adb does not detect anything !
So... I'll have to tell to my friend to buy a new phone ! I'll suggest to buy a Nexus... a bit less exotic phone
When I launched update from 3 buttons boot update.app were put there by my friend and i didn't know were it came from... I should have to check it before ! Damn !
Click to expand...
Click to collapse
have you tried holding the powerbutton for about 10 seconds?

haha, you kidding ? I pressed each for a minute at least !

LeEco Le 3 Pro - Phone in constant reboot loop

Hey guys,
Been looking around on the forum but couldn't find any info about this.
I recently purchased a Le 3 Pro and was actually working well. I had a few random reboots (I read this was something normal - happened in Snapchat, but after clearing the app cache all was well again).
Anyway, so today at work I noticed the phone just rebooted for no reason, but then it just kept rebooting and rebooting.
I have the stock Chinese rom (it's the X720 vesion by the way) so I have not done any rooting. Was planning to, but thought I'd give stock a run for its money.
So, not I'm stuck with a phone that's stuck in reboot mode.
I can get into fastboot and I tried flashing TWRP into Recovery, and that "seemed" to work (the command came back successful) however when going into recovery mode, it's just the LeEco Recovery and it doesn't do anything. So, I have to power cycle again and then gets stuck in the reboot cycle.
I don't think OEM unlocking was enabled, but seeing I can't get into the OS I can't check. The bootloader was unlocked upon arrival.
I turned the phone off (volume up and down + power button)
Now, I also tried putting the phone into the charger, (it was still at 85%-ish as far as I can remember) however it doesn't seem to be charging. So I'm thinking there may be a hardware issue.
However, maybe a software solution... never know, so if anybody DOES know - highly appreciated
Thx
EDIT: so I've been fiddling around using some guides on this forum... nothing...
C:\Users\Ryan\Desktop\LEMAX2>fastboot devices
403077b2 fastboot
C:\Users\Ryan\Desktop\LEMAX2>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (787 KB)...
OKAY [ 0.048s]
writing 'aboot'...
OKAY [ 0.023s]
finished. total time: 0.079s
C:\Users\Ryan\Desktop\LEMAX2>fastboot oem unlock-go
...
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Users\Ryan\Desktop\LEMAX2>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.092s]
finished. total time: 0.094s
** NOTE --> this was always showing unlocked (even if not doing any of these steps).
C:\Users\Ryan\Desktop\LEMAX2>fastboot flash recovery twrp-3.1.0-0-x2.img
target reported max download size of 536870912 bytes
sending 'recovery' (59348 KB)...
OKAY [ 1.284s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 1.697s
Click to expand...
Click to collapse
This would normally allow me to boot into TWRP recovery. however it just takes me to the Stock Recovery (and does nothing - ie: there is no option to do anything).

Have you tried booting into TWRP instead of flashing it? Try "fastboot boot recovery twrp-3.1.0-0-x2.img"
EDIT: What recovery you are using?

Presterin said:
Have you tried booting into TWRP instead of flashing it? Try "fastboot boot recovery twrp-3.1.0-0-x2.img"
Click to expand...
Click to collapse
Yes, tried that as well. Afterwards I tried:
Fastboot reboot
And also just manually booting into Recovery straight from the Fastboot screen (volume up + power).
Both times it just takes me to the "standard" LeEco Recovery Screen (it just says LeEco, some Chinese text and "Recovery") and doesn't allow me to do anything.
Also, I tried multiple chargers, no sign of the phone being charged at all (no sounds, no on screen display, no LED).
So, basically all I can do is turn it on and watch it reboot over and over again, or go into Fastboot, do some commands (which all seem to do nothing - although I get an "OK" status) or go into the standard LeEco Recovery (even after flashing TWRP into Recovery).
I'm seriously starting to think this is just a Hardware malfunction. However, I've scoured the net and haven't really found a case like mine.

Are you trying to flash Le Max 2 recovery on Le Pro 3? I don't know if it should work, but I would try one from this forum meant for this phone. For example this: https://drive.google.com/file/d/0B7uXK7jfW17nZGRCWmFmZU9NVWs/view (link copied from official LineageOS13 thread)

Presterin said:
Are you trying to flash Le Max 2 recovery on Le Pro 3? I don't know if it should work, but I would try one from this forum meant for this phone. For example this: (link removed) (link copied from official LineageOS13 thread)
Click to expand...
Click to collapse
No. Actually my dad and girlfriend have the Le Max 2 and had to install a new ROM on one of them, hence the LEMAX2 directory (where I'm just centralizing the flash files).
Basically I just want the stock (China) rom for the X720 -as that seemed to be working perfectly for me... for now (well, not now.. but you know what I mean).

I would try clearing all the data from recovery. See if that gets it to "reset".
If that doesn't work you could see about getting a hold of an "update.zip", pushing it to the device and flashing it from the stock recovery to see if it gets it out of the loop.

slgooding said:
I would try clearing all the data from recovery. See if that gets it to "reset".
If that doesn't work you could see about getting a hold of an "update.zip", pushing it to the device and flashing it from the stock recovery to see if it gets it out of the loop.
Click to expand...
Click to collapse
thanks for the answer, would you mind pointing me in the direction of how to "clear the data from recovery"?
Also, I'm not sure if I tried, by ADB doesn't work in Fastboot (to push the zip). At the moment, even in stock recovery I can't do anything.
EDIT: so, home from work. I've had the phone OFF for about 12 hours now. Plugged it in to charger and now I get an LED. Boots up normally, but battery was at 0%. I have no idea what's going on or why it now works, or even why the battery is at 0% (it was at 85% or so when it "crashed" yesterday I believe). Is this a known issue by chance? Or does this seem like a one off type of thing?

Ryanx0r said:
No. Actually my dad and girlfriend have the Le Max 2 and had to install a new ROM on one of them, hence the LEMAX2 directory (where I'm just centralizing the flash files).
Basically I just want the stock (China) rom for the X720 -as that seemed to be working perfectly for me... for now (well, not now.. but you know what I mean).
Click to expand...
Click to collapse
Can't get over "x2" in recovery image file, it points to Le Max 2 recovery.

Ryanx0r said:
thanks for the answer, would you mind pointing me in the direction of how to "clear the data from recovery"?
Also, I'm not sure if I tried, by ADB doesn't work in Fastboot (to push the zip). At the moment, even in stock recovery I can't do anything.
EDIT: so, home from work. I've had the phone OFF for about 12 hours now. Plugged it in to charger and now I get an LED. Boots up normally, but battery was at 0%. I have no idea what's going on or why it now works, or even why the battery is at 0% (it was at 85% or so when it "crashed" yesterday I believe). Is this a known issue by chance? Or does this seem like a one off type of thing?
Click to expand...
Click to collapse
There are some odd issues with this phone and charging. I'm not sure why it would bootloop and then die, only to charge and boot up again finally. Consider yourself fortunate that it works now! I ordered an Anker charger off of amazon and now use that for quick charging instead of the stock charger just in case...

What is the solution for this?
Ryanx0r said:
Yes, tried that as well. Afterwards I tried:
Fastboot reboot
And also just manually booting into Recovery straight from the Fastboot screen (volume up + power).
Both times it just takes me to the "standard" LeEco Recovery Screen (it just says LeEco, some Chinese text and "Recovery") and doesn't allow me to do anything.
Also, I tried multiple chargers, no sign of the phone being charged at all (no sounds, no on screen display, no LED).
So, basically all I can do is turn it on and watch it reboot over and over again, or go into Fastboot, do some commands (which all seem to do nothing - although I get an "OK" status) or go into the standard LeEco Recovery (even after flashing TWRP into Recovery).
I'm seriously starting to think this is just a Hardware malfunction. However, I've scoured the net and haven't really found a case like mine.
Click to expand...
Click to collapse
Can you reply me as soon as possible the solution for the constant reboots.

shivaraju07 said:
Can you reply me as soon as possible the solution for the constant reboots.
Click to expand...
Click to collapse
No solution. It "died" again (and to think I only used it for about 2 days).
I got into contact with the seller on Ali Express, I was told to send it back so they could look into it.
But Ali Express paid me back (while the seller was still looking into the problem). I didn't 'really' want my money back, just wanted the phone and an explanation - however, once I was paid back, the RMA was stopped and I was told to place a new order. Trying to do so, resulted in the seller letting me know that they no longer make the LeEco Pro 3.
So... I just went for OnePlus 5 instead - great phone

Ryanx0r said:
however, once I was paid back, the RMA was stopped and I was told to place a new order. Trying to do so, resulted in the seller letting me know that they no longer make the LeEco Pro 3.
Click to expand...
Click to collapse
I've read that LeEco stopped making phones. What they sell are the remaining stock, that it.

ZeblodS said:
I've read that LeEco stopped making phones. What they sell are the remaining stock, that it.
Click to expand...
Click to collapse
It's a real shame, because they're actually really good phones. My girlfriend has one and is really happy with it. It's the LeMax 2, but still a nice piece of (cheap, but great quality) hardware.

I have leeco le s3. After update Google Play Services, my phone always restarted continuosly when using GPS. Is that same with your issue?

InitialDS said:
I have leeco le s3. After update Google Play Services, my phone always restarted continuosly when using GPS. Is that same with your issue?
Click to expand...
Click to collapse
Have you solved the problem?