First of all you will need .NET installed if you do not have it already. I would recommend .NET 3.5. You can download it from Microsoft here.
The most important part about flashing a rom is knowing what SPL version your phone has and what rom you want to use before you begin flashing. If you are at a point where you have already begun flashing and are now getting a green, distorted screen, having huge issues with the phone not responding and airplane mode being stuck on, that is because you have done the process wrong. Don't fret, you can simply start over with this guide. You can still place your phone into the bootloader so you are ok.
The first thing to do is check what your SPL version currently is. To do this you need to enter bootloader by:
Turn it off.
Hold the volume down button while you press the power on button.
You should see a tri-color screen with some text (This is bootloader).
Plug in your phone to your computer via USB. At the very bottom of the screen it should show USB.
Once you know what your SPL version currently is you need to decide whether you want to use USPL or HSPL to flash roms.
The difference between USPL and HSPL:
HSPL is an user-modified SPL that you have to flash to your phone. It overwrites the existing SPL on your device with a "hacked" one so to say. It allows you to bypass the HTC certificate check and flash unsigned or CID-mismatching roms to your phone. You only have to flash it once and then you can flash roms anytime.
USPL is a temporary solution. It takes advantage of an exploit in the existing SPL and then loads a modified one to memory, effectively allowing the same thing as HSPL. However, since this is only memory-resident you have to do it each time you want to flash unsigned or CID-mismatching roms to your phone, because this exploited state is lost upon reboot. With USPL you must still have the right version of the HTC SPL that is compatible with the rom you want to use.
Now that you have decided which route you want to go as far as SPL's go, temporarily disable or uninstall your virus scanning software as 90% of them will conflict with flashing.
If you wish to use HSPL and it shows your current SPL as:
Anything but 1.56.OliNex - go to step (HSPL1) on post 2
1.56.OliNex - go to step (HSPL4) on post 2
If you wish to use USPL and it shows your current SPL as:
Anything but 1.54.0000 - go to step (USPL1) on post 3
1.54.0000 - go to step (USPL5) on post 3
If you are getting errors during the RUU process, read this guide for descriptions of the error codes and associated solutions/suggestions!
If you need to update your USB drivers, read this guide for step-by-step instructions!
MOD EDIT (01/10/09)
Video guide to help newbies out with loading ROMs
HSPL Method
Use this method only if you selected the HSPL route from the first post!
HSPL1 - Downloads
(HSPL1a) HSPLWrapper_Blackstone_156OliNex.zip
(HSPL1b) A 1.56+ based rom - Your end result rom, i.e. rom you want on device which is based on 1.56+
(HSPL1c) BlackstoneRUUWrapper.zip
(HSPL1d) SSPL-Manual-TouchHD.zip
(HSPL1e) Extract each item to its own folder
HSPL2 - Flash new SPL (1.56.OliNex)
(HSPL2a) Place your phone into its bootloader.
(HSPL2b) Run HSPLWrapper_Blackstone_156OliNex.exe from the download in step (HSPL1a) and follow it as normal.
(HSPL2c) If successful, go to step HSPL3. If the flashing process sits at 0% and you get Error [260] connection after some time, go to step (Troubleshooting).
HSPL3 - Check SPL version
(HSPL3a) Place your phone into its bootloader.
(HSPL3b) When the bootloader appears it should show SPL v 1.56.OliNex. If it does go to step (HSPL4). If it does not something happened so repeat step (HSPL2).
HSPL4 - Flash new 1.56+ rom
(HSPL4a) Place your phone into its bootloader.
(HSPL4b) If the rom you downloaded from step (HSPL1b) does not include BlackstoneRUUWrapper.exe then use the download from step (HSPL1c). Make sure the .nbh file from step (HSPL1b) and BlackstoneRUUWrapper.exe are in the same folder.
(HSPL4c) Run BlackstoneRUUWrapper.exe and follow it as normal.
(HSPL4d) Hard reset afterwards. Once or twice- up to you. Twice has been recommended. Turn off your phone. I personally do it right after flashing completes and I see the "Smart Mobility" screen. I just yank the battery out instead of waiting for it to boot up all the way and go through customization process just to hard reset Hold the volume down button and volume up button while you press the power on button. You should see a message saying "This operation will delete all your personal data, and reset all settings to the manufacturer default settings. Press VolUp to restore manufacturer defaults, or press other keys to cancel." Do exactly what it says...
You are done!
Troubleshooting - manual SSPL
Boot up your phone.
Copy SSPL-Manual-TouchHD.exe to your phone. In a file browser on your phone browse to where you copied SSPL-Manual-TouchHD.exe and run it.
Your phone will reboot into its bootloader and should show SPL v 1.07.OliNex.
When it shows USB at the bottom then run HSPLWrapper_blackstone_156OilNex.exe from your computer again.
Go to step HSPL3 if successful.
USPL Method
Use this method only if you selected the USPL route from the first post!
USPL1 - Downloads
(USPL1a) RUU_Signed_Blackstone_stockSPL154.zip
(USPL1b) HSPLWrapper_Blackstone_156OliNex.zip
(USPL1c) USPL GUI v 2.5.zip
(USPL1d) A 1.56+ based rom - Your end result rom, i.e. rom you want on device which is based on 1.56+
(USPL1e) BlackstoneRUUWrapper.zip
(USPL1f) Extract each item to its own folder
USPL2 - Updating HTC USB Sync driver
(USPL2a) Follow my guide here on updating the HTC USB Sync driver.
USPL3 - Flash new SPL (1.54.0000)
(USPL3a) Place your phone into its bootloader.
(USPL3b) Run USPL.exe from the download in step (USPL1c). Remember to disable your antivirus for this. Some provide a false positive that it is a virus/trojan. When the application appears click on Run USPL.
(USPL3c) Your phone should reboot and return to its bootloader but saying SPL v 1.15.USPL and USB at the bottom. If it does not show USB after some time, disconnect and reconnect the USB cable from your phone.
(USPL3d) Run HSPLWrapper_Blackstone_156OliNex.exe from the download in step (USPL1b). Do not click any buttons on the screen when the application appears.
(USPL3e) Copy RUU_Signed.nbh that you extracted from the download in step (USPL1a) and overwrite the one in the directory where you ran HSPLWrapper_Blackstone_156OliNex.exe from. If you get an error message saying that the file is already in use that is because you clicked one or more buttons in the HardSPL application window once it appeared. If that happens to you, exit from it, start it again, and DO NOT CLICK ANYTHING YET.
(USPL3f) Now you can continue in the HardSPL application and follow it as normal. Basically what you are doing is flashing the stock 1.54.0000 SPL to your phone by overwriting the HardSPL's .NBH file with the stock one.
USPL 4 - Check SPL version
(USPL4a) Place your phone into its bootloader.
(USPL4b) When the bootloader appears it should show SPL v 1.54.0000. If it does go to step (USPL5). If it does not something happened so repeat step (USPL3).
USPL 5 - Flash new 1.56+ rom
(USPL5a) Place your phone into its bootloader.
(USPL5b) Run USPL.exe from the download in step (USPL1c). Remember to disable your antivirus for this. Some provide a false positive that it is a virus/trojan. When the application appears click on Run USPL.
(USPL5c) Your phone should reboot and return to its bootloader but saying SPL v 1.15.USPL and USB at the bottom. If it does not show USB after some time, disconnect and reconnect the USB cable from your phone.
(USPL5d) If the rom you downloaded from step (USPL1d) does not include BlackstoneRUUWrapper.exe then use the download from step (USPL1e). Make sure the .nbh file from step (USPL1d) and BlackstoneRUUWrapper.exe are in the same folder.
(USPL5e) Run BlackstoneRUUWrapper.exe and follow it as normal.
(USPL5f) Hard reset afterwards. Once or twice- up to you. Twice has been recommended. Turn off your phone. I personally do it right after flashing completes and I see the "Smart Mobility" screen. I just yank the battery out instead of waiting for it to boot up all the way and go through customization process just to hard reset Hold the volume down button and volume up button while you press the power on button. You should see a message saying "This operation will delete all your personal data, and reset all settings to the manufacturer default settings. Press VolUp to restore manufacturer defaults, or press other keys to cancel." Do exactly what it says...
You are done!
Dude, this is tight!!! Awesome Yo!
Loveleh!
I am so frustrated!!!!!!!!! I have followed these instructions to a T, and I still get an error when trying to flash to 2.8. I keep getting the error: [240] File Open.
Can someone please help me???
Thanks!
You've been a busy boy!!!
Excellent post mate, was getting sick of posting this process myself. Now all I have to do is direct them all here, or to the wiki
Awesome stuff. I wish this was around the other night when I spent hours and hours reading and reading before finally sorting it out.
I failed at your step 7 however as I think it was 2am and I was passing out in front of the PC whilst rebooting and hard resetting over and over. Beer tonight then!
Cheers
This guide totally saved my life (A.K.A phone).
Thank you very much.
Wow... excellent mate!
Thanks!
Thanks for this great work.
Unfortunately Im stuck at step 5d
USB connection in Activesync mode is off.
My phone is in bootloader, "Serial" change to "USB" aswell
However when I launch blac_uspl.exe in command prompt (in windows XP) I have the following error : D:\Mes documents\Downloads\uspl_2.5>blac_uspl
HTC Blackstone USPL version 2.5, Apr 5 2009
Opening USB port \\?\usb#vid_0bb4&pid_00ce#5&381252ce&0&1#{25dbce51-6c8f-4a72-8a
6d-b54c2b4fc835}...
ERROR: USB port could not be opened!
Verify that device is connected and SPL boot mode is active,
disallow USB connections in ActiveSync settings and try again.
If I need to install "vista usb drivers", please kindlly state how to.. in XP as the folder c:\winnt\inf contains .inf & .cat files.
Thnx a lot.
Multani004 said:
Thanks for this great work.
Unfortunately Im stuck at step 5d
USB connection in Activesync mode is off.
My phone is in bootloader, "Serial" change to "USB" aswell
However when I launch blac_uspl.exe in command prompt (in windows XP) I have the following error : D:\Mes documents\Downloads\uspl_2.5>blac_uspl
HTC Blackstone USPL version 2.5, Apr 5 2009
Opening USB port \\?\usb#vid_0bb4&pid_00ce#5&381252ce&0&1#{25dbce51-6c8f-4a72-8a
6d-b54c2b4fc835}...
ERROR: USB port could not be opened!
Verify that device is connected and SPL boot mode is active,
disallow USB connections in ActiveSync settings and try again.
If I need to install "vista usb drivers", please kindlly state how to.. in XP as the folder contains .inf & .cat files.
Thnx a lot.
Click to expand...
Click to collapse
Yes, download the USB drivers from above and extract them to a folder. Mind where you extract them. Follow these steps:
(1) Start -> Run -> devmgmt.msc
(2) Look for HTC USB Sync
(3) Double-click it and click the Driver tab
(4) Click Update Driver
(5) On new screen tell it not to use Windows Update
(6) Install from a specified location
(7) Check only box that says "Include this location in the search"
(8) Click Browse and locate the extracted drivers you downloaded
(9) After selecting click next and select the new driver
(10) After it is updated reboot and try USPL again
Let me know how it works.
damian.r.smith said:
Awesome stuff. I wish this was around the other night when I spent hours and hours reading and reading before finally sorting it out.
I failed at your step 7 however as I think it was 2am and I was passing out in front of the PC whilst rebooting and hard resetting over and over. Beer tonight then!
Cheers
Click to expand...
Click to collapse
LOL, good deal!
pierce97 said:
I am so frustrated!!!!!!!!! I have followed these instructions to a T, and I still get an error when trying to flash to 2.8. I keep getting the error: [240] File Open.
Can someone please help me???
Thanks!
Click to expand...
Click to collapse
What is giving you this message? The RUU? What step are you at in my guide? Do you get USPL run successfully? Does your bootloader on your phone show 1.15.USPL and USB when it's connected to your computer?
Keep up the good work bro and you'll be a MOD soon enough!!!
Fallen Spartan said:
Keep up the good work bro and you'll be a MOD soon enough!!!
Click to expand...
Click to collapse
haha... that's a big job on this forum!
Thanks for the quick reply.
Up to step 5, everything is ok.
but It wont let me update saying its impossible to update the drivers.
1 more thing i want to mention is that i found those inf & cat files already present in c:\winnt\inf folder. ofcourse the size is not the same.
I will try to update the drivers again though Im starting to assume that my windows dont see a different between already present files and new extracted files.
Multani004 said:
Thanks for the quick reply.
Up to step 5, everything is ok.
but It wont let me update saying its impossible to update the drivers.
1 more thing i want to mention is that i found those inf & cat files already present in c:\winnt\inf folder. ofcourse the size is not the same.
I will try to update the drivers again though Im starting to assume that my windows dont see a different between already present files and new extracted files.
Click to expand...
Click to collapse
You can force Windows to accept the new driver files. You just have to tell it that you "Have Disk" and locate those files. Once you do it will show a dialog where you can select the device and it should overwrite your current driver with the one from the download.
Good picture step-by-step guide for updating drivers can be found here
Fallen Spartan said:
Good picture step-by-step guide for updating drivers can be found here
Click to expand...
Click to collapse
Nice, I'm going to edit that into my guide instead of my half-assed directions
Hi, i would like to somebody helps me, i got my htc recently and i can't do it a hardspl i do all the steps and when it comes to almost finish gave an error i've tried with many different hardspl and nothing, i will show you the erros that gaves me... please help me with this problem, cause i can't do anything to my htc...
Hi
I have the some problem, I have follow this guide :
Step 2 - Upgrade to Hard SPL
Hard SPL will allow you to flash cooked ROMs without SuperCID’ing your device and also will protect your device from being bricked in a bad flash. If a bad flash occurs it should remain in bootloader, and you can re-flash another ROM.
Before you proceed, check which SPL is on your device. Manually enter the Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time. If your SPL is 3.20.Olipro then you already have Hard-SPL on your device and can skip this step and proceed to upgrade your ROM or radio.
1. Download the Hard-SPL for P3600i (do NOT use any of the Hard-SPL's for Trinity/DoPod)
* Hard SPL 3.20.Olipro (P3600i HardSPL v1.1)
2. Unzip the Files, and click on ‘ROMUpdateUtility.exe’
Image Missing
3. Check the checkbox, and click ‘next’
Image Missing
4. Follow the directions in the window, and establish an activesync connection with your device
* Make sure the activesync icon is be green (finished synchronizing)
* Make sure your battery is charged
Image Missing
5. Check the checkbox, click ‘next’
Image Missing
6. In the next window, click the ‘Update’ button
This will show the version number of the ROM, radio, or in this case bootloader that you are about to flash.
Image Missing
7. After the version number has appeared, click next
Image Missing
8. In the following window, click ‘next’
after you click this, the flash will begin, so do not disconnect your device or do anything stupid on your computer
Image Missing
!NOTE! (quoted straight from Jon's post on first page)
WHEN FLASHING HARDSPL, IT WON'T WORK THE FIRST TIME - YOU WILL GET AN ERROR (CODE 260). THIS IS EXPECTED.
Quote:
Originally Posted by joncgde2
This is what happens.
You go to flash HardSPL like the guide says. LOOK AT THE SCREEN ON YOUR PHONE, YOU MIGHT HAVE SECURITY PERMISSIONS AND NEED TO MANUALLY ALLOW THE PROGRAMS TO RUN.
It looks like it's about to flash and then errors. BUT your phone is on the 3-colour bootloader screen! How odd. Well KEEP YOUR PHONE ON THE BOOTLOADER SCREEN, and unplug it from your computer. Exit the HardSPL program, RUN IT AGAIN, and FLASH THE PHONE AGAIN WITH HARDSPL (obviously connect your phone and stuff back to your PC).
The point here is this: the first time it will fail, but at least manage to get the bootloader up. With this bootloader up, exit the flashing program, restart it, and then you should be able to run the flashing program and have it complete.
DOUBLE CHECK YOUR PHONE HAS THE OLIPRO HARDSPL INSTALLED after completion, by soft-resetting (hold the power and camera buttons at the same time AND use the stylus to press the putton at the bottom of the phone. You might not get it the first time, but with practice you'll get the hang of it).
9. A Progress bar will appear on your computer screen, and your trinity will display a grey screen with progress bar. Be patient while your device is being updated.
Image Missing
Image Missing
10. Once your device is finished updating, it will automatically soft reset. Click the ‘Finish’ button to exit the RUU program.
Image Missing
To confirm is Hard-SPL is on your device, manually enter Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time. If successful you will see the tri-colour screen and the following will be displayed
Hard SPL 3.20.Olipro (P3600i HardSPL v1.1)
but also after restart a lot of time HARDSPLromupdateutility.exe, I still have the same problem!
anybody may help me?
Now I have stratos image,
maybe is this the problem?
Hi
Pls I need help, I tried to upgrade my HTC P3600 then my computer crash so now every time I try to start my phone all what I got is a picture (HTC start mobility) and then nothing.
Pls help me.
Thanks
Hi gys, I think that this is my first post, but I want to share some solution for with you. The most important think with "connection" errors is to have HSPL installed correctly. I was trying to install on my HD2 universal ones, like Hard spl v7 and 9, but problems occured. So after trying everything, I found HSPL (on this forum) just for HD2. After that, everything wass like a charm
Hi,
my P3600 has a serious problem! I've flashed an Elegant Ed. (but I don't remeber the version). Now, I'd like to reinstall original ROM, but this is the results:
1) PC WIN VISTA: Activesync get ON, the PC see the PPC and the result is CONNECTED.
2) Incoming to update the PPC but the error IS 260 (communication error)
3) in the bootloader is indicated:
a) TRIN100 - IPL-0.50
b) TRIN100 - SPL-1.07.0000
c) serial
4) I downloaded [P3600i] HardSPL v1.1 and installs its on PPC and in bootloader there's (but error 260 continues to work )
a) TRIN100 - IPL-0.50
b) TRIN100 - SPL-3.10.Olimpo
c) PPC in bootloader config.
d) serial
5) Now, there's a SPL on my PCC !!! Connect and disconnect my USB cable by PPC, leaving PPC in bootloader configuration and by activesync disable "connect by USB"
6) insert usb cable in PPC, but it doesn't go to USB
..... I do not know what to do !!!!
Please help my
Junior
base167 said:
Hi,
my P3600 has a serious problem! I've flashed an Elegant Ed. (but I don't remeber the version). Now, I'd like to reinstall original ROM, but this is the results:
1) PC WIN VISTA: Activesync get ON, the PC see the PPC and the result is CONNECTED.
2) Incoming to update the PPC but the error IS 260 (communication error)
3) in the bootloader is indicated:
a) TRIN100 - IPL-0.50
b) TRIN100 - SPL-1.07.0000
c) serial
4) I downloaded [P3600i] HardSPL v1.1 and installs its on PPC and in bootloader there's (but error 260 continues to work )
a) TRIN100 - IPL-0.50
b) TRIN100 - SPL-3.10.Olimpo
c) PPC in bootloader config.
d) serial
5) Now, there's a SPL on my PCC !!! Connect and disconnect my USB cable by PPC, leaving PPC in bootloader configuration and by activesync disable "connect by USB"
6) insert usb cable in PPC, but it doesn't go to USB
..... I do not know what to do !!!!
Please help my
Junior
Click to expand...
Click to collapse
You have choice a wrong HardSPL !!!
Olipro 3.10 and 3.20 are for HTC P3600i and no working for TRINITY P3600.
So, now probabily you don't see "USB" on Bootloader when you connect you trinity on PPC.
Solution:
You must reload your H-SPL With SD CArd.
It's very simple:
searching for a Hard SPL for trinity device, example Olipro 1.20 and rename file "RUU_signed.nbh" ---> "TRINIMG.nbh".
Then copy file "TRINIMG.nbh" in a SD CARD and insert it on your Trinity; After that , make a Soft reset with stylus reset +power+camera.
Power bottom for update your Bootloader.
Now you would see your trinity working again
Davide
Hello!
I have this problem:
I've installed WM6.5 on my Trinity, and it worked well, but today I wanted to try WM6.1 (0.4.9.0 digital) also. The following happened:
Everything worked fine, but at 54% flashing my brother lifted the phone, possibly it lost the USB-contact, because the flasing stopped with an error message (unfortunately can't remember the error number). Since then if I try to flash it with WM6.1 or WM6.5, after 1% the phone resets itself, and the RUU gives a 270 error.
I have the original WM5 ROM also, but if I try installing it, after "Verifying information on your PDA Phone" screen I get a connection error 260.
What can I do???
After the phone resets itself, I can see the HTC logo, and the red letters and numbers, but that's all.
If I try HardSPL, I also get a 260 error.
Can you enter bootloader manualy?
If you can than see SERIAL change to USB when connected to PC it should be OK.
if you have a SD card, you can also try to flash "manualy".
- put your RUU... NBH at the root of the card,
- rename it trinimg.nbh,
- reinsert the card in the phone,
- enter in bootloader (power+cam+reset)
you will have a grey screen asking to push "power", do it and that's it.
if USB is well working, maybe you just need to reflash the hardspooler.
Thank you for your replies.
Fortunately I solved the problem.
I did the following:
1. To be sure, do all the stuff on a Windows XP machine
2. DISABLE "Allow USB Connection" in Active Sync so you see a small red X symbol next to the Active Sync symbol
3. Start the device into Bootloader mode (Cam+Power+Reset) and connect the device to your PC and make sure USB is written on the bottom of your screen (NOT Serial!)
4. Download splxploit (http://forum.xda-developers.com/atta...0&d=1180043588) and execute unlock on your PC
5. Follow the instructions
6. Download HardSPL (http://forum.xda-developers.com/atta...8&d=1185364317) and follow the instructions
7. Finally (to be sure) restart into Bootloader mode and check if SPL is showing "SPL-1.30.Olipro) - if this is the case you've done it !
8. Flash your preferred ROM via miniSD or USB connection
I m glad you solved this. Every day another new way of solving the flash problems.
Hi to All guys
i've got a trinity from my work and it has a custom rom.
I wanted to changed the rom so i download a wm 6.5 and erase the trinity with mtty. After that i try to install the rom with he RUUUupdate, but it get error 270.
Only in that moment i read on the bootloader and see that it haven't olipro or another HARDSPL installed.
So i looked for a solution and i try the unbrick with the splxploit. I did it and i get olipro on the bootloader, but i don't know how go on with install, if i use the exe i get 260 connection error.
Can you help me?
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.
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...
alberto-a-l said:
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...
Click to expand...
Click to collapse
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!
I have some problem...
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/
Catani said:
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..
Click to expand...
Click to collapse
Hi - yes that's the site I am downloading the flashtool from. I pressed the volume +/- button and plugged in the phone after clicking on "Download" in the flash tool as you have suggested. It still disconnects and the download never happened - however the Flash tool gave me this this error message :
BROM ERROR : S_COM_PORT_OPEN_FAIL (0x3F5)
[COM] Failed to open COM port.
[HINT]:
Was this the same error you got from the Flash Tool when you tried plugging the phone when downloading? So you kept plugging it out and back in again until it worked right?
Catani said:
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/
Click to expand...
Click to collapse
Okay, so It seems like different solution has different outcome for everyone. Instead of clicking download button on SP Flash Tool and plugging in the phone (which did not work), I did the opposite instead by plugging in the phone first and THEN immediately click download button on SP Flash Tool. Also, instead of holding down Vol - button I pressed it repeatedly (apparently someone claims that this confuses the SP Flash tool and sometimes it works). Then all of a sudden the flashing starts working :laugh:. However, the SP Flash tool bugged out after 10 seconds and told me the Flashing process failed , and I was back to square one. The odd thing is that when I tried replicating this method the flashing process won't start anymore (SP Flash tool just get hung up) - though at least the phone now connects to the PC USB permanently. ADB still tool doesn't work either. So I'll try deleting and reinstalling the device driver and tinker with this but it looks like the only way to resolve this is to try as many different things as possible. Will post again if I can find a solution but in the meanwhile if you have any other suggestions please let me know!
joebah said:
Hi - yes that's the site I am downloading the flashtool from. I pressed the volume +/- button and plugged in the phone after clicking on "Download" in the flash tool as you have suggested. It still disconnects and the download never happened - however the Flash tool gave me this this error message :
BROM ERROR : S_COM_PORT_OPEN_FAIL (0x3F5)
[COM] Failed to open COM port.
[HINT]:
Was this the same error you got from the Flash Tool when you tried plugging the phone when downloading? So you kept plugging it out and back in again until it worked right?
Click to expand...
Click to collapse
Yes. It was the same for me but eventually I got it. I can't remember exactly but I was swapping the volume button. I remember I kept pressing either volume up or down and the download went all the way. If you don't press the volume button you will constantly get those errors. It's trial and error...keep trying , eventually you will get it. Oh, and I was forgetting, you can also try to change the driver manually, you should have 3 drivers to choose from. Try all 3, because only one of them work.
owell
i managed to get mediatek usb port in device manager but my download wont start in the flash tool. have you managed to unbrick it? if so, please provide some help
Summarizing my experience with the bricked X626 (so far)
Okay, so after a few days of messing around with the x626 - I was still unable to get it fixed :crying:. However, since I spent quite a few hours tinkering with the flashing process, I figured I might as well document my experience on XDA so other people who are having the same issues can at least get to where I am without having to waste a few days messing around with their PC, and perhaps share their experience with the rest of the community once they are able to unbrick their x626!
Resolving USB connect/disconnect issue (Windows 10)
-------------------------------------------------------------------
This was finally resolved for me - and I found the following solution to work most of the time:
1) Restarted PC in troubleshooting mode
2) press "7" at startup screen option to enable the user to install unsigned drivers.
3) After the booting is completed, open device manager
4) Connect the x626 to the PC's USB, wait for the generic USB driver to show up under "Ports (COM & LPT)" (along with the USB connect chime sound). Sometimes, you have to wait for a minute or two for this to happen. If this doesn't work try holding the power button and Vol -, it 'wakes' up the phone somehow.
5) Once you see the new COM port lights up on Device Manager, quickly select it, right click, update driver and overwrite with the "MediaTek DA USB VCOM" from the Windows+10_MTK+VCOM+USB+Preloader+Drivers inf file (you'll have to google the instructions from other website but it's pretty straight forward).
6) 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.
7) Now reassign all these COM ports (right click, properties, Port setting, advanced) to a single designated port (like, say "3").
8) 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 much easier to flash.
Resolving Flashing issue
------------------------------
This may not work for everyone, but this is what worked for me:
1) Power down the phone first (by holding Power button and Vol - button for 15 seconds since I have no way of telling if the phone is on or not due to the constant black screen) ,
2) Keep holding the Vol - button and plug the USB cable in, wait for the connection sound to chime on my PC
3) When that happens immediately click on Download button on Flashtool. Timing is crucial here, you have to be pretty quick with steps 2 and 3.
By doing this I was able to get the flashing going most of the time - though I do still get the "BROM ERROR : S_COM_PORT_OPEN_FAIL (0x3F5)" every now and then in which case I would unplug the phone from the USB and try again.
Dead end?
------------
Unfortunately, I wasn't quite able to flash everything. If I try to flash all the items in the Download table (except recovery and boot) using the Android scatter file, authentication file and DA_PL_HIGH.bin file per instruction, the status bar at the bottom of SP Flash Tool window would go from red (Downloading DA 100%) to purple (Download BootLoader 100%) - but then it ends up getting stuck for about 10 seconds, before giving me the error "BROM ERROR: STATUS_OPEN_FILE_ERR (0xC001000E)".
The ONLY way I can get the flashing process to go through completion is by unticking all the options on the download table except preloader. Only then would I get the "OK" notification from SP Flash Tool. Since the instructions on the web tells me that I should be ticking all the boxes except boot and recovery, I would imagine that this is not the correct way of doing things...
Fortunately, the Write Memory part works (that's where I press Ctrl Alt V, choose the Write Memory Tab, pick the recovery_stock_works _after_brick.img and type 0x8000 in the Being Address field). I used the same procedure as when flashing. So far so good...
But then I would run into the same problem again when flashing using DA_PL.bin file (supposedly the final part of the solution), with SP Flash tool tells me "BROM ERROR: STATUS_OPEN_FILE_ERR (0xC001000E)" .
So I am at a loss on what to do next. I did see some other people reporting that they got to where I am but pretty much can't progress any further due to this STATUS_OPEN_FILE_ERR problem... so if anyone is able to get through the flashing process and get their x626 to boot up, please please please share their experience, preferably on this thread! :fingers-crossed:
Catani said:
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/
Click to expand...
Click to collapse
You could ask for my permission at least, to copy paste my article to your blog hmm ?
os_man said:
You could ask for my permission at least, to copy paste my article to your blog hmm ?
Click to expand...
Click to collapse
I'm sorry, are you talking to me? That's not my blog. I was just helping the guy with his problem, I posted a link to a site that I found while I was researching the same problem that I had. If any of that material found on the blog is yours you should take it up with the owner, if I'm not mistaken I think he's a XDA member also.
Catani said:
I'm sorry, are you talking to me? That's not my blog. I was just helping the guy with his problem, I posted a link to a site that I found while I was researching the same problem that I had. If any of that material found on the blog is yours you should take it up with the owner, if I'm not mistaken I think he's a XDA member also.
Click to expand...
Click to collapse
Sorry i ment the owner of that blog that you gave the link, the tickernel guy
Okay, so after taking a break for a few days to clear my head and then coming back to this problem, I finally noticed what I did wrong. I used the wrong scatter files and .img file for all the steps! That's why the flashing process never completed!
So for the first part, the configuration is supposed to look like this:
Download Agent : \..\..\x620_flash_tool_androidbrick\secureboot\DA_BL_HIGH.bin
Scatter-Loading File: \..\..\LeEco_x620_SP_Rom.androidbrick\MT6797_Android_scatter.txt
Authentication File: \..\..\x620_flash_tool_androidbrick\secureboot\auth_sv5_letv.auth
Untick Boot and Recovery, and now I can flash the entire thing (Green okay sign) without even having to hold down the Vol - or + button!
Then for the memory step, I used the boot-verified.img in the downloaded folder LeEco_x620_SP_Rom.androidbrick, and write to 0xf900000, this time I pressed the Vol + button, and the writing works (Green okay sign)
For the second memory step, I used the recovery_stock_works _after_brick.img in the folder LeEco_x620_SP_Rom.androidbrick, and write to 0x8000. Once again, the writing works (Green okay sign)
I am not sure if I did the DA_BR.bin step correctly or not... but after doing this the screen came on when I tried to boot! I did have to charge it first as the battery was completely dead. However, like the tutorial said, the screen is 'mirrored' (ie, it's like holding the phone to a mirror and seeing everything backward - really weird). So I can't use the phone at this point - But hey, this is the first time in two weeks that I am no longer stuck on a black screen when I tried to power on the phone! Woo hoo!
I feel like I am getting close to fixing this phone now... will post if there is any new development. So excited! :fingers-crossed:
Finally!
Okay, so I downloaded the file S3_X626.rar per the second part of the instruction - took a while but in the end it resolved all my problem. Here's my experience (I want to document before I forget about the details as it seems with this issue you need to get everything right to unbrick the phone)
So my phone screen is mirrored right now, I can kind of navigate around but have to guess where to touch the screen to go into apps and settings. Also, the baseband, EMEI and just about everything is missing. Clearly this was sort of a temporary ROM that gets the phone back into a semi ususable state. In fact, it took me a little while to figure out how to shutdown the phone again! (necessary for the next step)
After unzipping S3_X626.rar - it created a folder called "乐视S3_X626". I also got a bunch of warnings from Windows Defender about virus/Trojans etc - I ignored them.
I booted the phone in fastboot mode per instruction (Vol -, Power), and the familiar black screen with Chinese characters showed up on the phone. I then plugged in the phone into USB. By now my PC fully recognizes the X626! So no more annoying connect/disconnect problem.
I ran the file 开机oem解锁-音量下+开机键_读取Devices.bat. The Dos prompt did a bunch of stuff (I guess it's unlocking the bootloader?) and then a text file "Devices.txt" is generated in the folder. I guess this part just figures out some sort of ID of the phone? Anyway, onto the next step..
I ran 刷机.bat, immediately I got an error on the dos prompt and had to exit. So it turned out that for this step, I need to change the folder name from 乐视S3_X626 to S3_X626 by removing all the Chinese characters - which the instruction said though it wasn't very clear when the author wrote it. The dos prompt went through some sort of flashing process which took like 10 mins. When it was done, I unplugged the phone - and had to hold down the power button for a while to reboot (at first it just got stuck on the bootloader screen)
The next part is where things got interesting. So now the phone rebooted normally and the "EUI" logo showed up. Then it froze. So I rebooted the phone again, and this time the EUI logo showed up and it started to initialize the app (I think 15 of them). That took about 10 mins - thankfully I had my device all charged up before I did all this! Finally, we got to the setup screen, put in my Sim Card and connected to Wifi - skipped the finger print set up stuff and finally I am back to the home screen. Also, the EUI is now in version 5.9.020S (I was on 5.8 earlier), with baseband, IMEI and everything! Android 6.0 of course. Everything works as it should.
So this has been one heck of an effort to unbrick. To be honest, I was about to throw away the phone had it not been for the fact that it's the holiday seasons and I had a lot of down time on my hands . Must have spent a good 15-20 hours messing around with it. Definitely the USB connection and flashing were the hardest to figure out as there are all sorts of different instructions on the web on how to do this and there doesn't seem to be one right way of doing it - though I would have to say that the tickernel blog / OS_man instruction (not sure who owns the IP to this one but thanks guys) is the most helpful. My guess is if your phone is bricked and tried to copy my instruction word for word, there's still a good chance it won't work for you! Anyway, I figured documenting my experience on XDA would be helpful because at least you get to know what will happen if you get a step right (or wrong) - I was mostly in the dark when I did this. Merry X mas!
Thanks for directing me to the website. I have unbricked my phone now and put a detailed 'journal' of how I did this on my original post under "Edit" section for all to see! Have a happy new year!
alberto-a-l said:
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...
Click to expand...
Click to collapse
Thanks for your help
Thanks for directing me to the website. I have unbricked my phone now and put a detailed 'journal' of how I did this on my original post under "Edit" section for all to see! Have a happy new year!
Catani said:
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/
Click to expand...
Click to collapse
batch23 said:
i managed to get mediatek usb port in device manager but my download wont start in the flash tool. have you managed to unbrick it? if so, please provide some help
Click to expand...
Click to collapse
Hi - please see the edited version of the original post where I made a detailed documentation of what I did to unbrick the phone. It's been extremely frustrating for me too and I got stuck in the flashing stage for almost three weeks - but if you try what I did I think you might be able to get the flashing work though the result is not always consistent (ie, you may have to attempt to flash several times and double/triple check everything as one minor error will immediately cause an error). It's a pain but don't give up yet! Happy new year!
Hi - if you did come up with the solution on that tickernel site then thanks for your help for making my phone work again! Have a happy new year!
os_man said:
Sorry i ment the owner of that blog that you gave the link, the tickernel guy
Click to expand...
Click to collapse
Hi please see my documented solution in the edited section of the original post Happy new year!
rapidsebuja said:
I have some problem...
Click to expand...
Click to collapse