Bricked Le S3 X626 after flashing TWRP, can't power on, PC won't recognize device

Search This thread
By:
Advanced…
M

marcof91

New member
May 12, 2018
3
1
elior126 said:
Thank you, but windows no longer recognize the phone. It says that the "USB DEVICE MALFUNCTIONED AND WINDOWS CANNOT RECOGNIZE IT".
If I connect the phone and press download nothing happens - strange.
Click to expand...
Click to collapse
marcof91 said:
Same issue as you.
And i think we don't have a solution for this because i have downloaded all necessary drivers and still the same problem.
The PC don't recognize the phone,gives error 43 in device manager.
I can put the phone in fastboot mode in itself but can't do anything with it.
Click to expand...
Click to collapse
OK,i finally got it!!! :laugh:
In fastboot mode,PC gives you a chime sound but nothing happens.
But if you open ADB command and type "fastboot devices" it shows your phone is connected.
The flash tool at this point was useless because it needs ADB connection but PC was not able to recognize the phone.
So what i did was pretty simple.
I copied the ALL the files inside the folder S3_X626/images (except the folder Mbin) to the folder LeEco_x620_SP_Rom.androidbrick.
It is 14 files around 3.30 GB.
Inside LeEco_x620_SP_Rom.androidbrick folder you see two bats (不清除数据刷机.bat) and (彻底清除数据刷机.bat).
Right click the first one and edit to see the code .
At the middle of the code you see something like this:
Code: 
fastboot flash preloader preloader_s2_plus.bin || call :FASTBOOTFAILED
	fastboot flash lk lk-verified.bin || call :FASTBOOTFAILED
	fastboot flash lk2 lk-verified.bin || call :FASTBOOTFAILED
	fastboot flash logo logo-verified.bin || call :FASTBOOTFAILED
	fastboot flash tee1 trustzone-verified.bin || call :FASTBOOTFAILED
	fastboot flash tee2 trustzone-verified.bin || call :FASTBOOTFAILED
	fastboot flash md1img md1rom-verified.img || call :FASTBOOTFAILED
	fastboot flash md1dsp md1dsp-verified.img || call :FASTBOOTFAILED
	fastboot flash md1arm7 md1arm7-verified.img || call :FASTBOOTFAILED
	fastboot flash md3img md3rom-verified.img || call :FASTBOOTFAILED
	fastboot flash scp1 tinysys-scp-verified.bin || call :FASTBOOTFAILED
	fastboot flash scp2 tinysys-scp-verified.bin || call :FASTBOOTFAILED
	fastboot flash boot boot-verified.img || call :FASTBOOTFAILED
	fastboot flash recovery recovery-verified.img || call :FASTBOOTFAILED
	fastboot flash cache cache.img || call :FASTBOOTFAILED
	fastboot flash system system.img || call :FASTBOOTFAILED
Those are files that you must replace and rename from X626 folder to X620.
Got it?
So,for example...in X626 folder you have the file md3rom.img ,you have to rename it to md3rom-verified.img and copy the file to X620 folder and replace the old one.
I think system and userdata files was not needed to rename but you must replace them anyway.
Now that you have renamed and replaced everything,put your phone in fastboot mode (vol down + power) and connect it to the PC then start the 不清除数据刷机.bat file
At the end of the operation it will ask to push any button to close.
Turn off the phone (long press power button) and turn it on normally.
And voilá it should be fixed. Mine got stuck for awhile at EUI screen (like 5 minutes) but then run like a charm. :cool:
 
Last edited:
  • Like
Reactions: marksklava
R

rashbaba

New member
Apr 29, 2015
2
0
marcof91 said:
OK,i finally got it!!! :laugh:
In fastboot mode,PC gives you a chime sound but nothing happens.
But if you open ADB command and type "fastboot devices" it shows your phone is connected.
The flash tool at this point was useless because it needs ADB connection but PC was not able to recognize the phone.
So what i did was pretty simple.
I copied the ALL the files inside the folder S3_X626/images (except the folder Mbin) to the folder LeEco_x620_SP_Rom.androidbrick.
It is 14 files around 3.30 GB.
Inside LeEco_x620_SP_Rom.androidbrick folder you see two bats (不清除数据刷机.bat) and (彻底清除数据刷机.bat).
Right click the first one and edit to see the code .
At the middle of the code you see something like this:
Code: 
fastboot flash preloader preloader_s2_plus.bin || call :FASTBOOTFAILED
	fastboot flash lk lk-verified.bin || call :FASTBOOTFAILED
	fastboot flash lk2 lk-verified.bin || call :FASTBOOTFAILED
	fastboot flash logo logo-verified.bin || call :FASTBOOTFAILED
	fastboot flash tee1 trustzone-verified.bin || call :FASTBOOTFAILED
	fastboot flash tee2 trustzone-verified.bin || call :FASTBOOTFAILED
	fastboot flash md1img md1rom-verified.img || call :FASTBOOTFAILED
	fastboot flash md1dsp md1dsp-verified.img || call :FASTBOOTFAILED
	fastboot flash md1arm7 md1arm7-verified.img || call :FASTBOOTFAILED
	fastboot flash md3img md3rom-verified.img || call :FASTBOOTFAILED
	fastboot flash scp1 tinysys-scp-verified.bin || call :FASTBOOTFAILED
	fastboot flash scp2 tinysys-scp-verified.bin || call :FASTBOOTFAILED
	fastboot flash boot boot-verified.img || call :FASTBOOTFAILED
	fastboot flash recovery recovery-verified.img || call :FASTBOOTFAILED
	fastboot flash cache cache.img || call :FASTBOOTFAILED
	fastboot flash system system.img || call :FASTBOOTFAILED
Those are files that you must replace and rename from X626 folder to X620.
Got it?
So,for example...in X626 folder you have the file md3rom.img ,you have to rename it to md3rom-verified.img and copy the file to X620 folder and replace the old one.
I think system and userdata files was not needed to rename but you must replace them anyway.
Now that you have renamed and replaced everything,put your phone in fastboot mode (vol down + power) and connect it to the PC then start the 不清除数据刷机.bat file
At the end of the operation it will ask to push any button to close.
Turn off the phone (long press power button) and turn it on normally.
And voilá it should be fixed. Mine got stuck for awhile at EUI screen (like 5 minutes) but then run like a charm. :cool:
Click to expand...
Click to collapse

i need an expert opinion on this .i bricked my brand new le s3 x626 when i was trying to flash the update and before then i have Not enable usb debung and oem unlock.now i have followed the (https://xdaforums.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937) guide to unbrick the phone and is now in mirrored stage.The phone is mirrored and will not boot to screen.
i am unable to complete the last part which is Part 5 - Running .bat files in S3 X626 folder as i keep getting error "unlocking operation not allow"
it has been 5 month now.i have tried everything i know and it seems now that am losing hope of reviving the phone. will appreciate if i can get help.
 
P

Pcpete69

New member
May 23, 2018
4
0
My problem is I am fastboot locked. What can I do??? Can not get into phone and enable debugging, its stuck at logo screen. Please help!!
 
P

Pcpete69

New member
May 23, 2018
4
0
Still playing with phone, now I'm in a boot loop. Loops between logo screen with two lines of chinese writing and then logo screen with one line of Chinese. Any suggestions?
 
M

marcof91

New member
May 12, 2018
3
1
Guys just do what i did in the post above.
I had all those problems you guys mentioned and after that it worked.
 
A

AvirRahul

New member
May 28, 2018
1
0
This is the same problem in my LeEco Le S3 X626, Please help me....

Your post link:- https:/xdaforums.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
 
H

homeer

New member
May 30, 2018
2
1
My solution!

1 To achieve stable connection, I used the SP Tool of this link (follow the steps of the SP Tool of the link)
https://xdaforums.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
I did not have to tamper with the signature inhibitor or the drivers. My LeEco x626 installed 3 drivers automatically on my computer.
** When the download procedure is performed, the program selects the driver in which there is a connection. **
However, only my "Preloader" file was filled with "location".
I clicked download, and managed to make the phone be recognized by the same port, even connecting and disconnecting.

2 Then I followed this link
https://xdaforums.com/le-2/help/brick-restoration-flashtool-s28-x620-t3754590

*And I followed the video tutorial.
* I caught the part where the "system" file was downloaded. It was not possible, it was a mistake.

3 Then I came to a light, on my own, like this:

* In my case, that the phone had no stable connection, via usb, I did the procedure below:

Download each item at a time (holding "Vol +" + Power, before clicking download, so the usb recognizes the device)
*
*** Keep the buttons pressed until the yellow bar reaches 100%. ***

I did in "Boot", "Recovery" and other items in the list.
(I could not pass all at once, nor the file "system", as stated above)


But to my surprise, the phone tried an initialization, in vain of course.
And after this procedure, it is possible to access the fastboot ("Vol-" + "Power").

4 I tried to restore via this link:
https://xdaforums.com/android/help/guide-leeco-le-s3-x626-x622-unbrick-t3705542
In vain again.

5 However, this content of "Orange State Remove" was exceptional.

-> Orange State remove

- Power off the phone
- "Power" & "Vol-"
- Go to unpacked "platform-tools" folder
- Shift + RMB & Open PowerShell console
- Type "fastboot oem lock"
Wait.
- Type "fastboot reboot"
- Before next flashing u need to unlock flow using "fastboot oem unlock" ---- >>> This allows you to flash in fastboot.

6 I did this procedure above and then tried to flash individual files.
(See below)
7 At this link, (https://xdaforums.com/showthread.php?t=2131284)
I used the fastboot commands:

-Now you are ready to flash your files. Starting with your recovery.img file and then followed by your boot.img kernels
*- In your command window type the following commands

** to flash you will need to type **
fastboot flash recovery recovery.img

** To flash your kernels boot.img you need to type **

fastboot flash boot boot.img

8 After this procedure, I put the boot, recovery and system.img files inside the "platform-tools" folder.

I made the flash of the 3 using
"fastboot flash recovery recovery.img"
"fastboot flash boot boot.img"
"fastboot flash system.img" ----> In this option, an error was encountered.

9 At last, very tired, I thought of putting a twrp, via fastboot.

From this link, I promise it will be the last link rs

https://xdaforums.com/le-2/development/x626-cuoco92-installed-multilingual-t3744201

I downloaded TWRP 3.1.1-0 (CUOCO92), and replaced the "recovery" file in the "platform-tools" folder.

I made the flash (always using "fastboot oem unlock" before)
-fastboot flash recovery recovery.img

I went to my phone, and pressed the "Power" button, to exit the fastboot mode. And then I pressed ("Vol +" + "Power")

I pressed for startup, and after about 20 seconds the screen blinked, and the twrp flipped open.

I kept the phone connected via usb, and I sent the official rom, for my storage (it was possible after the twrp)
I downloaded the rom from the same link, version 8.4 Stable.
I put in storage, opened the twrp, wiped cache, dalvik and date.

I rebooted, and re-entered the twrp (holding 20 seconds the buttons), and did the installation.

Anyway, my little son is reborn. After 10 minutes of installation, it worked.
So far, no problem.

Never lose hope, young men. After two days, it was !!!
Thanks to all of XDA, and all users of the links I put here.
My intention is to help, so I apologize if my tutorial was of poor understanding.
Hug from Brazil!
:D
 
  • Like
Reactions: Bobfish
A

Antrophin3

Member
May 10, 2016
5
0
Xiaomi Poco F1
Xiaomi Mi 10T / 10T Pro
Thanks dude

Thanks for explaining your troubles to us.

The moment i bought this unlucky (for me) phone i had random freezes/reboots. After many months trying different roms (either updates or fastboot Stock EUI Roms) none worked so i gave up.

Recently I have tried again, and for some unknown reason to me, the fastboot oem unlock and after -reboot option "killed" of the phone...

It went into red led state... Thanks to tickernel and you i managed to recover the damn phone... I'm at the moment of flashing that 020s fastboot rom...

It has now finished... I'm at the normal boot logo screen, waiting for it to boot up- :)

Edit: Stuck at boot logo, tried multiple reboots, the letters under the LeEco logo become red after some time, and just now it turned off on it's own (was overheating while trying to boot up).

Anyone had the same problem?

Now i connected it to the charger. I hope the battery hit 0%... Will try again after i have some sleep....
 
Last edited:
Punkerstein

Punkerstein

New member
Mar 26, 2010
2
0
Leskovac
Le S3 x626 - upside,down - alice in wonderland

First of all thanks for the great ''how to '' I followed procedure and manage to bring back to life my Leeco s3 x626 but when i booted it it turns OS like upside down and all os is like turned from left to right if you want to read something you must read it from right to left ??? Can you give me some advice how to correct this? :p Thanks in advance
 
D

Dudeonyx

Senior Member
Nov 17, 2014
74
21
Try rooting your phone or flashing a custom kernel, either option should get rid of dm-verify which is probably what is preventing complete booting.

Note: dm-verify prevents booting if system partition has been modified
 
A

Antrophin3

Member
May 10, 2016
5
0
Xiaomi Poco F1
Xiaomi Mi 10T / 10T Pro
Antrophin3 said:
Thanks for explaining your troubles to us.

The moment i bought this unlucky (for me) phone i had random freezes/reboots. After many months trying different roms (either updates or fastboot Stock EUI Roms) none worked so i gave up.

Recently I have tried again, and for some unknown reason to me, the fastboot oem unlock and after -reboot option "killed" of the phone...

It went into red led state... Thanks to tickernel and you i managed to recover the damn phone... I'm at the moment of flashing that 020s fastboot rom...

It has now finished... I'm at the normal boot logo screen, waiting for it to boot up- :)

Edit: Stuck at boot logo, tried multiple reboots, the letters under the LeEco logo become red after some time, and just now it turned off on it's own (was overheating while trying to boot up).

Anyone had the same problem?

Now i connected it to the charger. I hope the battery hit 0%... Will try again after i have some sleep....
Click to expand...
Click to collapse

Sorry for taking sometime to respond.
It didn't want to boot at all after trying many times with flashing the fastboot X626.zip ROM... I gave up, installed the TWRP 3.1.1.0 and latest MIUI from tickernel.org.

It works much better than the Stock EUI 5.8.0.18s (from GeeekBuying) or any other ROM (020s, 023s, 026s), but there are still reboots (i noticed it reboots much more when the battery is between 75 and 100%, than when it is below 75%). So it might be some MTK Helio x20 hardware bug (or kernel bug) related to managing battery life...
 
R

rdlegy

Senior Member
Dec 3, 2013
542
60
joebah said:
Okay, so I downloaded all three files "Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip", "x620_flash_tool_androidbrick.7z" and "unbrick_tool_x626.zip" and extracted them. I tried the "How to fix le x626 undetected" step first given that none of this will work if the USB connection is not stable...

The problem is that because my PC keeps connecting and disconnecting from the X626, it's impossible to update my PC device driver as the instruction suggests. However, I noticed that under the Port section of device manager, each time the X626 tries to reconnect to the PC, the name of the driver changes. It cycles from "MediaTek Preloader USB VCOM (Android) (COM3)" to "MediaTek USB Port (COM4)" in an endless loop. It's almost like the phone can't make up its mind about which driver to use. I am wondering if my earlier failed attempt to flash TWRP onto the x626 had caused this issue (along with bricking my phone)?

If anyone knows how to fix this problem please let me know. I'm fairly convinced that once the PC is able to connect, the unbricking process should be fairly straightforward!
Click to expand...
Click to collapse

I have managed to unbrick my leeco x626 using this guide. I am very thankful for the help. The problem now is that I am with the rescue rom and I want to install other rom like cuoco. I also don't have imei and baseband.I have lost my box and don't know the phones imei. Can you help me recover my imei(it could be different imei than my phone, I don't mind if it works) and install another rom. Thanks!
 
Last edited:
  • Like
Reactions: Mudiis
D

dreamer_X

Member
Jun 25, 2018
7
0
I may be in a boot loop.

Johndays01 said:
Thank you, this Flash Tool recognize my phone and starts flashing, but the device gets connected and disconnected in an endless loop...
Click to expand...
Click to collapse


I may be in a boot loop.

y phone is LeEco le 2 X620.


1. Enable developer mode on the main unit and unlock OEM.
2. Unlock the boot loader via fastboot.
3. Boot the TWRP like a Qualcom device.

> fastboot boot rrecovery.img

When I started TWRP, I mistook the file name for "rr", so the screen got dark and I could not start it.
Even if you press power and volume + or power and volume - at the same time, the screen is black.

Connecting to the PC will update the device repeatedly and the device will be lost before the le 2 driver insalling.

Even if the power button is pressed and connected to the PC after 15 seconds,
Even if you connect the power supply and volume + simultaneously to the PC,
Even if you press the power supply and volume - simultaneously to connect to the PC,
Le 2 does the same thing.

I can not turn off the power and can not enter other modes. (I also tried to press power for 30 seconds)
Connecting the PC in this state will result in the above operation.
Please let me know if you know how to stop the boot loop or how to fix it so that it enters fastboot.

You can get red light when connected with a PC.
 
A

antonio solis

New member
Jul 2, 2018
1
0
Imei fix solved lex626

i can fix the imei on a leeco lex626 with a mtk6797 using MauiMETA_v9.1635.23 and enable composite kernel USB port (for adb) and press vol - while boot in leeco logo (not in fastboot mode) and then the com port it's open and I JUST follow the steps on a xiaomis IMEI FIX video, and i found a twrp that works on the phone, thank you bro your answer was so helpful
 
M

mimossmart2

Member
Oct 17, 2010
5
1
antonio solis said:
i can fix the imei on a leeco lex626 with a mtk6797 using MauiMETA_v9.1635.23 and enable composite kernel USB port (for adb) and press vol - while boot in leeco logo (not in fastboot mode) and then the com port it's open and I JUST follow the steps on a xiaomis IMEI FIX video, and i found a twrp that works on the phone, thank you bro your answer was so helpful
Click to expand...
Click to collapse

Hi. How you manage to fix imei on your phone? Can you share what you do to fix the problem?
 
Last edited:
R

rashbaba

New member
Apr 29, 2015
2
0
Dudeonyx said:
Try rooting your phone or flashing a custom kernel, either option should get rid of dm-verify which is probably what is preventing complete booting.

Note: dm-verify prevents booting if system partition has been modified
Click to expand...
Click to collapse


can you be more specific pls.
the issue is, the phone is turned upside down (mirror) after using the guide to un brick and it continue to reboot.it wont boot to screen.
 
Last edited:
A

Apster21

New member
Mar 14, 2009
4
0
I have an issue which I can not fix on my own, so I'm kindly asking you guys for help.

It's a fully bricked phone, not able to turn it on. Only got the red flash light, while plugged.
It kept reconnecting, as described in the guide, I set the drivers on both COM ports. This way I saw 2 MediaTek DA USB VCOM Port (COM3).
I made sure i have the Flash Tool set up right and tried to run it, but it kept failing with BROM ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003).
So I've tried to download each element one by one, starting with the preloader. I've unchecked the others, unpluged the phone, held power+vol-, plugged it back in, hit Download and it worked.

Since that the phone is recognized differently on my PC and I'm not able to download the other elements.
Now it's switching between one of the COM3 ports and a new Unknown USB Device (Device Descriptor Request Failed). I can not select any of the MediaTek drivers for this USB device now.
Trying to download other elements, or all of them at once (except for recovery and boot) doesn't work, as I'm getting the same BROM error. I've tried holding volume buttons for the entire process etc., but nothing worked - it keeps switching between the COM and USB device and can not complete a download.

img_57fdba4d6e9aa.jpg


What would you guys suggest trying/doing?
Thanks in advance!
 
Last edited:
M

marksklava

Member
Jan 1, 2018
13
0
Apster21 said:
I have an issue which I can not fix on my own, so I'm kindly asking you guys for help.

It's a fully bricked phone, not able to turn it on. Only got the red flash light, while plugged.
It kept reconnecting, as described in the guide, I set the drivers on both COM ports. This way I saw 2 MediaTek DA USB VCOM Port (COM3).
I made sure i have the Flash Tool set up right and tried to run it, but it kept failing with BROM ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003).
So I've tried to download each element one by one, starting with the preloader. I've unchecked the others, unpluged the phone, held power+vol-, plugged it back in, hit Download and it worked.

Since that the phone is recognized differently on my PC and I'm not able to download the other elements.
Now it's switching between one of the COM3 ports and a new Unknown USB Device (Device Descriptor Request Failed). I can not select any of the MediaTek drivers for this USB device now.
Trying to download other elements, or all of them at once (except for recovery and boot) doesn't work, as I'm getting the same BROM error. I've tried holding volume buttons for the entire process etc., but nothing worked - it keeps switching between the COM and USB device and can not complete a download.

img_57fdba4d6e9aa.jpg


What would you guys suggest trying/doing?
Thanks in advance!
Click to expand...
Click to collapse

I am having the same issue right now, haven't been able to figure this out for about 5 months at this point.
 
S

syahz15

New member
Dec 20, 2014
2
0
kuala lumpur
luckyrai said:
Having Same Issue Bricked X626

First of all Thanks for your time to make this guide,Good Job, Lets now talk about problem i faced and solutions (Worked 4 days)

Things i deserve
1.No Need to change Ports Assignment (its optional)
2.Preloader Driver Works Great
3.Main Thing- If Flash tool crashes like mine did, Just Select MT6797_Android_scatter from LeEco_x620_SP_Rom.androidbrick Folder this will fix flash tool crash

If Custom OS installed already before bricking, after Unbrick your device is mirrored, if you did not enable OEM Unlock,刷机.bat will not work and gives error, Just Boot the device to system (Takes bit long) and enable OEM Unlock,
And if all things goes Good, Finally Unbrick And Stock Le ROM
Thanks
Click to expand...
Click to collapse

Hey. i did enable oem unlock but still it gives me error man. do i have to enable usb debugging also?
 
You must log in or register to reply here.

Similar threads

M
Letv LeEco s3 x626 root/roms
Replies
26
Views
41K
laikexpert
laikexpert
Kychera22
Brick Restoration | Flashtool | S28 | x620-x626 | Unbrick
Replies
75
Views
28K
thatRoland
thatRoland
K
[ROM] [MIUI 10] [BETA] MIUI 10 for Le 2/S3 [+UPDATING]
Replies
19
Views
26K
K
kaakaa2006
K
[ROM] [MIUI 10] [8.7.23] MIUI 10 for Le 2 - S3 = Info in YT
Replies
29
Views
26K
S
Santhosh suddala
S
Unable to Enable MTP in TWRP Recovery .
Replies
12
Views
31K
D
divyashakti

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 10
    J
    joebah
    Hi - I'm not sure if I am having the same problem as b1gb1ng has - but I'll describe what I am experiencing as best as I can...

    After using my Le S3 X626 for a week with no problems at all, I decided to install TWRP. So the first thing I did was follow the instruction on this website getdroidtips.com to unlock the bootloader via my Windows 10 64bit PC with the ADB.exe and fastboot.exe tool. I followed all the instructions carefully, my batteries were well above 80%, and I got to the part where I issued the command "fastboot reboot" on my Dos prompt. The phone rebooted and everything seemed perfectly normal. So far, so good... The next thing I did was used the same ADB.exe and fastboot.exe tool to flash a TWRP file that I downloaded from another website. I issued the command: "fastboot flash recovery twrp.img" and THAT'S when the problem began - the screen of my le S3 x626 just went pitch black this time around instead of showing the Chinese characters!

    I disconnected my Le S3 x626 from my PC, tried turning the phone's power on (no response), tried holding the Vol+ and/or Vol- buttons and the power button (no response). The phone was completely unresponsive. No light came on at all. I connected my Le S3 x626 back to the PC's USB port, and the red light on the phone came on (as if it's charging) but my PC kept connecting and disconnecting to the Le S3 x626 over and over again (before this incident, the PC would recognize my Le S3 X626 right after I connect to USB port). I tried to reboot the bootloader again via Dos Prompt - but instead I get the error message "error: device '(null)' not found. Which I guess makes sense because my PC was no longer able to connect to the Le S3 x626 anymore...

    << 1st EDIT - Dec 26 2017>>
    <<2nd EDIT - Jan 5 2018>>
    <<3rd EDIT - Jan 11 2018>>
    <<4th EDIT - Jan 27 2018>>
    <<5th EDIT - Jan 30 2018>>

    So after more than a month of tinkering with the phone, I was able to unbrick the phone. It seems like a lot people are able to solve in one or two days so my slow progress was likely due to a combination of 1) there being many different version of the solution on the web which confuses more than helps and 2) my inability to follow instructions properly and 3) not having a lot of time on my hand. Anyway, I have summarized my experience in solving this problem as well all the errors due to my screwing up the process - so hopefully this will be a useful guide for everyone who bricked their X626!

    Which solution to use
    ---------------------------
    The solution that worked for me was based on advice from alberto-a-l and Catani who pointed me to http://tickernel.org/how-to-unbrick-le-x626-red-light/ which apparently was taken from an article written by os_man... So I guess thanks to all three of you???

    What we're all about to accomplish
    --------------------------------------------

    In case you're interested in the technical details of what we're about to do, here's the quick low down: according to kanewilliam, the Tickernel website solution tells us that we need to first flash the le eco x620 firmware as well as boot and recovery into our bricked x626 phone, and for that we need to download a bunch of files from various websites. Once we have all the necessary files and we have successfully flashed the x620 firmware/boot/recovery via spflash tools, the phone will successfully boot but the screen will be mirrored making it unusable. However, that's okay, because after that we can then boot the mirrored phone in fastboot mode, relock the bootloader, and then flash the phone with a new ROM via dos commands, and after that we will have the phone back up and working again (albeit all the original info would have been deleted). Big thanks to kanewilliam for clarifying the big picture for us!

    Part 1 - setting up
    ---------------------
    First you need to download and unzip four files/folders - "LeEco_x620_SP_Rom.androidbrick", "x620_flash_tool_androidbrick", "Windows+10_MTK+VCOM+USB+Preloader+Drivers" and "乐视S3_X626". You need all of them for this solution to work. The links are on http://tickernel.org/how-to-unbrick-le-x626-red-light/ page. These files are like 2.3GB combined and you need to click all sorts of ad stuff to download so this will take a while...

    Since a lot of people had problems downloading the files from the tickernel website - I've included the steps on what you need to do to get the files downloaded. There are two ways of doing this:

    Method A - via Tickernel links
    ========================

    1. Firstly, you need to find the link first! You could navigate through the website by clicking on the word "steps" which will then take you to a second page where you have to scroll all the way to bottom, or you can just use these links that I copied from the page:

    Download :*
    Firmware for unbrick:*http://idsly.com/0dN
    SP Flash Tool :*http://idsly.com/Xfppfu
    Driver :*http://idsly.com/d3t5

    Download without ads:
    Firmware for unbrick:*https://cnhv.co/teyy
    SP Flash Tool:*https://cnhv.co/tezc
    Driver:*https://cnhv.co/tf1i

    2. Pick either with ads or without ads. If you choose download without ads, they will make you do some mining for them first (proof of work) and once done they'll let you download. If you choose download with ads, there won't be any mining (apparently) but you have to view a few ads before they let you download
    3. If you choose with ads (which was what I did), you will first be taken to the IDSLY page where you need to do some fun ad clicking activities. First, scroll down slightly and click on the green "visit link" button once, and tell your browser to allow pop up if prompted.
    4. A new page will open up along with an ad pop up. The new page will say "your link is almost ready"... yeah right! You can close the pop up but DO NOT close the new page. Now scroll down the “your link is almost ready" page and click the blue "get link" button.
    5. More pop-up windows show up, and some of them have the potential to be NSFW (not safe for work) so be sure to do this at home! You can close the pop-up windows but don't ever close the main page or you'll have to start all over again! However, you may be taken back to the original IDSLY page that you were directed to in (3). Don't be disheartened, this is normal... they like to mess with you!
    6. Repeat the steps 3-5 again, and again, and again. By the third or fourth time it'll no longer loop you back to the IDSLY page and you'll just be stuck with "your link is almost ready" page instead. This is a good sign. Keep clicking on the blue "Get Link button" and close all the virusy pop ups as they show up.
    7. After may be a few more times of clicking blue "Get Link" button and closing a dozen virusy pop up ads, you'll finally get the browser prompt (legit this time) asking you to download the file - "What do you want to do with .LeEco_x620_SP_Rom.androidbrick.7z". Click “save” to download the file and now you're done with one file!
    8. Now do the same for the other two files... yeah, this process takes a while!

    Method B - Gizmodo links & mediafire
    ==============================

    Based on the responses I got in this thread, there are some people who don't like method A as you need to 1) go through a ton of clicking just to get to the final download URL for each file, and 2) along the way there are lot of those spam/adware sites that pop up on your browser. Personally I think these pop ups are pretty harmless as long as you don't download or install anything outside of the zip files you need (like flashplayerx.exe!), but understandably some people don't want to deal with the hassle. Thankfully, adaa1262 has informed us that you can get most of the files from gizmodo at https://www.gizmochina.com/2016/12/20/leeco-le-2-x620-x620-pro-x625-pro-rescue-guide-video/, although you may have to follow their instructions since their file naming convention is different from the Tickernel files that I downloaded and used.

    Regardless, you would still need to get the S3_X626 file which gizmodo doesn't seem to provide a link to. If you want to bypass the tickernel link method, here's the direct mediafire link for S3_X626:

    http://www.mediafire.com/file/cmkqb7...h7/S3_X626.rar

    Note - apparently the author of the Tickernel website changed the URL, probably because too many people were getting the file directly instead of going through the advertising loop.... or either that mediafire has a policy of randomizing the URL labels.... So anyway it looks like the only way to get the S3_X626.rar file is via the Tickernel website for now, unless someone is generous enough to host it on an ad free server!

    Note that when unzipping 乐视S3_X626.rar, I got a bunch of warnings from Windows Defender about virus/Trojans etc. - so just ignore them.



    Part 2.1 Installing the MediaTek drivers
    ---------------------------------------------
    First you need to get Windows into unsigned mode. The instruction below is fairly straightforward and taken from Dell website.

    1. Click the Start menu and select Settings.
    2. Click Update and Security.
    3. Click on Recovery.
    4. Click Restart now under Advanced Startup.
    5. Click Troubleshoot.
    6. Click Advanced options.
    7. Click Startup Settings.
    8. Click on Restart.
    9. On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.

    Once you've disabled signed driver enforcement, you can try to restore the drivers - so here are the next steps:

    10) If you haven't done so, go to device manager and connect the x626 to the PC's USB
    11) Sometimes, you have to wait for a minute or two for the PC to recognize the phone. If this doesn't work, unplug, try holding the power button and Vol - for 15 seconds then let go, it 'wakes' up the phone somehow, then connect it back in. You might need to do this a few times.
    12) If you get it to work, it will try to install a generic USB driver. Wait for the generic USB driver to show up under "Ports (COM & LPT)" (along with the USB connect chime sound), then click on "update driver"
    13) Select "browse my computer for driver software"
    14) Select "Let me pick from a list of available drivers on my computer"
    15) Select "Have Disk..."
    16) Select "Browse", then find the Windows+10_MTK+VCOM+USB+Preloader+Drivers inf file that you saved earlier and click on the appropriate version (x64 for me)
    17) Now you will have the option to replace the generic driver with the new drivers. I personally selected "MediaTek DA USB VCOM" driver.

    Note that luckyrai had success with the preloader driver instead of the DA USB VCOM driver. So you could try those drivers instead if you're stuck later on

    Part 2.2 fixing USB connect and disconnect
    ----------------------------------------------------
    This was the most difficult part for me (and I guess a lot of people) - but here's how I resolved it:

    Note that both luckyrai and blueasteroid stated that steps 1-5 below is not be necessary in their experience

    1) After the MTK driver installation is completed, take out the phone
    2) Keeping the device manager windows opened, plug the phone back in again
    3) After this, disconnect the x626 from the PC's USB port and reconnect again. The PC will most likely try to switch to another COM Port and reinstall another generic USB driver. If it does that, repeat step 5 and overwrite the new generic driver and COM port with the MediaTek DA USB VCOM driver . Keep doing this until you end up with a situation where you have the PC cycling between 2-3 COM ports in the connect/disconnect loop but at least they will be showing MediaTek DA USB VCOM every time.
    4) Now reassign all these COM ports (right click, properties, Port setting, advanced) to a single designated port (like, say "3").
    5) If you follow this instruction, the phone will still connect and disconnect from the USB, but each time it does so the phone will always connect to the same COM port and using the same driver - this will make it easier to flash though success is not guaranteed every time

    Part 3 - SP Flash Tool
    ---------------------------
    This part is supposed to be easy but I screwed this one royally by not following instructions and ended up wasting a lot of time.

    1) The first thing you are supposed to do is open one of the downloaded folders "x620_flash_tool_androidbrick", then double click on flash_tool.exe to open the SP Flash Tool.
    2) press Ctl Al S and it will expand the fields to include Authentication File .
    3) fill each fields like this by navigating to each specific file in each specific folders:

    Download Agent : \..\..\x620_flash_tool_androidbrick\secureboot\DA_ BL_HIGH.bin
    Scatter-Loading File: \..\..\LeEco_x620_SP_Rom.androidbrick\MT6797_Andro id_scatter.txt
    Authentication File: \..\..\x620_flash_tool_androidbrick\secureboot\aut h_sv5_letv.auth

    Note the "Certification File" field you leave blank.

    Now it is paramount that you select the EXACT file in the EXACT folder. If you did this right, then the download rows should be populated and the tick boxes all ticked, and the "location" column is filled up with the location of all the .bin files. If you did not follow the instruction properly (like I did), what ends up happening is even though the "Name" column is filled up, the Location column will be mostly empty and the tick boxes unticked except "preloader" row and this will give you errors later on when you try to download (more on that in a bit)

    4) Untick recovery (second row) and boot (eleventh row).
    5) Then plug in the X626. At first I held down the Vol - button but it turned out that if you did this right, you don't need to press any button at all! When the USB connect sound chimes immediately click "Download". If you did this wrong, you will get the error message “BROM ERROR : S_COM_PORT_OPEN_FAIL (0x3F5)". In that case, unplug phone, hold down power and Vol - button for 15 seconds, then try again. If you did it right, it will start to flash.

    Note that blueasteriod confirmed that holding the Vol - button the entire time is absolutely necessary for him as it somehow ensures that the device stays connected despite the COM port switching issue, so basically the same opinion as alberto-a-l and Catani, so I guess you can try the Vol - button option if the flashing continues to fail

    6) However, depending on whether you did step (3) right, the flashing process could die within 10 seconds and give you the error "BROM ERROR: STATUS_OPEN_FILE_ERR (0xC001000E)". If you see this error then you screwed up step 3 (like I did many times) - go back and make sure you selected the right file I the right folder and the relevant boxes are ticked.
    7) If you did step 3 right, then the SP Flash Tool window would go from red (Downloading DA 100%) to purple (Download Bootloader 100%), then goes to yellow as it download each of the .bin files to the phone. The process could take about 10 mins. Again, at first I thought you need to hold down the Vol - button but turned out if you did it right you won't need to.
    8) So that's the hard part. Now the easy part - press Control Alt V, go to "Window" in the menu bar of SP Flash Tool and click on "Write Memory". The write memory tab will magically appear next to memory test tab. Again, you need do exactly as the instruction says - select boot-verified.img in the downloaded folder LeEco_x620_SP_Rom.androidbrick, and type "0xf900000" on the Begin Address field. Connect the X626 to USB but this time hold the Vol - button while doing so. Click "Write Memory" and the writing should work (Green okay sign). If you didn't do this right, you will get a slightly different error (something like VFY_FAIL).
    9) Repeat the process but choose recovery_stock_works _after_brick.img in the folder LeEco_x620_SP_Rom.androidbrick for the file path, and change the Begin Address field to 0x8000. Again, connect the phone and hold down Vol +, and click "Write Memory"

    Now, I skipped the DA_BR.bin part although it didn't seem to cause a problem. Anyway, I tried to power on my phone - initially and the red light started flashing and the battery icon appears on the screen - which means I need to charge my phone first since the battery has been depleted after a month of trying to fix the phone. So I charged it up for 20 mins, tried again and this time the phone booted! However, the screen will like its mirrored (just like the instructions said), and you won't be able to do much but at least I was able to boot into the home screen. Yay!

    Part 5 - Running .bat files in S3 X626 folders
    ----------------------------------------------------

    1) Boot the phone in fastboot mode per instruction (Vol -, Power), and the familiar black screen with Chinese characters showed up on the phone. Plug in the phone back into USB. By now the PC fully recognizes the X626! So no more annoying connect/disconnect problem.
    2) Run the file 开机oem解锁-音量下+开机键_读取Devices.bat. The Dos prompt would then show that is doing a bunch of stuff (I guess it's unlocking the bootloader?) and then a text file "Devices.txt" is generated in the folder..
    3) Run the file 刷机.bat. You will get an error on the dos prompt. So what you need to do is change the folder name from "乐视S3_X626" to "S3_X626" by removing all the Chinese characters. Run the file again and the dos prompt will through some sort of flashing process which will take about 10 mins.
    4) Unplugged the phone and hold down the power button for a while to reboot. You may need to do this several times as I found that I was stuck in the bootloader screen.
    5) Now the phone would reboot normally and the "EUI" logo showed up. What happened to me was it froze. So I rebooted the phone again, and this time the EUI logo showed up and it started to initialize all the default apps (I think 15 of them). That took about 10 mins. So be sure that your battery is fully charged when you do this!
    6) You are then taken to the setup screen, put in the Sim Card and connect to Wifi - skipped the finger print set up stuff and you will be back to the home screen.
    7) You'll note that EUI is version 5.9.020S (I was on 5.8 earlier), with baseband, IMEI and everything all in place.
    View
    2
    Kychera22
    Kychera22
    Stephinnoye said:
    Please help me ooo, this is the 3rd week my phone has gone black.
    Here is my spft erro
    BROM ERROR:STATUS DEVICE CTRL EXCEPTION (0xC00500001)
    Pls wat next to do?
    Thanks in advance



    I jst got the error when i hold down d vol- and connect phone to pc and immediately press d download button
    New error=> BROM ERROR:STATUS BROM CMD DA FAIL (0xC0060003)

    But i hardly get this error when i retry
    Click to expand...
    Click to collapse

    Press and hold the power button for 10-20 seconds. the phone may not be completely turned off.
    Which download agent are you using?

    If DA_BR, then before connecting the cable, hold the Vol + and hold.
    If DA_PL, connect without the clipped buttons.
    error 0xC0060003, just occurs if the button is not pressed, or vice versa. it depends on the agent.
    View
    1
    A
    alberto-a-l
    joebah said:
    Hi - I'm not sure if I am having the same problem as b1gb1ng has - but I'll describe what I am experiencing as best as I can...

    After using my Le S3 X626 for a week with no problems at all, I decided to install TWRP.

    So the first thing I did was follow the instruction on this website getdroidtips.com to unlock the bootloader via my Windows 10 64bit PC with the ADB.exe and fastboot.exe tool. I followed all the instructions carefully, my batteries were well above 80%, and I got to the part where I issued the command "fastboot reboot" on my Dos prompt. The phone rebooted and everything seemed perfectly normal. So far so good...

    The next thing I did was used the same ADB.exe and fastboot.exe tool to flash a TWRP file that I downloaded from another website. I issued the command: "fastboot flash recovery twrp.img" and THAT'S when the problem began - the screen of my le S3 x626 just went pitch black this time around instead of showing the Chinese characters!

    I disconnected my Le S3 x626 from my PC, tried turning the phone's power on (no response), tried holding the Vol+ and/or Vol- buttons and the power button (no response). The phone was completely unresponsive. No light came on at all.

    I connected my Le S3 x626 back to the PC's USB port, and the red light on the phone came on (as if it's charging) but my PC kept connecting and disconnecting to the Le S3 x626 over and over again (before this incident, the PC would recognize my Le S3 X626 right after I connect to USB port).

    I tried to reboot the bootloader again via Dos Prompt - but instead I get the error message "error: device '(null)' not found. Which I guess makes sense because my PC was no longer able to connect to the Le S3 x626 anymore...

    I am the end of my wits at this point, and really wish I hadn't mucked around with my phone :crying:... is there anyway I can recover my Le S3 X626 back to stock ROM? Thank you very much!
    Click to expand...
    Click to collapse

    250/5000
    Hello, the same thing happened to me. Try using the manual on the following page ]ht tp://tickernel.org/how-to-unbrick-le-x626-red-light/ but the flashtool does not detect the terminal when trying to click on download does nothing. I do not know what to do...
    View
    1
    Catani
    Catani
    joebah said:
    Okay, so I downloaded all three files "Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip", "x620_flash_tool_androidbrick.7z" and "unbrick_tool_x626.zip" and extracted them. I tried the "How to fix le x626 undetected" step first given that none of this will work if the USB connection is not stable...

    The problem is that because my PC keeps connecting and disconnecting from the X626, it's impossible to update my PC device driver as the instruction suggests. However, I noticed that under the Port section of device manager, each time the X626 tries to reconnect to the PC, the name of the driver changes. It cycles from "MediaTek Preloader USB VCOM (Android) (COM3)" to "MediaTek USB Port (COM4)" in an endless loop. It's almost like the phone can't make up its mind about which driver to use. I am wondering if my earlier failed attempt to flash TWRP onto the x626 had caused this issue (along with bricking my phone)?

    If anyone knows how to fix this problem please let me know. I'm fairly convinced that once the PC is able to connect, the unbricking process should be fairly straightforward!
    Click to expand...
    Click to collapse
    I've been through the same thing, soft bricked my phone the first day I got it :)) . Long story short...black screen , just the red light when connecting the usb cable and pc just basically didn't recognize it or kept disconnecting when it did. I've spent 2 days playing around with it and I can't remember where but there is a site and a youtube clip that explains how to unbrick. What worked for me was pressing the volume up or volume down (try both since I don't remember which worked) when connecting the cable to the phone in Flash Tool/Mtk tools .IKeep pressing the volume button until the download starts and you see the green bar loading. otherwise it will imediatly disconnect. I know I'm a little cryptic here but it's my first phone with an MTK chip so the whole flash process is new to me . I'm more used with the simple Qualcomm process. Hope this helps.

    I don't know if I'm allowed to post a link but here it is.. http://tickernel.org/how-to-unbrick-le-x626-red-light/
    View
    1
    R
    rdlegy
    joebah said:
    Okay, so I downloaded all three files "Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip", "x620_flash_tool_androidbrick.7z" and "unbrick_tool_x626.zip" and extracted them. I tried the "How to fix le x626 undetected" step first given that none of this will work if the USB connection is not stable...

    The problem is that because my PC keeps connecting and disconnecting from the X626, it's impossible to update my PC device driver as the instruction suggests. However, I noticed that under the Port section of device manager, each time the X626 tries to reconnect to the PC, the name of the driver changes. It cycles from "MediaTek Preloader USB VCOM (Android) (COM3)" to "MediaTek USB Port (COM4)" in an endless loop. It's almost like the phone can't make up its mind about which driver to use. I am wondering if my earlier failed attempt to flash TWRP onto the x626 had caused this issue (along with bricking my phone)?

    If anyone knows how to fix this problem please let me know. I'm fairly convinced that once the PC is able to connect, the unbricking process should be fairly straightforward!
    Click to expand...
    Click to collapse

    I have managed to unbrick my leeco x626 using this guide. I am very thankful for the help. The problem now is that I am with the rescue rom and I want to install other rom like cuoco. I also don't have imei and baseband.I have lost my box and don't know the phones imei. Can you help me recover my imei(it could be different imei than my phone, I don't mind if it works) and install another rom. Thanks!
    View

New posts