Options for fixing bricked M4 - Sony Xperia M4 Aqua

I accidentally posted this in the wrong section... so this will just be a repost of that.
So I have an xperia M4 Aqua Dual (E2363), it is not rooted, locked bootloader, usb degugging disabled, basically straight from the factory.
When I turn it on all I get is the white Xperia screen, it doesn't loop, but it doesn't get any further.
I can get in to fastboot mode but I don't think I can do anything here since usb debugging is disabled right?
If I try flash mode, I get the green light but the phone is never detected in flashtool (tried windows and linux versions 9.23 and 9.18).
Some background:
I have been having problems alot recently, so much so that in the past 3 weeks I have used Xperia Companion to software repair 5 times. I have also had problems since I got the phone, but not as frequent as recently.
Usually XC software repair works, but just like with flash mode in flashtool, XC no longer detects when I plug the phone in.
Based on that I have always had this problem, albeit not as often, I think there must be some hardware problem.
Is there anything left that I can try?

It could be hardware problem. But try flashtool. If not help- go to service center.

Related

[Q] Get back to stock 2.1 FW from stock 2.3.3 w/ broken or damaged USB port?

Hi guys! Been a long follower of posts here in the X10 forums and the Acer A500 forums since I own both devices and it would be really great if you can help me in my problem with my X10:
( DEVICE: Sony Xperia X10 ; ANDROID VERSION: Stock/Official 2.3.3 )
Recently I have noticed a problem with my Xperia X10 since I updated it with Official 2.3.3 gingerbread update from sony, here are my observations:
* when connected to the PC, it only charges and does not sync or function as a mass storage in any way (I have tried turning off USB Debugging in the settings but nothing happened.
* I tried repairing it thru PCC or SEUE but still it cant be detected by the program (Even tried reinstalling PCC and SEUE for many times, also tried to sync it thru Flash Mode but it doesnt enter flash mode, the green LED just blinks but nothings even appearing on the screen even if I click on it for 10 minutes or so)
* I tried using Flashtool to install a stock or even a custom rom but like Ive said it wont enter flash mode
* One time I connected it, it tried to install the driver but it failed then suddenly the device disappeared (Even tried to look at Device Manager)
* Tried restarting the computer then connect the X10 but still its not detected
* Tried to hard reset it to see if there will be any changes but nothing happened
* Tried to install and reinstall the drivers included with Androxyde's flashtool and Azuzu's Flashtool but nothing happens, still it wont be detected
Now back to my problem, can I install an earlier stock rom or a custom rom in any other way other than using Flash mode just so that I can root it and install an ICS rom or FXP's Cyanogen 9 rom, or even install Beats by Dre & Bravia Engine tweaks for my X10? I've seen Doomlord's similar solution ( http://forum.xda-developers.com/showthread.php?t=1054818&nojs=1#goto_threadsearch ) sadly it's only for custom roms. Need your reply guys, thank you very much!
Reply
TheViperCE said:
Hi guys! Been a long follower of posts here in the X10 forums and the Acer A500 forums since I own both devices and it would be really great if you can help me in my problem with my X10:
( DEVICE: Sony Xperia X10 ; ANDROID VERSION: Stock/Official 2.3.3 )
Recently I have noticed a problem with my Xperia X10 since I updated it with Official 2.3.3 gingerbread update from sony, here are my observations:
* when connected to the PC, it only charges and does not sync or function as a mass storage in any way (I have tried turning off USB Debugging in the settings but nothing happened.
* I tried repairing it thru PCC or SEUE but still it cant be detected by the program (Even tried reinstalling PCC and SEUE for many times, also tried to sync it thru Flash Mode but it doesnt enter flash mode, the green LED just blinks but nothings even appearing on the screen even if I click on it for 10 minutes or so)
* I tried using Flashtool to install a stock or even a custom rom but like Ive said it wont enter flash mode
* One time I connected it, it tried to install the driver but it failed then suddenly the device disappeared (Even tried to look at Device Manager)
* Tried restarting the computer then connect the X10 but still its not detected
* Tried to hard reset it to see if there will be any changes but nothing happened
* Tried to install and reinstall the drivers included with Androxyde's flashtool and Azuzu's Flashtool but nothing happens, still it wont be detected
Now back to my problem, can I install an earlier stock rom or a custom rom in any other way other than using Flash mode just so that I can root it and install an ICS rom or FXP's Cyanogen 9 rom, or even install Beats by Dre & Bravia Engine tweaks for my X10? I've seen Doomlord's similar solution ( http://forum.xda-developers.com/showthread.php?t=1054818&nojs=1#goto_threadsearch ) sadly it's only for custom roms. Need your reply guys, thank you very much!
Click to expand...
Click to collapse
Hmm, Interesting problem. Are you sure you have checked Your device manager when you turned off your phone and pressed Back button and USB connected? Like this thing shows?
View attachment 1129524
If not, either these two ways:
1)Download These ADB driver here for X10i and look how they installed. See is it solved?"
2)Are you sure how to use flashmode?? Power off button, don't connect your USB to computer yet. Then press and hold Back button and connect the USB to your PC. The green light will retain and screen will be black all the time
3)If not, Try reinstall SONY PCC / Or try email SONY
AND!!!! BEFORE You do anything like installing custom rom or stock rom from XDA here, your X10 must BE ROOTED my friend??Or not, custom roms cannot be installed into your phones? and The link you pasted methods only worked after you rooted your X10+r installed recovery.
AND, back to your problem. Sorry but No. for 2.3.3official X10, rooting must be done via flashtool. And it's considered MI5 for installing ROMs without rooting!! Plus, ICS roms or CM9 only can be flashed after your phone's bootloaded is unlocked..and of course after rooting!!
Hope this helps.
whitefang
Thank you very much on your reply whitefang! Your help is very much appreciated. Will try to test those things and will keep you posted ASAP.

[Q] I9300 won't boot, has no recovery mode and isn't getting recognized by Windows

Hi guys, I need some help with my Samsung Galaxy S3 GT-I9300.
A couple weeks ago my phone turned off by itself and never turned on completely again. If I turn it on, it stays on the very first boot screen forever (the white text saying Samsung Galaxy S3 GT-I9300, like this one (https://cdn-images.xda-developers.com/direct/1/1/5/2/1/9/8/I9300.bootlogo.jpg).
I've removed the SIM card and the MicroSD card with no effects whatsoever, and I've also left the device turned on for hours but it always stays on the same screen.
I cannot enter recovery mode (it just shows the boot screen mentioned above) but I can enter download mode. At download mode, I get this info:
ODIN MODE
Product name: GT-I9300
Custom binary download: No
Current binary: Samsung Official
System Status: Oficial
As you can see, I have never flashed a custom rom (or rooted or even unlocked the bootloader). This is what intrigues me the most, since everybody I've seen with the same problem had trouble during or after a flash.
My last OS version was 4.3.1 and it was received OTA months ago.
In the past few months, my device rebooted out of nowhere, even when I was not using it. Occasionally, it had the stuck power button, which caused it to reboot on a loop, but I always solved it by nudging the power button a little. I don't know if these two previous problems might have caused the problem I'm facing now, but they're not showing up anymore.
Anyway, I've tried to flash the newest official rom (NK1 - ZTO) via Odin but I always get a NAND Write error.
I've tried changing USB ports, USB cable and computers; tried Odin 3.04, 3.07 and 3.09; tried Samsung USB drivers v1.5.45 and 1.5.49 but nothing of the above made any difference.
Today things started getting worse, though. In the past, Windows would always recognize the device on at least one specific USB port; Odin would also recognize the device and then I would get the NAND Write error. Now, Windows will not recognize the device no matter the cable, USB port or driver version. I only get a unknown device error and Odin won't recognize anything connected.
I tested all my setup with a working Galaxy S3 I9300 and it got recognized every single time, no matter the USB port, the cable or the computer.
Considering that another device is getting recognized by different computers, I suppose that the problem lies in my Galaxy S3.
So, can anyone offer me any kind of advice or point me in any direction on how I can try to fix my phone? Is my phone physically dying and no software solution will unbrick it?
Your power button issue has corrupted/damaged the nand memory. Try the dead boot recovery thread in general forum but unless you have warranty you might be better off with a new phone.
I was afraid of that.
I checked the post you mentioned but it seems I'd have to buy tools and hardware more expensive than the phone itself, so I'd rather buy a new smartphone.
Thanks for the help!

sticks to the logo of the operator.

Hi all, I introduce myself, I am Franco Paladini, First Son.
Well let's get my phone will not turn on, (on but not quite, sticks to the logo of the operator) can not have it connected to the PC, which is the worst.
I commented as was my dear LG L9:
Windows :8.1 pro
Phone: LG P778G (P768 board)
ROM: Stock JB (V20B Personal Argentina)
Kernel: Stock
Root: Yes
It all started when you activate or re-activate a tweak to the "Android Tweaker 2" application. Previously it had already activated some as battery life, performance, multimedia, etc. All tested walked 10 points. But I happened to go over those who had already turned and noticed that some had not been activated, immediately afterwards the turn, I remember that was the voltage Flash, JPEG quality, and I think that caused the problem persistence hw ui. This caused the restart not pass the logo of the operator. I am no expert on the subject but not a rookie, I thought it would be easy flash, as he had done previously with other devices, and with this also but had flashed with the device running all ok. Now the problem is that the computer does not recognize my phone, or cell phone does not connect well with pc. When I plug in download mode (SW / UPGRADE) does not install any driver. When I plug in recovery mode (stock not cwm not TWRP) some drivers but not the OMAP, only androidnet installed sooner, but soon turned off to not connect ever. Or turning off or restarting anyway connected, please help! Will thank a lot and was investigating several hours and not be able to connect, have reinstalled drivers, have tried different versions but none of them work, I'm desperate, it IS URGENT! I can spend the Device Manager list of windows or what they may.

Can't update M4 to 26.3.A.1.33 - USB Problem or something?

Hi, unfortunately I've had to go back to my xperia m4 aqua because my new phone ended up being bricked or locked or whatever and I can't seem to get it back on in anyway. It just stays on the same screen after doing resets and other things.
Anyway I need help with XPERIA. When I do an update using Xperia companion it will turn my phone off and tell me to do the hold down volume and put the usb in. I do that then it just comes up with USB not recognized. I've tried uninstalling and finding usb drivers etc. But nothing seems to work. Any help here? I haven't used my Xperia for a year so not sure if I should root my phone and do a rom install or something. I have no idea since I'm a noob.
Think I posted in the wrong forum section? Anyway of moving it to Q&A?
(update) I have moved the USB to 2.0 ports. It says MTP USB Device not successfully installed (code10).
Also my XPERIA M4 AQUA is 5.0? I just read there is a 6.0? I can't seem to update ffs lol

Undetected by PC. Unable to access fastboot, flashtool. "USB devices disabled"

Undetected by PC. Unable to access fastboot, flashtool. "USB devices disabled"
Note 1: I purchased this device second hand in a third world country, so please don't suggest "warranty" or return or service options.
Note 2: Both my computers work perfectly fine with other devices, so please don't waste time asking questions about them. They are fine. My adb configuration is fine. Yes I've tried many, many different cables. This problem is definitely 100% with the phone. The only thing that COULD be computer-side is drivers, but once again, it was connecting normally without any drivers before the "USB devices disabled" warning. I have the latest version of everything with the latest updates. I have followed all the info in all other guides all over the internet.
When I first got this phone, I did what I always do: Enable dev options, enable OEM unlock and ADB debugging. Connected it to PC and was detected normally in My Computer like any other phone. I had no particular Sony drivers installed and no Xperia Companion, only ADB drivers.
I started looking up how to install TWRP, which is the first thing I do on any phone. For some reason, I wasn't able to access fastboot or flashmode on this phone. I tried to access them in adb, but adb wouldn't show the device, even though it appeared in My Computer, had ADB debugging enabled and USB connection type set as MTP File Transfer.
Odd. I installed Xperia Companion, which detected the phone normally, but that didn't make adb work. ̶I̶ ̶t̶r̶i̶e̶d̶ ̶i̶n̶s̶t̶a̶l̶l̶i̶n̶g̶ ̶t̶h̶e̶ ̶o̶f̶f̶i̶c̶i̶a̶l̶ ̶d̶r̶i̶v̶e̶r̶ ̶a̶s̶ ̶s̶u̶g̶g̶e̶s̶t̶e̶d̶ ̶e̶v̶e̶r̶y̶w̶h̶e̶r̶e̶,̶ ̶b̶u̶t̶ ̶f̶o̶r̶ ̶s̶o̶m̶e̶ ̶r̶e̶a̶s̶o̶n̶ ̶W̶i̶n̶d̶o̶w̶s̶ ̶w̶o̶n̶'̶t̶ ̶l̶e̶t̶ ̶m̶e̶ ̶i̶n̶s̶t̶a̶l̶l̶ ̶i̶t̶.̶ ̶I̶n̶ ̶o̶n̶e̶ ̶m̶e̶t̶h̶o̶d̶,̶ ̶i̶t̶ ̶t̶e̶l̶l̶s̶ ̶m̶e̶ ̶t̶h̶a̶t̶ ̶"̶T̶h̶i̶s̶ ̶d̶e̶v̶i̶c̶e̶ ̶i̶s̶ ̶a̶l̶r̶e̶a̶d̶y̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶b̶e̶s̶t̶ ̶d̶r̶i̶v̶e̶r̶"̶,̶ ̶a̶n̶d̶ ̶t̶h̶e̶ ̶H̶a̶v̶e̶ ̶D̶i̶s̶k̶ ̶m̶e̶t̶h̶o̶d̶ ̶t̶e̶l̶l̶s̶ ̶m̶e̶ ̶t̶h̶a̶t̶ ̶"̶T̶h̶i̶s̶ ̶d̶r̶i̶v̶e̶r̶ ̶i̶s̶n̶'̶t̶ ̶c̶o̶m̶p̶a̶t̶i̶b̶l̶e̶ ̶w̶i̶t̶h̶ ̶t̶h̶i̶s̶ ̶d̶e̶v̶i̶c̶e̶"̶,̶ ̶a̶n̶d̶ ̶i̶n̶ ̶b̶o̶t̶h̶ ̶c̶a̶s̶e̶s̶ ̶t̶h̶e̶ ̶i̶n̶s̶t̶a̶l̶l̶a̶t̶i̶o̶n̶ ̶f̶a̶i̶l̶s̶.̶
Edit: I successfully installed flashtool drivers as well as the official Sony driver. Still unsuccessful.
I kept reconnecting to different ports and different cables to see if it helps, but I started getting a strange warning on my phone that I've never seen before: "USB devices disabled for using too much power". I ignored it and clicked ok. This showed up twice or 3 times. After that, the phone stopped being detected by My Computer and also Xperia Companion. Windows started warning me upon connecting that "USB Device not recognized".
A̶l̶l̶ ̶o̶f̶ ̶t̶h̶i̶s̶ ̶w̶a̶s̶ ̶y̶e̶s̶t̶e̶r̶d̶a̶y̶.̶ ̶I̶ ̶f̶o̶r̶g̶o̶t̶ ̶a̶b̶o̶u̶t̶ ̶i̶t̶ ̶a̶n̶d̶ ̶k̶e̶p̶t̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶p̶h̶o̶n̶e̶ ̶n̶o̶r̶m̶a̶l̶l̶y̶.̶ T̶o̶d̶a̶y̶,̶ ̶I̶ ̶d̶e̶c̶i̶d̶e̶d̶ ̶t̶o̶ ̶t̶r̶y̶ ̶a̶g̶a̶i̶n̶,̶ ̶b̶u̶t̶ ̶e̶v̶e̶r̶y̶t̶h̶i̶n̶g̶ ̶s̶e̶e̶m̶e̶d̶ ̶t̶o̶ ̶b̶e̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶s̶t̶i̶l̶l̶.̶ ̶I̶ ̶d̶e̶c̶i̶d̶e̶d̶ ̶t̶o̶ ̶t̶r̶y̶ ̶o̶n̶e̶ ̶m̶e̶t̶h̶o̶d̶ ̶t̶h̶a̶t̶ ̶I̶ ̶t̶h̶o̶u̶g̶h̶t̶ ̶w̶a̶s̶ ̶p̶r̶e̶t̶t̶y̶ ̶s̶t̶u̶p̶i̶d̶ ̶w̶h̶e̶n̶ ̶I̶ ̶f̶i̶r̶s̶t̶ ̶c̶a̶m̶e̶ ̶a̶c̶r̶o̶s̶s̶ ̶i̶t̶,̶ ̶b̶u̶t̶ ̶a̶t̶ ̶t̶h̶i̶s̶ ̶p̶o̶i̶n̶t̶ ̶I̶ ̶w̶a̶s̶ ̶o̶u̶t̶ ̶o̶f̶ ̶o̶p̶t̶i̶o̶n̶s̶ ̶s̶o̶ ̶I̶ ̶f̶i̶g̶u̶r̶e̶d̶ ̶w̶h̶a̶t̶ ̶t̶h̶e̶ ̶h̶e̶c̶k̶.̶ ̶I̶ ̶d̶i̶s̶a̶b̶l̶e̶d̶ ̶A̶D̶B̶ ̶d̶e̶b̶u̶g̶g̶i̶n̶g̶,̶ ̶O̶E̶M̶ ̶u̶n̶l̶o̶c̶k̶ ̶a̶n̶d̶ ̶d̶e̶v̶e̶l̶o̶p̶e̶r̶ ̶o̶p̶t̶i̶o̶n̶s̶.̶ ̶ ̶T̶h̶e̶ ̶p̶h̶o̶n̶e̶ ̶c̶o̶n̶t̶i̶n̶u̶e̶d̶ ̶t̶o̶ ̶b̶e̶ ̶u̶n̶d̶e̶t̶e̶c̶t̶e̶d̶,̶ ̶s̶o̶ ̶I̶ ̶d̶e̶c̶i̶d̶e̶d̶ ̶t̶o̶ ̶r̶e̶s̶t̶a̶r̶t̶ ̶t̶h̶e̶ ̶p̶h̶o̶n̶e̶.̶ ̶I̶t̶ ̶b̶o̶o̶t̶s̶ ̶c̶o̶m̶p̶l̶e̶t̶e̶l̶y̶ ̶a̶n̶d̶ ̶n̶o̶r̶m̶a̶l̶l̶y̶,̶ ̶b̶u̶t̶ ̶u̶p̶o̶n̶ ̶e̶n̶t̶e̶r̶i̶n̶g̶ ̶m̶y̶ ̶p̶i̶n̶ ̶c̶o̶d̶e̶,̶ ̶i̶t̶ ̶c̶r̶a̶s̶h̶e̶s̶ ̶a̶n̶d̶ ̶r̶e̶b̶o̶o̶t̶s̶.̶ ̶T̶h̶e̶ ̶f̶u̶r̶t̶h̶e̶s̶t̶ ̶I̶'̶v̶e̶ ̶b̶e̶e̶n̶ ̶a̶b̶l̶e̶ ̶t̶o̶ ̶g̶e̶t̶ ̶i̶t̶ ̶w̶a̶s̶ ̶t̶o̶ ̶r̶e̶a̶c̶h̶ ̶m̶y̶ ̶h̶o̶m̶e̶ ̶s̶c̶r̶e̶e̶n̶ ̶(̶b̶y̶ ̶d̶i̶s̶a̶b̶l̶i̶n̶g̶ ̶W̶i̶-̶F̶i̶ ̶a̶n̶d̶ ̶m̶o̶b̶i̶l̶e̶ ̶d̶a̶t̶a̶,̶ ̶n̶o̶t̶ ̶s̶u̶r̶e̶ ̶i̶f̶ ̶t̶h̶a̶t̶ ̶m̶a̶d̶e̶ ̶a̶ ̶d̶i̶f̶f̶e̶r̶e̶n̶c̶e̶)̶,̶ ̶b̶u̶t̶ ̶t̶h̶e̶n̶ ̶i̶t̶ ̶c̶r̶a̶s̶h̶e̶s̶ ̶a̶g̶a̶i̶n̶.̶ ̶A̶n̶y̶ ̶a̶t̶t̶e̶m̶p̶t̶ ̶t̶o̶ ̶a̶c̶c̶e̶s̶s̶ ̶S̶e̶t̶t̶i̶n̶g̶s̶ ̶i̶n̶s̶t̶a̶n̶t̶l̶y̶ ̶m̶a̶k̶e̶s̶ ̶i̶t̶ ̶c̶r̶a̶s̶h̶,̶ ̶a̶l̶t̶h̶o̶u̶g̶h̶ ̶a̶c̶c̶e̶s̶s̶i̶n̶g̶ ̶s̶p̶e̶c̶i̶f̶i̶c̶ ̶s̶e̶t̶t̶i̶n̶g̶s̶ ̶m̶e̶n̶u̶s̶ ̶t̶h̶r̶o̶u̶g̶h̶ ̶Q̶S̶ ̶(̶l̶i̶k̶e̶ ̶m̶o̶b̶i̶l̶e̶ ̶d̶a̶t̶a̶)̶ ̶o̶p̶e̶n̶ ̶f̶i̶n̶e̶,̶ ̶b̶u̶t̶ ̶i̶t̶ ̶s̶t̶i̶l̶l̶ ̶c̶r̶a̶s̶h̶e̶s̶ ̶a̶f̶t̶e̶r̶ ̶a̶ ̶c̶o̶u̶p̶l̶e̶ ̶o̶f̶ ̶s̶e̶c̶o̶n̶d̶s̶.̶
Edit: Reboot has been fixed with a factory reset via Support > System > Factory reset during the short uptime of the device before it reboots.
This phone is 100% stock, Oreo, latest updates. Zero root exploit attempts have been made. I activated Substratum's Andromeda via PC but Substratum still told me that it didn't work, so I stopped trying. I also side-loaded some APKs (all trusted, none of which on the system partition), but that's about it.
I've also tried connecting it to my laptop with no difference. The exact same behavior, so it's clearly the phone itself.
Clearly, the key to all of this is finding a way to access fastboot and flashmode, but for the life of me I can't get either to work. I follow the instructions and get a red LED that gets stronger if I keep holding down the VOLdwn button and the Sony splash screen followed by the charging animation. VOLup never does anything, it boots normally, unless the power button is also pressed which makes it vibrate 3 times, apparently signaling that the device was powered off.
Also, figuring out why the charging port ("USB Devices") seems to have been disabled (as per the warning message) and how to re-enable it. From what I've read, this typically happens when moisture is detected in the charging port and is done to protect the phone from over-voltage. However I have not used this phone anywhere near water since I've gotten it. And it was initially being detected normally.
I saw some great guides made by @FoxTheLegend and @YasuHamed for this phone and I was hoping they'd be able to lend their experience to help me figure this out. I've never been completely locked out of a device like this in a way that I was completely unable to solve, and I've dealt with Samsung devices with FRP and the 7 day thing.
Update: I installed flashtool drivers, but still not having any luck getting into fastboot or flash mode. The device still shows up as not recognized even when just charging. Same behavior is exhibited in safe mode.
Good morning sir, @Ace2213
thank you for the detailed Recital of your observation but frankly the KEY info which is required for me to make any observation is missing
1. Windows Version ? Win7 x64/32x ?? , w10 ?
2. firewall status? which antivirus/internet security running? or in win10, security essentials were disabled or not?
3. if win10 , has digital driver signatures were put to sleep? or not?
4. flasthtool versions?, drivers installation? , google usb drivers? xperiax Motherboard driver from developer.sonymobile.com ?
5. google adb & minimal fastboot version?
6. Xperia X running on which Stock Version? (Oreo/Nougat) ???
7. in xperia X under services menu > configuration, Unlocking status is allowed or not? but ...
8. as you said you bought it second hand, is the device is already UNLOCKED? & when you boot do u see "THIS DEVICE is UNLOCKED and CANNOT BE TRUSTED" warning from sony for 5 seconds before xperia splash screen?"
my guess is if the device is already unlocked by the time you made purchase, alot have had might happend to it by previous user(s) which ofcourse something mystry now!
so now if the device is totally bricked and non responsive try ..
1. press volume up and power keys for 15 seconds, you should feel 3 jerks (after 1 jerk at 5th second) and this will force device to force shutdown.
2. try installing fresh drivers (for everything) and flash the stock firmware) via flashtool ( read guide thoroughly, as there are many details)
but
if device is totally dead and doing nothing! then do the #RUBBER #BAND trick
1. tie rubber band across Xperia X, in a way that Volume DOWN key is pressed 100% and keep it overnight,, this will force battery drain, & Motherboard to reset
2. after 36 hours , plug mobile to wall charger and leave it for a 24hrs,,,, later see if red led blinks! or appears ,,
3. keep charging , once red led goes off, NOW is the time to connect xperia x to flashmode and flash stock firmware via flashtool!!!
U
YasuHamed said:
1. Windows Version ? Win7 x64/32x ?? , w10 ?
Click to expand...
Click to collapse
Win10 x64 with latest updates, both computers.
YasuHamed said:
2. firewall status? which antivirus/internet security running? or in win10, security essentials were disabled or not?
Click to expand...
Click to collapse
Windows Firewall and I'm guessing Security Essentials are enabled (Should I disable?). No AV or 3rd party security on either computer.
YasuHamed said:
3. if win10 , has digital driver signatures were put to sleep? or not?
Click to expand...
Click to collapse
Admittedly, I only figured out this part after I made the post, so now flashtool drivers have successfully been installed.
YasuHamed said:
4. flasthtool versions?, drivers installation? , google usb drivers? xperiax Motherboard driver from developer.sonymobile.com ?
Click to expand...
Click to collapse
Latest version of flashtool from the website. I installed the first 2 "common" drivers and all Z device drivers (like you suggested on another post). I tried to search for Google drivers, but for Sony, they sent me back to the Sony website for the official driver, which I have "installed", appearing constantly as "Sony sa0114 ADB Interface Driver" with Error Code 10. I'm guessing "motherboard" is the official Sony driver?
YasuHamed said:
5. google adb & minimal fastboot version?
Click to expand...
Click to collapse
Latest, from xda thread.
YasuHamed said:
6. Xperia X running on which Stock Version? (Oreo/Nougat) ???
Click to expand...
Click to collapse
Oreo. I know I need to downgrade to MM.
YasuHamed said:
7. in xperia X under services menu > configuration, Unlocking status is allowed or not?
Click to expand...
Click to collapse
BL Unlocking allowed, yes.
YasuHamed said:
8. as you said you bought it second hand, is the device is already UNLOCKED? & when you boot do u see "THIS DEVICE is UNLOCKED and CANNOT BE TRUSTED" warning from sony for 5 seconds before xperia splash screen?"
Click to expand...
Click to collapse
No. People are not very tech savvy here and are scared of root.
I cannot use fastboot or flashmode. The result of connecting the cable while pressing down ANY button is the same result as connecting the cable without any button. It almost seems like it doesn't recognize the button presses at all. But PWR+VLUP does work and vibrates 3 times.
Are you familiar with the "USB devices disabled for using too much power" message? I feel like this is a key to understanding the problem.
The other breakthrough would be figuring out why I cannot enter fastboot or flashmode.
Another big question is why my phone is restarting by itself now after I disabled developer options. Did I trip dm-verity or some security thing?
- on win10 when digital signature verification is off along with firewall and security essentials, win10 allows adb/fastboot connections. if you have any other droid, try making connection. if windows fails then its not xperia X you whould be focusing on.
- since you selected on first two of xperia z drivers from flasthool given setup, i would suggest you to rerun it and install all of them! just incase
- also see this https://developer.sony.com/file/download/xperia-x-driver/
- for random reboots issue, reset your device (factory reset) (wipe all data)
- since boot it locked you can repair the device from Xperia companion
- try different usb cable ( ironically / comically, sony's own give cable usually don't connect with flashtool, ) i always use xaiomi or samsung cable to make test connection!
- if device jerks that amazing sign! device is not hard bricked! it might be soft bricked due to some software error! or attempts to root etc
- downgrading to MM to save DRM KEYS is HIGHLY RECOMENDED
but since
- the device is now almost 4 years old and have all of the possible updates! if you don't have drmkeys saved! it doesnt matter! but then if you wana give/sell this device in your country tommorow , for better deal you must relock the bootloader and you need drmkeys to relock the bootloader!
YasuHamed said:
- if you have any other droid, try making connection. if windows fails then its not xperia X you whould be focusing on.
Click to expand...
Click to collapse
My old Samsung J5 Prime worked fine with adb on both devices with all the same settings. The problem is the phone, for sure.
YasuHamed said:
- since you selected on first two of xperia z drivers from flasthool given setup, i would suggest you to rerun it and install all of them! just incase
Click to expand...
Click to collapse
I installed the first two common ones, and ALL the Z ones.
YasuHamed said:
- also see this https://developer.sony.com/file/download/xperia-x-driver/
Click to expand...
Click to collapse
That's the official driver that I'm talking about.
YasuHamed said:
- for random reboots issue, reset your device (factory reset) (wipe all data)
Click to expand...
Click to collapse
I can't, without access to Settings (the phone doesn't stay on long enough) and no adb, fastboot or flashtool or Xperia Companion.
YasuHamed said:
- since boot it locked you can repair the device from Xperia companion
Click to expand...
Click to collapse
Xperia Companion doesn't detect it. That's the whole point.
YasuHamed said:
- try different usb cable ( ironically / comically, sony's own give cable usually don't connect with flashtool, ) i always use xaiomi or samsung cable to make test connection!
Click to expand...
Click to collapse
I've tried almost 20 cables so far, including Samsung and Motorola cables.
YasuHamed said:
- if device jerks that amazing sign! device is not hard bricked! it might be soft bricked due to some software error! or attempts to root etc
Click to expand...
Click to collapse
Ok but how to fix it?
YasuHamed said:
- downgrading to MM to save DRM KEYS is HIGHLY RECOMENDED
Click to expand...
Click to collapse
I don't really care about DRM keys, I just want TWRP.
So no idea about the USB port being disabled? Or why I'm unable to access fastboot and flash mode?
Ace2213 said:
My old Samsung J5 Prime worked fine with adb on both devices with all the same settings. The problem is the phone, for sure.
I installed the first two common ones, and ALL the Z ones.
That's the official driver that I'm talking about.
I can't, without access to Settings (the phone doesn't stay on long enough) and no adb, fastboot or flashtool or Xperia Companion.
Xperia Companion doesn't detect it. That's the whole point.
I've tried almost 20 cables so far, including Samsung and Motorola cables.
Ok but how to fix it?
I don't really care about DRM keys, I just want TWRP.
So no idea about the USB port being disabled? Or why I'm unable to access fastboot and flash mode?
Click to expand...
Click to collapse
sounds like i should get hold of your device to do RND ....
it will be challanging!
at this point i think, (assuming) that the usb port is faulty! it charges for sure but data transfer is not happening.
this happens when local shops repairs usb port if user has damaged it (damage can be usb wire head hard bent while it was plugged it! something that has made port faulty)
can you transfer files to/from device? if no then this might be the case
i am running out of options
YasuHamed said:
can you transfer files to/from device?
Click to expand...
Click to collapse
At the beginning, when the device was detected over USB, I transfered files to\from it. Now, I'm not sure
Like I said, it gave me warning about "USB devices disabled" RIGHT BEFORE it stopped being recognized
Anyone else? I really need my phone back asap since I use it for work
Is there another way to factory reset? In my 2-5 seconds I have inside my phone, I put the Xperia Support app on the home screen and keep restarting to see if I can factory reset within the time limit. Support > System > Factory Reset > Factory Reset > Reset. Powering off the device between boots makes it last a bit longer, but still not enough. The farthest I can get is to entering my pin to confirm factory reset. I enter it, click enter and everything freezes again.
Could this be hardware related? The top right corner gets a bit warm and this whole situation is starting to remind me of the Nexus 5X. This is also a hot country. Maybe if I try using it inside a freezer I'll be able to factory reset.
If not, is there another way to factory reset that would be faster to access through the system? Or an easy key combination or hardware action (like disconnecting a component)? This phone doesn't look easy to disassemble though
If I can factory reset I should at least (hopefully) fix the bootloop and be able to re-enable dev options, OEM unlock and ADB debugging.
UPDATE: I INITIATED THE FACTORY RESET! I was fast enough using the above steps and triggered it. The phone reset and the reboots finally stopped. The OEM unlock option is disabled, which means I was right. I did trip a security feature. In Samsung devices, when this happens, you need to wait 7 days for the option to reappear. Is there a workaround for Xperia devices?
Update: I was able to enable OEM unlocking by long pressing on the option.
I tried to access fastbood and flashmode, same as before. I connected it to the PC in normal mode and the PC recognized it, configured it then showed "Xperia X". The phone prompted me to install Xperia Companion. I clicked install and it opened the Xperia Companion on my PC which was already installed, but it didn't detect the phone. Windows still saying "device not recognized". Still no "USB Connection Type" notification. USB Connection still disabled under Settings > Connectivity > USB, saying "Not Connected".
I noticed the tip of the charger getting very warm while charging (maybe because it's loose and keeps coming off?) and the bottom of the phone near the charging port sort of seems warm on the inside.
I'm using Motorola's Turbo Wall charger. Is it possible that the current is too high? My device charged to 94% over USB while I was trying to fix it yesterday, so it clearly has no issue with low-watt charging.
The reason I'm mentioning it is because I've read that Sony can disable "USB devices" if moisture is detected to protect from over-voltage. Is it possible that this happened in my case even without moisture, but simply because a too-powerful charger was used?
Did you get any solvings for ur Xperia X issue?
Ace2213 said:
I noticed the tip of the charger getting very warm while charging (maybe because it's loose and keeps coming off?) and the bottom of the phone near the charging port sort of seems warm on the inside.
I'm using Motorola's Turbo Wall charger. Is it possible that the current is too high? My device charged to 94% over USB while I was trying to fix it yesterday, so it clearly has no issue with low-watt charging.
The reason I'm mentioning it is because I've read that Sony can disable "USB devices" if moisture is detected to protect from over-voltage. Is it possible that this happened in my case even without moisture, but simply because a too-powerful charger was used?
Click to expand...
Click to collapse
Greeting dude,
My friend have Sony Xperia X Dual (F5122) phone, and about 2 months ago he got problems with sound (phone doesn't play any sound and record voices, sometimes restarting phone helps, but only for a couple hours ) i guessed that problem with OS because he was step by step upgrading Android from 6.0 till 8.0 and then got this problem. By problem with sound he got "Warranty Time Service" message in top of phone. Then i suggested him to fully reinstall OS, i have read instruction how to flashh phone, but i got same issue as you. I couldn't put phone to fastboot, it just charging, that's all. Computer doesn't recognize him like any new device. I used almost 5 different cables that i use for my Samsung Galaxy phone. All cable are workable and many times i flash and tranfer datas with them. I don't know really how to fix this issue.
I was able to get a screenshot of this error. Happened while using a Motorola 2.1A quick charger. Also came up a couple of times before it stops, but the phone was undetected before and after.
I'm honestly disappointed in the lack of community support for this device. I'm going to sell it and get an XZ1. Hopefully that one is better supported. If not, at the very least it runs Pie and will run Q.

Categories

Resources