Related
after unlock boot loader and root and instal boot.img phone doesn't open only vibration and dead
please please help my phone is dead and he is new for me
sorry for my lang
first your image is pretty low res that I can't see anything! but as far I saw everything get okey!
then just flash another boot.img. go to fastboot again flash another boot.img.
also be sure that you are flashing a really boot.img!! (which should be in elf format)
if you're willing to flash stock you can flash with flashtool and bring back your phone.
ALSO YOU MUST FLASH YOUR PHONE KERNEL not others this is pretty important.
sijav said:
first your image is pretty low res that I can't see anything! but as far I saw everything get okey!
then just flash another boot.img. go to fastboot again flash another boot.img.
also be sure that you are flashing a really boot.img!! (which should be in elf format)
if you're willing to flash stock you can flash with flashtool and bring back your phone.
ALSO YOU MUST FLASH YOUR PHONE KERNEL not others this is pretty important.
Click to expand...
Click to collapse
I had a same problem. would you give me atutorial from beginning?im really noob. about this problem... I dont know what have to do first
Please answer this question... if i had a same problem. but the worst thing is i still in lock bootloader? help me please
Getting back to stock
Download and install Flashtool by Androxyde. Remember to get 32 bit/64 bit version depending on your computer.
Download any stock firmware, preferably for your area/country and unmodified. Make sure it is the full firmware! It should be at least ~200 MB, but will probably be much larger if I remember correctly, maybe ~700 MB, though it maybe compressed inside a ZIP. You can get stock FW's on the forums, just look around. It should be in .ftf format.
Copy the .ftf file to "firmwares" folder, which is inside the Flashtool install folder. By default, this is C:\Flashtool.
Start Flashtool and keep it open. For 64 bit, you have to specifically choose the "Flashtool64" program.
Plug your USB cable into your computer, but not your phone.
Hold down the volume down key and plug the USB cable into your phone.
In Flashtool, look at the output window (the white space with all the log info) and one of the last entries should be "Device connected in flashmode" or something like that. If it says fastboot, repeat the process with the other volume key held down.
It may ask you to choose your device first. If so, choose Xperia ZR (obviously).
Click the button with lightning symbol on it. Select Flashmode and click OK.
You should see the file you downloaded in the list. Select it.
Make sure all the boxes in the "Wipe" section are checked, and all the boxes in the "Exclude" section are unchecked. DO NOT CHANGE ANY OTHER OPTIONS UNLESS YOU KNOW WHAT YOU ARE DOING!!!
Click "Flash". Wait for it to complete and hope that no errors come up. :fingers-crossed:
You should now have an out-of-the-box phone, software-wise. :good:
SirVer said:
Download and install Flashtool by Androxyde. Remember to get 32 bit/64 bit version depending on your computer.
Download any stock firmware, preferably for your area/country and unmodified. Make sure it is the full firmware! It should be at least ~200 MB, but will probably be much larger if I remember correctly, maybe ~700 MB, though it maybe compressed inside a ZIP. You can get stock FW's on the forums, just look around. It should be in .ftf format.
Copy the .ftf file to "firmwares" folder, which is inside the Flashtool install folder. By default, this is C:\Flashtool.
Start Flashtool and keep it open. For 64 bit, you have to specifically choose the "Flashtool64" program.
Plug your USB cable into your computer, but not your phone.
Hold down the volume down key and plug the USB cable into your phone.
In Flashtool, look at the output window (the white space with all the log info) and one of the last entries should be "Device connected in flashmode" or something like that. If it says fastboot, repeat the process with the other volume key held down.
It may ask you to choose your device first. If so, choose Xperia ZR (obviously).
Click the button with lightning symbol on it. Select Flashmode and click OK.
You should see the file you downloaded in the list. Select it.
Make sure all the boxes in the "Wipe" section are checked, and all the boxes in the "Exclude" section are unchecked. DO NOT CHANGE ANY OTHER OPTIONS UNLESS YOU KNOW WHAT YOU ARE DOING!!!
Click "Flash". Wait for it to complete and hope that no errors come up. :fingers-crossed:
You should now have an out-of-the-box phone, software-wise. :good:
Click to expand...
Click to collapse
Hi, i cant do that.. My flashtool give me a error:
16/021/2014 11:21:40 - ERROR - Drivers need to be installed for connected device.
16/021/2014 11:21:40 - ERROR - You can find them in the drivers folder of Flashtool.
I installed all it drivers, and nothing. It could be the Pc? or Firm? I need help pls.. Thx
Are you running Windows 8? If so, you need to disable the driver protection. Follow the steps mentioned here.
He says something about installing with "have disk." I have no idea what this means, as I used a different method that I don't remember right now. After you boot in test mode as instructed, simply running the installer as you did before should work. Also, there's no need to install all the drivers. I don't know for sure, but it may be bad to have all the drivers installed. Maybe. In any case, you only need to install the "Common ADB drivers for Lagan, Fusion3 board devices based on APQ8064 chipset: Xperia Z, ZL, ZR, ZQ, A, UL, Tablet Z." It should be there in the driver install menu. If that doesn't work, install all of them.
If this doesn't work, or you're not on Windows 8, then download the latest FlashTool driver pack here. Actually, you should do that anyway, before everything else. Best to have the latest drivers when experimenting. The latest version is v1.5, at the time of writing. If yours is v1.5, leave it be.
If that doesn't work, then... Nope, I got nothing. If none of this works, ask an experienced dev for help, or give it to Sony service. They'll probably charge you quite a bit, so be prepared for that.
Hope this helps.
SirVer said:
Are you running Windows 8? If so, you need to disable the driver protection. Follow the steps mentioned here.
He says something about installing with "have disk." I have no idea what this means, as I used a different method that I don't remember right now. After you boot in test mode as instructed, simply running the installer as you did before should work. Also, there's no need to install all the drivers. I don't know for sure, but it may be bad to have all the drivers installed. Maybe. In any case, you only need to install the "Common ADB drivers for Lagan, Fusion3 board devices based on APQ8064 chipset: Xperia Z, ZL, ZR, ZQ, A, UL, Tablet Z." It should be there in the driver install menu. If that doesn't work, install all of them.
If this doesn't work, or you're not on Windows 8, then download the latest FlashTool driver pack here. Actually, you should do that anyway, before everything else. Best to have the latest drivers when experimenting. The latest version is v1.5, at the time of writing. If yours is v1.5, leave it be.
If that doesn't work, then... Nope, I got nothing. If none of this works, ask an experienced dev for help, or give it to Sony service. They'll probably charge you quite a bit, so be prepared for that.
Hope this helps.
Click to expand...
Click to collapse
So thx! i was on win8, now im trying in win7.. but i have other problem now -.-"!.. The flashtool start with the flash, but dont move, just stay on 0%.. :c.. What hapen now..?
(Srry for my english ><..)
------------
Ready, i rapared it. Just install the last flashtool version. And it work. So thx!! My zr IS LIVE! xD
Glad I could help. If you haven't already, please hit that thanks button. ?
Also, in the future, please search more thoroughly for your answers. Most of this is there on the forums, if you look for it. I'm not trying to be mean, it's just a reminder. ?
If anyone has been paying attention to any of my threads you'd know i've been having a horrible time trying to get my LG G4 to work. After much trouble of not being able to connect my phone to the computer via download mode ( driver wont start , code 10) my cyanogenmod recovery magically allowed me to install the supersu zip to root the system, and finally the global root access option in cm13 worked which enabled me to install an app and flash twrp. From here I was able to download prometheus rom, and install it from twrp because the cm recovery kept giving me errors., ran smoothly.. was able to get all of my downloaded apps retrieved via google. I reboot the phone this morning after deleting some un wanted apps I had now i'm getting ' secure boot error 1003" and will not boot past the Lg screen. I am really at a lost here and would appreciate it if someone would take the time out to help me. Now I am totally screwed because I cant get windows to install the download mode driver correctly as there is a yellow exclamation mark next "LGE Android MTP device" with a code 10. That is important because adb/fastboot wont recognize the device unless this driver is running and working. I mean sheesh ive tried this on three computers and cant get this da*n driver to install, really? am i seriously missing something? lg software wont even recognize my phone unless its in download mode and even then, will fail to run because * the device can not start* so the software shuts down
Please, help. and if any suggestions, please provide tutorials to back it up.
Sunaj1 said:
If anyone has been paying attention to any of my threads you'd know i've been having a horrible time trying to get my LG G4 to work. After much trouble of not being able to connect my phone to the computer via download mode ( driver wont start , code 10) my cyanogenmod recovery magically allowed me to install the supersu zip to root the system, and finally the global root access option in cm13 worked which enabled me to install an app and flash twrp. From here I was able to download prometheus rom, and install it from twrp because the cm recovery kept giving me errors., ran smoothly.. was able to get all of my downloaded apps retrieved via google. I reboot the phone this morning after deleting some un wanted apps I had now i'm getting ' secure boot error 1003" and will not boot past the Lg screen. I am really at a lost here and would appreciate it if someone would take the time out to help me. Now I am totally screwed because I cant get windows to install the download mode driver correctly as there is a yellow exclamation mark next "LGE Android MTP device" with a code 10. That is important because adb/fastboot wont recognize the device unless this driver is running and working. I mean sheesh ive tried this on three computers and cant get this da*n driver to install, really? am i seriously missing something? lg software wont even recognize my phone unless its in download mode and even then, will fail to run because * the device can not start* so the software shuts down
Please, help. and if any suggestions, please provide tutorials to back it up.
Click to expand...
Click to collapse
This happened to me last night. I tried to "relock" the bootloader. I had to put the phone in download mode, and recover using LG bridge. I found several different ways to accomplish the download mode listed but only one worked., i believe it was here. http://www.androidexplained.com/lg-g4-how-to-boot-into-download-mode/
I used these directions mostly but did one thing a little differently
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Instead of using the KDZ files, I used lg bridge. Once i was actually in download mode, and lg bridge recognized my phone, i went the the software update tab and clicked on the error recovery, the tool downloaded the proper rom, installed in and I was back to stock, no root.
Take the cover off of your battery, have a good usb cable handy. I had to remove the battery, hold the buttons and start over several times before I got it to work, but I did.
Good luck.
happimeal said:
This happened to me last night. I tried to "relock" the bootloader. I had to put the phone in download mode, and recover using LG bridge. I found several different ways to accomplish the download mode listed but only one worked., i believe it was here. http://www.androidexplained.com/lg-g4-how-to-boot-into-download-mode/
I used these directions mostly but did one thing a little differently
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Instead of using the KDZ files, I used lg bridge. Once i was actually in download mode, and lg bridge recognized my phone, i went the the software update tab and clicked on the error recovery, the tool downloaded the proper rom, installed in and I was back to stock, no root.
Take the cover off of your battery, have a good usb cable handy. I had to remove the battery, hold the buttons and start over several times before I got it to work, but I did.
Good luck.
Click to expand...
Click to collapse
Thanks so much. Hopefully I can get this to work, if I can get the PC to see the LGE MTP download mode driver then the rest is golden. Will keep things updated. Will try when I get home.
happimeal said:
This happened to me last night. I tried to "relock" the bootloader. I had to put the phone in download mode, and recover using LG bridge. I found several different ways to accomplish the download mode listed but only one worked., i believe it was here. http://www.androidexplained.com/lg-g4-how-to-boot-into-download-mode/
I used these directions mostly but did one thing a little differently
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Instead of using the KDZ files, I used lg bridge. Once i was actually in download mode, and lg bridge recognized my phone, i went the the software update tab and clicked on the error recovery, the tool downloaded the proper rom, installed in and I was back to stock, no root.
Take the cover off of your battery, have a good usb cable handy. I had to remove the battery, hold the buttons and start over several times before I got it to work, but I did.
Good luck.
Click to expand...
Click to collapse
bro, thanks for taking the time to write this out. Not sure what I was doin wrong before, but i was able to flash back to stock
Hi there,
perhaps you guys can help me
I use a onePlus 3T 128GB and directly after delivery I update the OS, install twrp, make a clean backup and then personalized the phone.
Runs quite good but yesterday I wanted to update the system to 4.0 Nougat...
So I downloaded the full installer, backuped the full current system via twrp and then flash and install the 4.0 version.
Yeah... doesn't work really good...
After the Pin and the code for the sim card, the OS ask for a third pin code but none of both works. And I never have another pin code since years...
Then I wipe the cache and system with twrp and restore the last backup. Doesn't work. It only boots to the onePlus Logo and then nothing happens.
Same for the first clean backup without any personalisation...
For now I have an great smartphone that doesn't work... yayy...
Anyone of you has an idea how can I get my running phone back – with all my data and apps?
Edit1: adb sideload doesn't work
Edit2: Full Installer installed >> reboot >> no OS installed
Thanks for all guys.
Oliver
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
You said you wiped your system..
what did you expect?
use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
raj7749 said:
use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
No, it doesn't work
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Jo_Jo_2000 said:
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
When wiping system before installing a full roms zip (not only an incremental update), I would expect a working, os containing partition - like on the oneplus one (did that many times on bacon). But I can confirm, it's not working on opt3; at least not with oos4. In this case I need to restore working systemmpartition (from twrp-3.0.3-0), and flash then the rom zip.
current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:
GammarursPulex said:
current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:
Click to expand...
Click to collapse
Would you try the following: From twrp restore your very first backup (firmware, system and boot), don't leave twrp and wipe (reformat with f2fs) data (I'm talking of the entire userdata partition, not only "wiping data without wiping media"); flash the full oos4 zip (the one with 1.4GB); don't leave twrp, go to Advanced->copy logfile. Try to boot system.
If the system stiil refuses to boot up completly, get the logfile with adb via twrp and show us.
DO NOT try this, without usb-c otg cable and usb stick, because you are reformating your data partition. That's the reason I have not tried this: need to get an usb-c otg cable (BTW: recommendations on usb-c otg cables welcome, but OT: so PM).
GammarursPulex said:
No, it doesn't work
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me
mcdachpappe said:
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me
Click to expand...
Click to collapse
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.
GammarursPulex said:
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.
rms4067 said:
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.
Click to expand...
Click to collapse
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience
GammarursPulex said:
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience
Click to expand...
Click to collapse
When you say load the backup, you mean a backup that you made in TWRP recovery, prior to bricking your phone?
My experience with the unbricking guide was that it in essence did a full wipe and reset (including the recovery partition). That would eliminate TWRP from your phone as well as any stored backups you had.
When I unbricked, I opted to just leave it stock as nougat was around the corner.
I also re-read your original post. I wouldn't have considered your phone "bricked" at that point.
I would bet that you could have booted the phone into TWRP.
You'll want to keep these things in mind too for future TWRP encryption issues (it's a known issue that most likely won't be fixed).
1) before you make a twrp backup, remove any figerprints/pins/passwords from your device, sometimes prevents issues for me
2)if you existing pins/passwords don't work try "default_password" that may work
3)if all else fails, boot into twrp, navigate to /data/system/ and down the list will be a few files to delete
- password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
4) the last step is always the first step for me, too many issues with twrp and encryption
GammarursPulex said:
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.
Click to expand...
Click to collapse
u r doing something wrong.. please follow guide correctly
It works 100℅
Just out of curiosity, did you unlock the bootloader before you did everything? Also did you go into settings -->developer mode and turn on OEM unlock and USB debugging?
From my experience, try wiping everything through twrp --> install the firmware/backup --> and then try doing another wipe and reboot. Now I understand you might lose your root/SU after wiping, but perhaps this will at least boot into the system for you.
If all else fails, try using ODIN and flash your stock firmware http://downloads.oneplus.net/devices/oneplus-3t/
EDIT:
If you're having driver issues try this.
1. Go into device manager (as admin)
2. Double click the device that you're having trouble with
3. Click on "Details" tab
4. Under "Property" dropdown, choose "Hardware Ids"
5. When you select that you should see a bunch of values under there. Right click the first one and copy it.
Ex:\ I have an S7 phone so mine looks like "USB\VID_04E8&PID_6860&REV_0400&ADB"
6. Now the value you copied, try searching it in google. Or paste it on here for us to help you find drivers compatible with it. Usually you can find compatible drivers in google. Once you find them and download them, if you go back to that device and click "Update Driver" you can manually point to the extracted drivers. It will find the compatible *.inf file and install it for that device.
Hope this helps!
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
this works for me, every time i kill my 3T.
you must be doing something wrong.
Follow everyline
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
If you can flash/boot into TWRP, then probably nothing is lost. While in TWRP, if you connect your phone with PC, what happens? Do you hear the usual USB connection sound? If yes, what appears in the device manager?
Even if it doesn't appear in device manager, don't worry.
Boot into TWRP, go to storage, DISABLE MTP and enable it again. I know it sounds dumb, but just try it. It will be recognized as long as you have the proper drivers installed.
After that copy the zip of an OxygenOS based ROM like FreedomOS and flash it. Don't wipe anything. It will boot fine. I've done that a few times, never had a problem.
Thanks for the advice guys - no, no sound, nothing - as I said, I only get the charging (+) icon in twpr next to the battery percentage.
I did disable and enable MTP before - although not plugged in a pc during the process - will try if I have the chance.
One more thing that might ring a bell for someone - I tried the key combo for hard reset today(power + vol down) for a couple second and moments later I got a fuzzy (random colored pixels) screen and a red led. Weird, if you ask me.
P.S.: Today I tried to chat with OP a bit - 230 Eur for a new MB (64GB) and 255 Eur for my 128GB version - I just wanted to know, I'm still not admitting failure though. But as a student, these numbers from the support literally hurt me when reading...
grello said:
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
Click to expand...
Click to collapse
1) try to update the twrp to the official 3.1.1.0. Then flash the latest modem firmware for your device and try to flash a custom rom like lineage os (a 7.x rom)
If you connect the phone to PC in TWRP and your phone is not recognized, chances are good that either your phone's USB or the cable (or the USB port on the computer) is not working. You can try to download the adb driver installer from here, just to check if your phone is listed by the installer: http://adbdriver.com/downloads/
Update - tried the MTP Enable/disable option in TWRP (in the Mount menu) while plugged into the PC, with no luck
IvanPrince - have you actually read the description of my problem? I have the 3.1.1-0 and even if not, how should I actually flash another version of twrp? The problem here is I cannot seem to find a WAY how to flash ANYTHING on the device.
I'll see about the adb drivers and update.
Thanks all,
Does the phone show up as anything on the PC when you boot to fastboot? I re-read but didn't see anything about it.
Nope - nothing. By now, I believe it is a hardware problem as the phone indeed got wet before my mistake with the advanced wipe. It appears to work just fine though, apart from the connectivity issue, so I believe the MB should be ok as everything else, including the screen is.
I just have one, perhaps a little courageous thing I'd like to ask from someone kind enough. Anyone with a Oneplus 3 or 3T who's not afraid to open the phone for a couplne minutes and has a multimeter alongside with a USB cable should be able to help me. :angel:
Could you, my awesome stranger, check where the 4 USB pins (on the side where you plug them into the PC) lead (make contact/'BEEP' on the multimeter) with the actual phone motherboard? It would REALLY help me in troubleshooting and perhaps saving 250 Eur. So far, I have this: (same color means contact) at that point. See picture.
BLACK - GND (all the heatsinks are connected to GROUND as well)
GREEN - DATA +
YELLOW - DATA -
RED - VCC
If anyone decides to open up their phone and help out a fellow xda guy, it will be greatly appriciated. :angel:
Hey Bro I was curious to know if you tried this method of recovering from a hard brick... When I first got my 3t something similar happened to me. I can't remember all the details of my hard brick but I thought I was f***ed. Please try this if you have not already.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Might be a dumb question, but you did remember to mount the USB when you connected the otg right?
If the bootloader is unlocked, you can save it.
I would flash the stock recovery and the latest factory image (4.1.7)
Download them both from here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
After flashing the stock recovery using fastboot, boot to stock recovery and sideload through ADB the stock factory image.
Reboot and after checking that everything is working fine, feel free to relock the bootloader if you wish to stay 100% stock.
If the computer doesn't recognize it at all then it's a driver problem, not the phone... at least that's what I think.
try to use the program to fix my oneplus 3t it said download complete. try to restart
try to use the program to fix my oneplus 3t it said download complete. try to restart it and can press the screen and it keep rebooting it like the screen is frozen
please help me out
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