Bricked Le S3 X626 after flashing TWRP, can't power on, PC won't recognize device
- Thread starter joebah
- Start date
Hello! I wrote you a long message but I think I deleted it or it is not posted :CHi please see my documented solution in the edited section of the original postHappy new year!
I wanna thank you your trial and error findings because I think it's very helpfull for everyone in the same boat (as me).
I bricked phone for recovery as you did and I'm having issues with driver and SP detection.
I think your findings are very interesting but I have one problem, in the step you change the driver VCOM, im in windows 7 and it doesn't detect them good.
I can have the drivers installed ok (only once at time) but then the SP ignore the phone.
You're my last hope.
Hi - so I didn't get your detailed message so I'm going to have to assume from your msg below that despite installing the driver successfully, when you plug in the phone nothing happened - not even USB connect sound right?
So I had that happened to me as well - and here's how I eventually fixed it:
First, I have the device manager window and Flash window open side by side. Not sure if this is the case in Win 7 but normally if the driver is working properly when you plug the phone in the device manager list will change and the driver shows up in the list right after the USB connect sound. With that out of the way, here was what I did which eventually got to working (can't remember which combination but I had to do these steps repeatedly):
1) Hold the Power and Vol- button for 15-20 seconds, let go off both buttons, then plug in without anything pressed. Try this a couple of times. If you do this right then the connection should happen within 5 seconds of plugging in
2) If this doesn't work despite repeated attempts, now try to do the same thing but hold down the Vol - button, then try the Vol + button.
3) If this doesn't happen, try leaving the phone connected by press the Power and Vol- or Power and Vol + or just the power button, and let go after a few seconds. Do this repeatedly.
4) If none of this works, try charging the phone overnight - somebody said it helped them, it didn't help me but it might work for you.
5) If 1-4 still doesn't work, uninstall the drivers, reinstall and redo steps 1-4 again.
I remembered I had to do steps 1-5 at least 3 times before I got it to work... as you can imagine it took a long time...
So I had that happened to me as well - and here's how I eventually fixed it:
First, I have the device manager window and Flash window open side by side. Not sure if this is the case in Win 7 but normally if the driver is working properly when you plug the phone in the device manager list will change and the driver shows up in the list right after the USB connect sound. With that out of the way, here was what I did which eventually got to working (can't remember which combination but I had to do these steps repeatedly):
1) Hold the Power and Vol- button for 15-20 seconds, let go off both buttons, then plug in without anything pressed. Try this a couple of times. If you do this right then the connection should happen within 5 seconds of plugging in
2) If this doesn't work despite repeated attempts, now try to do the same thing but hold down the Vol - button, then try the Vol + button.
3) If this doesn't happen, try leaving the phone connected by press the Power and Vol- or Power and Vol + or just the power button, and let go after a few seconds. Do this repeatedly.
4) If none of this works, try charging the phone overnight - somebody said it helped them, it didn't help me but it might work for you.
5) If 1-4 still doesn't work, uninstall the drivers, reinstall and redo steps 1-4 again.
I remembered I had to do steps 1-5 at least 3 times before I got it to work... as you can imagine it took a long time...
Hello! I wrote you a long message but I think I deleted it or it is not posted :C
I wanna thank you your trial and error findings because I think it's very helpfull for everyone in the same boat (as me).
I bricked phone for recovery as you did and I'm having issues with driver and SP detection.
I think your findings are very interesting but I have one problem, in the step you change the driver VCOM, im in windows 7 and it doesn't detect them good.
I can have the drivers installed ok (only once at time) but then the SP ignore the phone.
You're my last hope.
Sorry because english is not my native language and I speak randomly.
Maaaaan, few minutes later I post here I got blessed with a good timing and the flashing started. And I have to thank you because there is a very important TIP in your experience.
The KEY point is to press the vol - to wake up the phone. Trust me, I have this memory very recent. That way you avoid to plug and unplug endlessly without luck. Because in my case, if the flash show error, the driver stopped switching. If i would told you how many drivers and reebots I did have... (like 100?) :C
I had no phone for 3 days, the battery was full and when I revived it, it was 20ish... very strange. I will make a step by step guide, because I think that is the most important thing of the whole process.
So, once more. Thank you man. Reading you, that you took like a month with the 'common' problems made me less nervious.
Do you think you could edit that?
Something like i wrote you. Press the vol- until the phone wakes up the driver switching (MTK USB driver and MTK preloaded Vcom), and then press the download button, that way the phone flash will eventually start and you don't lose the conection because the driver keeps switching all the time (key point).
I think you don't have to change the com ports, but I was so desperate I did evertyhing i read in the whlole internet
Just one last question. IT was completely necessary to flash the recovery and the boot thing with the hexidecimals? Because after you flash the rom, you have already fastbot to flash the new recovery. I followed your steps, just asking.
See you here)
PS: Now im using miuisu_v6.0_x622_7.10.19, I tried the AOSP of kangburra, but I prefered to avoid exposed and tweaks I won't use. Very nice MIUI, first time in my life.
Maaaaan, few minutes later I post here I got blessed with a good timing and the flashing started. And I have to thank you because there is a very important TIP in your experience.
The KEY point is to press the vol - to wake up the phone. Trust me, I have this memory very recent. That way you avoid to plug and unplug endlessly without luck. Because in my case, if the flash show error, the driver stopped switching. If i would told you how many drivers and reebots I did have... (like 100?) :C
I had no phone for 3 days, the battery was full and when I revived it, it was 20ish... very strange. I will make a step by step guide, because I think that is the most important thing of the whole process.
So, once more. Thank you man. Reading you, that you took like a month with the 'common' problems made me less nervious.
Do you think you could edit that?
Something like i wrote you. Press the vol- until the phone wakes up the driver switching (MTK USB driver and MTK preloaded Vcom), and then press the download button, that way the phone flash will eventually start and you don't lose the conection because the driver keeps switching all the time (key point).
I think you don't have to change the com ports, but I was so desperate I did evertyhing i read in the whlole internet
Just one last question. IT was completely necessary to flash the recovery and the boot thing with the hexidecimals? Because after you flash the rom, you have already fastbot to flash the new recovery. I followed your steps, just asking.
See you here)
PS: Now im using miuisu_v6.0_x622_7.10.19, I tried the AOSP of kangburra, but I prefered to avoid exposed and tweaks I won't use. Very nice MIUI, first time in my life.
Glad I was able to help! You mean press both the power button and Vol- button right? I will edit that in my original note and make note of your experience...
To be honest I have no understanding about the mechanics of this whole recovery process... but I share the same sentiment that perhaps some of the steps mentioned in the tickernel site may be redundant. As you read in my note, I skipped the entire DA_BR.bin step (out of sheer laziness) and it didn't cause any problems for me at all. Taking a wild guess here - since the goal of flashtool is to get this phone back into a semi usable state (mirrored screen version) so you can boot into recovery mode and run all that fastboot stuff , perhaps the author of the website wanted to make 100% sure that everything is in place when in fact you may only need to do just the first part with DA_PL_HIGH.bin You're certainly welcomed to try!
To be honest I have no understanding about the mechanics of this whole recovery process... but I share the same sentiment that perhaps some of the steps mentioned in the tickernel site may be redundant. As you read in my note, I skipped the entire DA_BR.bin step (out of sheer laziness) and it didn't cause any problems for me at all. Taking a wild guess here - since the goal of flashtool is to get this phone back into a semi usable state (mirrored screen version) so you can boot into recovery mode and run all that fastboot stuff , perhaps the author of the website wanted to make 100% sure that everything is in place when in fact you may only need to do just the first part with DA_PL_HIGH.bin You're certainly welcomed to try!
Sorry because english is not my native language and I speak randomly.
Maaaaan, few minutes later I post here I got blessed with a good timing and the flashing started. And I have to thank you because there is a very important TIP in your experience.
The KEY point is to press the vol - to wake up the phone. Trust me, I have this memory very recent. That way you avoid to plug and unplug endlessly without luck. Because in my case, if the flash show error, the driver stopped switching. If i would told you how many drivers and reebots I did have... (like 100?) :C
I had no phone for 3 days, the battery was full and when I revived it, it was 20ish... very strange. I will make a step by step guide, because I think that is the most important thing of the whole process.
So, once more. Thank you man. Reading you, that you took like a month with the 'common' problems made me less nervious.
Do you think you could edit that?
Something like i wrote you. Press the vol- until the phone wakes up the driver switching (MTK USB driver and MTK preloaded Vcom), and then press the download button, that way the phone flash will eventually start and you don't lose the conection because the driver keeps switching all the time (key point).
I think you don't have to change the com ports, but I was so desperate I did evertyhing i read in the whlole internet
Just one last question. IT was completely necessary to flash the recovery and the boot thing with the hexidecimals? Because after you flash the rom, you have already fastbot to flash the new recovery. I followed your steps, just asking.
See you here)
PS: Now im using miuisu_v6.0_x622_7.10.19, I tried the AOSP of kangburra, but I prefered to avoid exposed and tweaks I won't use. Very nice MIUI, first time in my life.
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 observe
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
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 observe
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
Last edited:
G
GuestD2478
Guest
Hi, same problem with X626, still trying... but having hope thanks to everybody adding information and files (blueasteroid!!!)
just to verify that i get two things right............
1) we need to make the driver switch to PRELOADER instead of COM 8 Port, right? because its switching between those two and keeps changing, but sometimes it gets stuck on COM Port only. To work with the SPFlashtool, it can ONLY work on Preloader - is that right?
and
2) i always get a BROM Error on SPFlashtool. is that the error everybody else gets aswell? just to verify that i'm stuck in the same boat with everybody, and not having a rare random error.........
So BROM Error ist normal?
Thanks guys and good luck everyone that is trying so hard to unbrick a LeEco phone......
just to verify that i get two things right............
1) we need to make the driver switch to PRELOADER instead of COM 8 Port, right? because its switching between those two and keeps changing, but sometimes it gets stuck on COM Port only. To work with the SPFlashtool, it can ONLY work on Preloader - is that right?
and
2) i always get a BROM Error on SPFlashtool. is that the error everybody else gets aswell? just to verify that i'm stuck in the same boat with everybody, and not having a rare random error.........
So BROM Error ist normal?
Thanks guys and good luck everyone that is trying so hard to unbrick a LeEco phone......
I think I installed the mediatek auto drivers, but I tried many versions.
Try to find the SP drivers mediatek 2.0.
If you connect the device and the drivers start switching it's good game. After you get the first red error (as I had many times), press the vol- button without disconect the device, after few seconds the phone 'wakes up' and the driver will be switching endlessly. Then, just try to flash in the time you hear the windows sound when the preloaded is active.
PS: I think it was vol-1 (if not, tell me because I'm editing a guide in spanish to solve this issue). Tell me when you can if it's vol - or vol - with power at same time.
Good luck. You will
Can someone tell me how to enter the usb driver which one should i choose (preload or da ...)
Okay, so I admit I skipped the documentation on this part but I will edit it when I have time.
So installing the drivers is a little bit tricky as you have to disable Signed Driver enforcement... If you're Win 10 like me you can use the following steps (Taken from the Packard bell website)
Click the Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
Once you've disabled signed driver enforcement, you can plug in the phone and assuming you 'woke up' your phone using the Power Vol- trick, it will try to install a generic USB driver that won't work for flashing. Once it's finished with the installation, that's when you can start replacing it
To do this, go to device manager, you will now see a new COM port with the generic driver installed, select it and right click, click on "update driver", go to "browse my computer for driver software", then click "Let me pick from a list of available drivers on my computer", then click on "Have Disk...", click on "Browse", select the Windows+10_MTK+VCOM+USB+Preloader+Drivers inf file, and you will now have the option to overwrite with the "MediaTek DA USB VCOM" driver. Let me know if I skipped any step as I'm kinda of doing this all from memory.
Note that there should be three drivers to choose of them. I tried all of them and the one that worked for me was "MediaTek DA USB VCOM". You can try the generic MTK driver too, I didn't have any luck with it, and for me the preloader driver did not work either...
So installing the drivers is a little bit tricky as you have to disable Signed Driver enforcement... If you're Win 10 like me you can use the following steps (Taken from the Packard bell website)
Click the Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
Once you've disabled signed driver enforcement, you can plug in the phone and assuming you 'woke up' your phone using the Power Vol- trick, it will try to install a generic USB driver that won't work for flashing. Once it's finished with the installation, that's when you can start replacing it
To do this, go to device manager, you will now see a new COM port with the generic driver installed, select it and right click, click on "update driver", go to "browse my computer for driver software", then click "Let me pick from a list of available drivers on my computer", then click on "Have Disk...", click on "Browse", select the Windows+10_MTK+VCOM+USB+Preloader+Drivers inf file, and you will now have the option to overwrite with the "MediaTek DA USB VCOM" driver. Let me know if I skipped any step as I'm kinda of doing this all from memory.
Note that there should be three drivers to choose of them. I tried all of them and the one that worked for me was "MediaTek DA USB VCOM". You can try the generic MTK driver too, I didn't have any luck with it, and for me the preloader driver did not work either...
Thank you for responding
Can you tell me when to press download (like before connecting the phone or when you hear the first sound that says usb is connected )
As you know the phone keeps connect and disconnect itself.
when I connect the phone (in the first connect and disconnect ) it shows me mediaTek usb port (COM10) ,but in the second Connect and disconnect it shows me MEDIATEK preloader USB VCOM (Android )(COM7)
You said I should update COM but which one (USB PORT OR PRELOADER USB VCOM ).
---------- Post added at 08:36 PM ---------- Previous post was at 08:09 PM ----------
Now after updated the mediaTek usb port it changed to mediaTek DA usb VCOM port
Last edited:
G
GuestD2478
Guest
okay i made it !!! the phone is back to life, i'm so happy !!!
All i did was switching DA_PL to DA_PL_HIGH and just kept trying the Power and Vol - pressing........ it suddenly finished and the phone screen went on! but the screen is mirrored now.
I read about this already from others, it should be not too hard to get rid of this :fingers-crossed:
All i did was switching DA_PL to DA_PL_HIGH and just kept trying the Power and Vol - pressing........ it suddenly finished and the phone screen went on! but the screen is mirrored now.
I read about this already from others, it should be not too hard to get rid of this :fingers-crossed:
stuck at last step. fastboot oem unlock are not allowed
tried other command not allowed too. seem like boot loader locked and device become and mirror version
anyone same with me ?
tried other command not allowed too. seem like boot loader locked and device become and mirror version
anyone same with me ?
Can someone please contact me and show me how to fix it
The sp flash tool part
The sp flash tool part
What worked for me was connecting the phone as soon as you hear the USB connection sound, so I would literally have the x626's USB plug hovering in front of the PC's USB port with my right hand, and with the mouse pointer hovering on download. So as soon as I plug and the connection sound comes out, I immediately press the download button.
If this doesn't work, one option is to hold down the Vol - button (no power button this time) when connecting in the phone and keep it held down. At first I thought I needed to do it but then it turned out that I could let go of the Vol - button and the outcome would be the same, again, try experimenting with that.
If this still doesn't work, then try different drivers. Like I said, the Preloader didn't do it for me but it worked for other people in the forum.
Last edited:
Congrats! Getting the screen to the mirrored state was the toughest part, but when the phone finally booted up for the first time it felt so good!
I believe another user calvin1982 has an issue when trying to get through the last part (which was odd as it was smooth sailing for me) - so do let us know if you run into the same problem (or not)!
Which part are you stuck at? Can you tell us what BROM error you're getting?
I believe Luckyrai posted the following a few posts ago on this thread:
"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"
I'm not sure what he means by all this as I didn't have this issue - but it seems to be related to the problem you're having. If you can get it fix based on this instruction do let all of us know so we can document the error and the solution!
@joebah, Before Bricking i was trying to install Custom ROM and suddenly Device Bricked, but OS was installed since OEM Unlock disabled itself, After SP Flash Method Device Mirrored, What i do is tried again and again hold the power button OS loads it was also mirrored, i enabled Developer Options and enabled OEM Unlock,After power off the device-Fastboot Mode- Run 刷机.bat It Unlocked Bootloader and installed Le ROM
Final Results - No Mirrored Device,Device Loads Le ROM but IMEI error, this was also the difficult part, i used Maui META ver 9.1724.0.00 method to Write IMEI
Will post my experience and Guide Soon
Thanks joebah without your guide it was not possible to unbrick
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone