Related
So as you may already be aware phones like mine, (orange uk) have the fastboot locked down, and so we cant unlock the bootloader.
I for one believe it can be accessed but needs a little bit of time and research on getting it done.
This thread is aimed for brain-storming for ideas and collecting them for us to try out,
You can de-brand your phone by flashing the software from this thread
http://forum.xda-developers.com/showthread.php?t=1033193
thanks to scott4 for the first upload mirror on page 3
Any ideas on getting the bootloader up and going on locked devices please put them in here
UPDATES
We now have root access thanks to Chainfire's gingerbreak apk which is here
http://forum.xda-developers.com/showthread.php?t=1044765
If your getting "could not extract assets" from gingerbreak
try doing
xperiax10.awesome said:
cool, finally I rooted my xperia ARC
these are very simple steps(copied from different threads):
1. Install the attached apk: Gingerbreak-v1.00
after installing most people getting this error - "could not extract assets".
TO OVERCOME THIS, just copy the attached ADB.zip and extract it on your laptop (windows)
say at
E:\mobile_Xperia\ADB
goto above path in your cmd promt and types these lines (your phone should be connected to laptop in debugging mode)
E:\mobile_Xperia\ADB>adb shell rmdir /data/local/tmp
E:\mobile_Xperia\ADB>adb shell mkdir /data/local/tmp
NOW JUST INSTALL THE apk file again and click on ROOT
Click to expand...
Click to collapse
if that Fails try replacing it with rm -r /data/local/tmp
Update 2
Blagus has kindly opened up this thread here
http://forum.xda-developers.com/showthread.php?t=1063394
We need people with a SIM-FREE phone with a LOCKED bootloader to help us all out, so if thats YOU !!!
Help us poor sods with branded handsets please.
UPDATE 3
Blagus Has come out with his release (As the man who can)
Blagus said:
Omnius for SE v0.23 (30th August 2011)
Added unlocking of S1 MSM7x30 GSM/UMTS phones (testpoint connection to GND is required.)
Added bootloader unlocking for S1 MSM7x30 phones
Anyone who donated (+punk... sorry forgot username, the OP ), contact me for free unlock.
For rest, contact for price (cheaper than at official Omnius resellers).
Click to expand...
Click to collapse
You can contact him here http://forum.xda-developers.com/member.php?u=2645841
Instructions
TESTPOINT INSTRUCTIONS PROVIDED BY mooxie FROM XDA FORUM:
1 turn of the phone
2 take of the backcover
3 remove the battery and sim card
4 take of the plastic covering the test point it's a bit stuck there but the gentle if you can.
5 Find something flexible like a wire or so i used steel wire. Make bend it so you easily can put it on the test point and the ground since you need to hold it there and press the powerbutton in the next step.
6 put in the battery
7 put the wire on the test point and the ground keep it there and press the power button for a few seconds. You wont get any confirmation that it suceeded.
8 Plug in the usb cable in the phone. Windows will now search for a new driver.
If it doesn't install automaticly. Go into the device manager of windows and look up something called SEMC_HUBB think it was that name. Choose update driver and browse to your omnius\driver folder. You will get a warning that the driver isn't signed but press okay and it should install.
9 Now if everything is done right the flashing will start and you should soon have an unlocked phone
Also side note i had problems with
qhsusb_dload driver not installing correctly.
if this is your case right click update and point to the omnius folder and choose update. worked for me.
Have you tried connecting via ADB, and running the command "adb reboot fastboot"?
dh2311 said:
Have you tried connecting via ADB, and running the command "adb reboot fastboot"?
Click to expand...
Click to collapse
What does this command does beside going to the fastboot?
Rithina said:
What does this command does beside going to the fastboot?
Click to expand...
Click to collapse
Well if we can get into fastboot we can unlock the kernal, for the people stuck with not being able to do the normal way
dh2311 said:
Have you tried connecting via ADB, and running the command "adb reboot fastboot"?
Click to expand...
Click to collapse
Reboots back up as normal, also did adb devices and it was there,
Have you tried removing the simlock?
MarylandCookie said:
Have you tried removing the simlock?
Click to expand...
Click to collapse
No not sure how to do it for free, i think someone with a Japaneses version has removed it, i will PM him to ask him
Here's a thought: backup TA. Write random values to security area. If fastboot is disabled/enabled depending on TA simlock info, tampered sec. zone could give you fastboot. Then unlock bootloader and in order to get your phone back to life, restore TA.
Method should be 100% safe as long as you can write TA back.
Sent from my X8 using XDA App
Tampered units wont let the phone boot.
lollylost100 said:
Tampered units wont let the phone boot.
Click to expand...
Click to collapse
But what about flash mode and fastboot? I know they won't boot but that's why in the end TA is restored.
so now all you crazy kids with unlocked phones have root I dont suppose anyone has any more ideas about this problem do they?
I have a few more ieas;
1) I presume you have also tried
adb reboot bootloader
I haven't got my arc yet, Im just saying old ways of getting DHD into bootloader/fastboot
2)
Also, what i think was being mentioned above, Im not too sure what was being said, but on advent vega's and optimus 2x's if you wiped the boot partition, it rebooted into fastboot, because there was no OS installed.
3)
Another one to try is look for market apps that offer reboot into recovery type options and see if they work
have you tried booting your device using the S1 BOOTLOADER method and the S1 DOWNLOAD method? (power off, hold menu + plug battery, then plug cable in pc) you should see a blue LED light. (power off, hold back key + plug battery, then plug cable in pc) you should see a green LED light.
try these two methods and give us a feedback
kazuni said:
have you tried booting your device using the S1 BOOTLOADER method and the S1 DOWNLOAD method? (power off, hold menu + plug battery, then plug cable in pc) you should see a blue LED light. (power off, hold back key + plug battery, then plug cable in pc) you should see a green LED light.
try these two methods and give us a feedback
Click to expand...
Click to collapse
manage to get Green light to come up, and it installs drivers
SEMC Flash Devices installs as the drivers,
After the installation of the new drivers still no blue light
adb reboot bootloader just reboots as normal
Hi !
For me, first method makes my phone booting normaly (no led light).
With the second one, it's OK : green led light appears.
If i can help...
PS : my PC doesn't want to install drivers :-(
punkmonkey1984 said:
manage to get Green light to come up, and it installs drivers
SEMC Flash Devices installs as the drivers,
After the installation of the new drivers still no blue light
Click to expand...
Click to collapse
so that means SEMC Flash is available. Try using Flashtool and flash a UK/Global firmware, and see if it works =)
Skyseb said:
Hi !
For me, first method makes my phone booting normaly (no led light).
With the second one, it's OK : green led light appears.
If i can help...
PS : my PC doesn't want to install drivers :-(
Click to expand...
Click to collapse
Download SEUS. PC Companion doesn't install the right drivers.
kazuni said:
so that means SEMC Flash is available. Try using Flashtool and flash a UK/Global firmware, and see if it works =)
Click to expand...
Click to collapse
Already flashed global firmware,
Still locked,
I guess the lock is actually in the bootloader level, which can't be overridden by writing a ftf package.
Sorry, but no other ideas at the moment =\
??? Have you seen this post ? => http://forum.xda-developers.com/showpost.php?p=13064854&postcount=420
Edit : ok, forget it...
Sorry.
Hi all, I'm new here and very much a novice when it comes to phones, operating systems etc so excuse me for the noob question and complete lack of knowledge...
My Xperia T developed a microphone fault whereby nobody could hear me when I called them (incredibly faint). I had the phone repaired at a local repair shop. Almost immediately upon receiving the phone back it developed a (What appears to be very common) battery fault, whereby it would reach 80% then shut down, restart, shut down, restart......
So, before returning it to the shop for further repairs I attempted a repair using the sony software. Half way through this repair the phone shut down!!! PC lost communication and I was left with a phone that simply displayed the 'Sony' start-up logo.
I have now returned to the shop and they have installed a new battery but are unable to get communication with the phone via the sony software (so basically they dont appear to be getting any further than me!). They are saying it is beyond repair - but I find that hard to believe? Surely it is just a software issue?
Can anyone advise what can be done? I am reluctant to write this phone off - surely it can be flashed with a new operating system or whatever needs to be done to what is essentially now a 'dumb' device?
This is the way to fix the software issue, ALL YOU DATA WILL BE LOST. And i'm not responsible for anything might happen to you device . DO THIS AT YOUR OWN RISK.
Google xperia t .145 ftf file
Google flashtool for xperia
Download them
When you have installed flashtool, go to its folder, install drivers (tick the TX, flashmode and fastboot drivers boxs)
Open flashtool, click the lightning logo, select flashmode
Put the firmware file you've downloaded to the firmware folder in flashtool folder.
Connect the phone in flashmode, hold power and volume up until it vibrates 3 times, now hold the vol down, plug your phone in the computer with flashtool running, you will now able to flash the firmware.
Good luck man.
tuzmaster_v2 said:
This is the way to fix the software issue, ALL YOU DATA WILL BE LOST. And i'm not responsible for anything might happen to you device . DO THIS AT YOUR OWN RISK.
Google xperia t .145 ftf file
Google flashtool for xperia
Download them
When you have installed flashtool, go to its folder, install drivers (tick the TX, flashmode and fastboot drivers boxs)
Open flashtool, click the lightning logo, select flashmode
Put the firmware file you've downloaded to the firmware folder in flashtool folder.
Connect the phone in flashmode, hold power and volume up until it vibrates 3 times, now hold the vol down, plug your phone in the computer with flashtool running, you will now able to flash the firmware.
Good luck man.
Click to expand...
Click to collapse
Thankyou very much for your reply!! Thats what I need, a step by step muppets guide!
To be honest I couldn't care less about any data, I'm way past that stage - if I can just have the phone working again I would be a very happy man (I'm fairly desperate as you can probably tell, Im running my business from an ancient, failing HTC desire following weeks of the shop having the sony!). I can't really afford to write off a phone I paid good money for 6 months back so need to have a go myself.
I am collecting the phone today so will give that a go.....
So I had a go at the above - got the flash tool installed (Emma?) etc and managed to get the software to see the phone - unfortunately though I had neglected to mention the phone is locked to a particular network, which Emma politely informs me.
So, I have attempted to follow unlocking instructions as per the sony instructions (on their website):
But I am stuck. I was getting nothing when using the volume down button and connecting. To get the computer to see the phone I have to press and hold the power button, the red led starts blinking 3 times, repeatedly. This causes windows to recognise the phone when plugged in via usb, but I was not being asked for drivers (as per sony step 13). I found the device in device manager and uninstalled drivers in an attempt to force this. Now all that happens is the device appears in the list as 'S1 Boot Load' with a yellow exclamation mark. However I have then tried installing drivers manually from the location where I copied 'android_winusb' to, but this does not work.
To compound the issue I think the battery problem is causing the phone to cycle. when connected the green led lights up for a bit, but then goes off, then back on, then red.....repeatedly. The device only appears in device manager as 'S1 boot load' when green. This gives a very short window to try to do anything.
Wrong flashtool, download the one from the Dev section and flash a stock FTF
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Wrong flashtool, download the one from the Dev section and flash a stock FTF
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh right, first mistake then. The phone will still need unlocking first though I assume?
FASTdan2 said:
Oh right, first mistake then. The phone will still need unlocking first though I assume?
Click to expand...
Click to collapse
No, flashing a stock firmware works with locked bootloader
FASTdan2 said:
Oh right, first mistake then. The phone will still need unlocking first though I assume?
Click to expand...
Click to collapse
St.Jimmy90 said:
No, flashing a stock firmware works with locked bootloader
Click to expand...
Click to collapse
You do not even need root.
FASTdan2 said:
So I had a go at the above - got the flash tool installed (Emma?) etc and managed to get the software to see the phone - unfortunately though I had neglected to mention the phone is locked to a particular network, which Emma politely informs me.
So, I have attempted to follow unlocking instructions as per the sony instructions (on their website):
But I am stuck. I was getting nothing when using the volume down button and connecting. To get the computer to see the phone I have to press and hold the power button, the red led starts blinking 3 times, repeatedly. This causes windows to recognise the phone when plugged in via usb, but I was not being asked for drivers (as per sony step 13). I found the device in device manager and uninstalled drivers in an attempt to force this. Now all that happens is the device appears in the list as 'S1 Boot Load' with a yellow exclamation mark. However I have then tried installing drivers manually from the location where I copied 'android_winusb' to, but this does not work.
To compound the issue I think the battery problem is causing the phone to cycle. when connected the green led lights up for a bit, but then goes off, then back on, then red.....repeatedly. The device only appears in device manager as 'S1 boot load' when green. This gives a very short window to try to do anything.
Click to expand...
Click to collapse
I've been dealing with a similar problem. When connected to a wall charger is your phone cycling from Green to Red and keeps doing that? Also have you installed Sony PC Companion maybe your phone will get recognized from the drivers in that install.
Same problem
Hi, I am currently having the same problem. I have tried to use flashtools and I've got all the necessary drivers (I think) but once I put hold power button and vol+ (3 vibrations), then press vol-, connect to pc via USB and I get a temporary green led, which goes after about 5 seconds, and then my phone disconnects from my computer again. I really need my phone to work Could someone out there please help with this! I would really appreciate if someone responded very soon as I would like to get this sorted as soon as possible. Flashtools gives me these messages:
22/012/2013 23:12:07 - INFO - Device disconnected
22/029/2013 23:29:07 - INFO - Device connected in flash mode
22/029/2013 23:29:18 - INFO - Device disconnected
Also one more thing i'd like to add.. Once I go into that BLU thing, it keeps on asking me what device I have, so I select Xperia T and then it gives the following messages:
22/052/2013 22:52:26 - INFO - Your phone bootloader cannot be officially unlocked
22/052/2013 22:52:26 - INFO - You can now unplug and restart your phone
Might this have something to do with it? Any suggestions would be grateful! I've been at this for hours now and need to get this sorted
Thanks to any kind person who helps fix this!
Hi, I have tried to use flashtools and I've got all the necessary drivers (I think) but once I put hold power button and vol+ (3 vibrations), then press vol-, connect to pc via USB and I get a temporary green led, which goes after about 5 seconds, and then my phone disconnects from my computer again and i get a constant red led while the Sony logo appears. I really need my phone to work Could someone out there please help with this! I would really appreciate if someone responded very soon as I would like to get this sorted as soon as possible. Flashtools gives me these messages:
22/012/2013 23:12:07 - INFO - Device disconnected
22/029/2013 23:29:07 - INFO - Device connected in flash mode
22/029/2013 23:29:18 - INFO - Device disconnected
Also one more thing I'd like to add.. Once I go into that BLU thing, it keeps on asking me what device I have, so I select Xperia T and then it gives the following messages:
22/052/2013 22:52:26 - INFO - Your phone bootloader cannot be officially unlocked
22/052/2013 22:52:26 - INFO - You can now unplug and restart your phone
Might this have something to do with it? Any suggestions would be grateful! I've been at this for hours now and need to get this sorted
Thanks to any kind person who helps fix this!
1) Dial *#*#7378423#*#* and goto software info/configuaration. If it says bootloader unlocked allowed: no, then you CANNOT unlock it via ANY means
2) If it says yes (I doubt it, because flashtool has already checked this) then you can.
3) Flashmode has nothing to do with bootloader. Press volume up to get into fastboot (Blue LED) for working with bootloader, press volume down (Green LED) to work in flashmode, which is for flashing FTF's.
4) If you are trying to flash a FTF, then do not connect the phone until it asks
5)Make sure you have gone to C:\flashtool\drivers and run drivers.exe. Ensure you choose fastboot, flashmode and TX drivers.
6) Make sure you are on the latest version of flashtool 0.9.13.1
Can I ask what you are actually trying to do?
Also flashmode and fastboot and adb dont work on windows 8(.1)
gregbradley said:
1) Dial *#*#7378423#*#* and goto software info/configuaration. If it says bootloader unlocked allowed: no, then you CANNOT unlock it via ANY means
2) If it says yes (I doubt it, because flashtool has already checked this) then you can.
3) Flashmode has nothing to do with bootloader. Press volume up to get into fastboot (Blue LED) for working with bootloader, press volume down (Green LED) to work in flashmode, which is for flashing FTF's.
4) If you are trying to flash a FTF, then do not connect the phone until it asks
5)Make sure you have gone to C:\flashtool\drivers and run drivers.exe. Ensure you choose fastboot, flashmode and TX drivers.
6) Make sure you are on the latest version of flashtool 0.9.13.1
Can I ask what you are actually trying to do?
Click to expand...
Click to collapse
Its not even booting, past the Sony logo so i cannot do anything (i can't do step 1 as you've asked). Its literally a bootloop. Can you give me step-by-step instructions to get out of this bootloop? I tried to install custom ROM but it died on me, and now its on the bootloop, which i can't get passed.
hhamzah49 said:
Also flashmode and fastboot and adb dont work on windows 8(.1)
Click to expand...
Click to collapse
Oh okay. I'm using windows 8.1, so what would I do to fix the issue?
I have given my phone to the manufacturers to try and sort out but I have a feeling they will refuse to fix it, so any help would be appreciated. If i use a windows 7 machine, would it work? If so, how do I fix it such that it exits bootloop and allows me to access my phone. I don't mind losing all my data (although i think its lost anyway lol)
P.S. thanks for the reply.
fizstarrr said:
Oh okay. I'm using windows 8.1, so what would I do to fix the issue?
Click to expand...
Click to collapse
use windows 7 or linux. i read about problems with win8.1 too. thats why i not updated my win8 yet.
immerblind said:
use windows 7 or linux. i read about problems with win8.1 too. thats why i not updated my win8 yet.
Click to expand...
Click to collapse
Question is, will is definitely work if i use windows 7? I.e. is the fact that i'm using windows 8.1 the reason why it's not working?
fizstarrr said:
Hi, I have tried to use flashtools and I've got all the necessary drivers (I think) but once I put hold power button and vol+ (3 vibrations), then press vol-, connect to pc via USB and I get a temporary green led, which goes after about 5 seconds, and then my phone disconnects from my computer again and i get a constant red led while the Sony logo appears. I really need my phone to work Could someone out there please help with this! I would really appreciate if someone responded very soon as I would like to get this sorted as soon as possible. Flashtools gives me these messages:
22/012/2013 23:12:07 - INFO - Device disconnected
22/029/2013 23:29:07 - INFO - Device connected in flash mode
22/029/2013 23:29:18 - INFO - Device disconnected
Also one more thing I'd like to add.. Once I go into that BLU thing, it keeps on asking me what device I have, so I select Xperia T and then it gives the following messages:
22/052/2013 22:52:26 - INFO - Your phone bootloader cannot be officially unlocked
22/052/2013 22:52:26 - INFO - You can now unplug and restart your phone
Might this have something to do with it? Any suggestions would be grateful! I've been at this for hours now and need to get this sorted
Thanks to any kind person who helps fix this!
Click to expand...
Click to collapse
I'm sure your batt is dead. Try the rubber band method. Give it like 2/3 rounds of it on the power button and hold it and plug in charger. it should charge with red led on. Pull battery and try again if it does not charge. Give it some charging and it should be able to enter flashmode to flash stock.
Unknownkj said:
I'm sure your batt is dead. Try the rubber band method. Give it like 2/3 rounds of it on the power button and hold it and plug in charger. it should charge with red led on. Pull battery and try again if it does not charge. Give it some charging and it should be able to enter flashmode to flash stock.
Click to expand...
Click to collapse
I don't think the battery is dead, as the led would just blink and wouldn't even show me the Sony logo.. Everytime i use the phone with the charger it goes into the bootloop, looping around the Sony logo and then switching off again, then the sony logo will show again, etc. I've sent it off to Sony manufaturers. Would they fix it (even if the manufacturers warranty is void)? Like, even if they charge a little (hopefully not stupid amounts of money lol)? If not, i'm going to try and use flashtool on windows 7 machine and hope that it works, as I've heard flashmode and fastboot and adb do not work on windows 8(.1), which is what im currently using :crying:
fizstarrr said:
I don't think the battery is dead, as the led would just blink and wouldn't even show me the Sony logo.. Everytime i use the phone with the charger it goes into the bootloop, looping around the Sony logo and then switching off again, then the sony logo will show again, etc. I've sent it off to Sony manufaturers. Would they fix it (even if the manufacturers warranty is void)? Like, even if they charge a little (hopefully not stupid amounts of money lol)? If not, i'm going to try and use flashtool on windows 7 machine and hope that it works, as I've heard flashmode and fastboot and adb do not work on windows 8(.1), which is what im currently using :crying:
Click to expand...
Click to collapse
Hello. Have you tried hard reset?
Press power button and vol up key together until it vibrates. Phone should start up?
Sent from my LT30p using xda premium
fizstarrr said:
Question is, will is definitely work if i use windows 7? I.e. is the fact that i'm using windows 8.1 the reason why it's not working?
Click to expand...
Click to collapse
Yes (or, at least its definitely one of the reasons). Use Win 8 or Win 7 or Win XP.
If after that point you still have trouble with it sticking to flashmode: I also had trouble flashing via flashmode with one of my USB ports. I like to use the front ones on my PC but they don't work for every device. There is also a USB cable that I have that does not work for flashmode. Consider these 2 things
LaZiODROID said:
Yes (or, at least its definitely one of the reasons). Use Win 8 or Win 7 or Win XP.
If after that point you still have trouble with it sticking to flashmode: I also had trouble flashing via flashmode with one of my USB ports. I like to use the front ones on my PC but they don't work for every device. There is also a USB cable that I have that does not work for flashmode. Consider these 2 things
Click to expand...
Click to collapse
I'll try windows 7 when I get it back. And wow really? I didn't realise that using different cables actually made a difference? At the end of the day, if it charges the phone it should work! Lol, Sony know how to make things real complicated!
Experia T stuck on SONY logo
Help, another help
I read about the leaked 4.3 and the latest 4.4
Did much flashing with HTC Desire.
Now I made a big mistake trying something with my Xperia T
Using DooMLorD flashtool I got into fastboot mode and then clicked on 'Reboot device into system'
I WISH I HADN'T
Now my Xperia T is dead.
Starting up it gets stuck on the SONY logo, nothing, nothing happens.
Please help me recover the device!
HvdW said:
Help, another help
I read about the leaked 4.3 and the latest 4.4
Did much flashing with HTC Desire.
Now I made a big mistake trying something with my Xperia T
Using DooMLorD flashtool I got into fastboot mode and then clicked on 'Reboot device into system'
I WISH I HADN'T
Now my Xperia T is dead.
Starting up it gets stuck on the SONY logo, nothing, nothing happens.
Please help me recover the device!
Click to expand...
Click to collapse
It's just a soft brick. What did you wanted to flash? Just flash a stock .ftf file with flashtool, or a kernel with recovery.
St.Jimmy90 said:
It's just a soft brick. What did you wanted to flash? Just flash a stock .ftf file with flashtool, or a kernel with recovery.
Click to expand...
Click to collapse
Well, first of all I want the phone to start up normally again so that I can use it.
What I did achieve up till now is that I can get it connected to flashtool in Fastboot mode.
I guess this gives me the opportunity to flash a boot.img first so that I can install 4.4 or 4.3 later.
But first things first.
Do you think flashing a boot.img could restore the phone in a state that it functions as a normal phone again?
HvdW said:
Well, first of all I want the phone to start up normally again so that I can use it.
What I did achieve up till now is that I can get it connected to flashtool in Fastboot mode.
I guess this gives me the opportunity to flash a boot.img first so that I can install 4.4 or 4.3 later.
But first things first.
Do you think flashing a boot.img could restore the phone in a state that it functions as a normal phone again?
Click to expand...
Click to collapse
My xperia t has gone in for repair. Before considering this though, could you try one thing to see if it'll help restore phone? Go to your PC companion (and no, its not a standard recovery which i'm going to suggest so keep reading!). Once you have done this, click on "Support zone". Click "Start" on the "Phone/tablet software update" option. Note, you do not need to plug in your device yet!. You should get an error message coming up saying device not connected. And once you get this, there should be a message asking you whether you are having "severe problems with your phone/tablet". There's a "repair my phone/tablet" hyperlink. I want you to click that and NOT the connect button. Once you have clicked that, please follow the on screen instructions. Tell me if this works for you I hope it does!
fizstarrr said:
My xperia t has gone in for repair. Before considering this though, could you try one thing to see if it'll help restore phone? Go to your PC companion (and no, its not a standard recovery which i'm going to suggest so keep reading!). Once you have done this, click on "Support zone". Click "Start" on the "Phone/tablet software update" option. Note, you do not need to plug in your device yet!. You should get an error message coming up saying device not connected. And once you get this, there should be a message asking you whether you are having "severe problems with your phone/tablet". There's a "repair my phone/tablet" hyperlink. I want you to click that and NOT the connect button. Once you have clicked that, please follow the on screen instructions. Tell me if this works for you I hope it does!
Click to expand...
Click to collapse
No it dod not.
Why?
Because SONY decided that I have made changes to my phone and SONY now refuses to repair my device.
HvdW said:
No it dod not.
Why?
Because SONY decided that I have made changes to my phone and SONY now refuses to repair my device.
Click to expand...
Click to collapse
Ah that sucks! Are you not on windows 8? I've heard that windows 8 and flashtools don't get along, but if you're saying you've got your device into fastboot you should be able to flash it using flashtools!
Sony Xperia T LT30p dead resolved
OK, here it is for those interested on how to revive a dead Xperia device.
Yesterday my phone stalled at the SONY logo.
Nothing could be done anymore.
My phone has returned into normal state thanks to SonyXperiakiasT :good:
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2315572
Howto get into a state that one can flash the phone.
- download: LT30P_9.1.A.1.141_PL.ftf (the original firmware)
- install and activate flashtool-0.9.13.0-windows.exe
- at the SONY logo push on/off, vol-up and vol-down together
- when the phone vibrates an the logo disappears release all buttons and immediately after push on/off and vol-up button
- when phone vibrates release on/off button, keep pushing vol-up button and plug in USB cable from computer
- you will be in a state with a blue light at the top left of your phone.
- however you want to get in a state with a green led
- push vol-down and on/off
- unplug the USB
- wait for the phone to vibrate
- release the on/off button and plug in the USB
- Follow the instructions in the thread mentioned above and your phone will be revived.
All the pushing, releasing, plugging and unplugging is a quite delicate affair.
I tried it during several hours before I got a bit of grip on it and still I am not shure how I got into the green led state.
Try it, be patient and be shure that repair is within reach as soon as you have a green LED on your phone.
Good luck!
Hein
HvdW said:
OK, here it is for those interested on how to revive a dead Xperia device.
Yesterday my phone stalled at the SONY logo.
Nothing could be done anymore.
My phone has returned into normal state thanks to SonyXperiakiasT :good:
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2315572
Howto get into a state that one can flash the phone.
- download: LT30P_9.1.A.1.141_PL.ftf (the original firmware)
- install and activate flashtool-0.9.13.0-windows.exe
- at the SONY logo push on/off, vol-up and vol-down together
- when the phone vibrates an the logo disappears release all buttons and immediately after push on/off and vol-up button
- when phone vibrates release on/off button, keep pushing vol-up button and plug in USB cable from computer
- you will be in a state with a blue light at the top left of your phone.
- however you want to get in a state with a green led
- push vol-down and on/off
- unplug the USB
- wait for the phone to vibrate
- release the on/off button and plug in the USB
- Follow the instructions in the thread mentioned above and your phone will be revived.
All the pushing, releasing, plugging and unplugging is a quite delicate affair.
I tried it during several hours before I got a bit of grip on it and still I am not shure how I got into the green led state.
Try it, be patient and be shure that repair is within reach as soon as you have a green LED on your phone.
Good luck!
Hein
Click to expand...
Click to collapse
Hey so I ran into this same problem! my phone wouldn't do anything except boot up to the Sony screen, no lights no charging nothing
I figured it out, at least for me
>Have your flash ready to go via Flashtool
>Have your phone plugged into your computer via USB
>Hold the volume down button and then while holding it turn it on
you should have your green light and may have to hold the volume button the whole time until its done flashing.
Hope this works
FIX!
Hey the same thing happened to my xp T few days ago. My phone was rooted with UB. I was stuck on SONY LOGO too n my phone was rebooting from there repeatedly but I was managed to get into cwm n I installeddifferent kernels + Rome but it was no good. Like u said in your OP I couldn't get into flashmood too. When I select the firmware flashtools say preparing files then the phone reboots! Then flashtools say device disconnected!! The solution for this is when flashtools says device disconnected pull the usb cable n press vol up with power button n turn off phone. Then once turned off straight away press vol down n plug in usb cable n flashtools will start flashing. The important thing here is not to close the window that pops up when flashtool say device disconnected in red. Hope this helps, same prob worked for me so should work for you! Peace
Hello everyone,
It seems that my worst nightmares came up, and got my device bricked while trying to flash it to a stock ROM (had a custom multilingual ROM installed by the chinese seller), and now it's in a strange stage, as Windows detects the Qualcomm port, but adb can't see it.
The adb devices list is in blank, and QPST detects everything, but when trying to flash the device, the error message on the screenshot appears.
Also tried to do it with MiFlash, but didn't worked too.
Any idea about how to solve this?
Thank you in advance for your help.
P.D.: My device is in black screen, so no menu or anything.
P.D.2: Already downloaded the Android SDK in order to try it's ADB, but it didn't worked too.
Now after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and after the flash, USB debugging was set on, so can't figure out what could be happening...
Is it possible it's completely dead?
Any idea?
Just to say that I have tried multiple combinations while plugging the device to the PC, and didn't worked...
I mean, the PC seems to react, but always with the same end, only shows the Qualcomm port 9008, nothing about the adb...
Getting out of ideas, anyone more has some?
did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Zukunft said:
did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Click to expand...
Click to collapse
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.
Noggin said:
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.
Click to expand...
Click to collapse
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..
arif_kholid said:
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..
Click to expand...
Click to collapse
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...
Noggin said:
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...
Click to expand...
Click to collapse
i've already tried xiaomi deep flash cable, and its work on my z2 plus, that's how to force phone into 9008 mode.. and also, dont add space between folder names where your firmware files there or there will always sahara fail
Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:
Well, finally, I talked with the aftersales dpt from the shop where I got the device, and returned it, and incredibly it seems it was defective.
The guy from the tech dpt said that it wasn't supposed to die that way, so they returned me a brand new device, and fortunately it's up to date with ZUK's last official ROM.
Thank you everyone for your ideas and help, now I can enjoy this great device
My Zuk Z2 plus got stuck after TWRP, I need help badly.
sirmclord said:
Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:
Click to expand...
Click to collapse
I will tell my issue
I bought this device this July month, I was encouraged seeing you guys did a lot of flashing, I thought I could flash myself but it became a nightmare now.
I am not that much technical so please bare my usage of words below, but I need a real help.
I was doing the basic TWRP for getting the AICP ROM 12.1 but after wiping the data from TWRP my device doesnt get recognized for the Sideload and I did whatever I can but it doesnt detect my phone, so I am having a screen with Start "Green" which is showing the device status as unlocked and when I click on Recovery it goes to the Zuk logo and doesn't have any sign after that.. stuck really
I tried using QFIL but my device detects as 900H but not 9008 also adb doesn't detect my device at all after this.
I think I really did a hard brick of my device.
I dont want to loose hope, I want your help really badly.
For those of you who had the same problem don't give up! I was in that same situation and I solved by putting my phone on EDL via this method
https://www.youtube.com/watch?v=2m44xKog-dI
After plugging the phone for the second time and QFIL recognize as EDL mode I clicked on download content as fast as I could so it started to flash the ROM that I spent like 10h trying to figure a way to do it lol. Anyways, the procedure is the same as putting into EDL via adb fastboot, the only difference is that you make it through a "fake" deep flash cable as that guy in the video shows.
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