Today I was surfing using Firefox, suddenly the screen froze. Battery was probably at about 45%. I could do nothing, not even locking the screen.
I pressed the power button for some seconds, did nothing.
Suddenly the screen turned black. Since them I'm not able to reboot the phone.
I tried VolUp + Power for longer than 15s, but nothing. I also tried VolDown+Power, VolUp+VolDown+Power, VolUp+VolDown. Nothing works.
Plugging in AC does not do anything... When I plug it into the PC, I can see the following in the syslog:
Code:
[ 172.018947] usb 2-3.1.3: new high-speed USB device number 7 using xhci_hcd
[ 172.121955] usb 2-3.1.3: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
[ 172.121959] usb 2-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 172.121961] usb 2-3.1.3: Product: QUSB__BULK
[ 172.121963] usb 2-3.1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 172.141741] usbcore: registered new interface driver usbserial_generic
[ 172.141756] usbserial: USB Serial support registered for generic
[ 172.144155] usbcore: registered new interface driver qcserial
[ 172.144164] usbserial: USB Serial support registered for Qualcomm USB modem
[ 172.144187] qcserial 2-3.1.3:1.0: Qualcomm USB modem converter detected
The interesting thing is, that if I press VolUp+Power for 15s, the device disconncts and connects again:
Code:
[ 571.412179] usb 2-3.1.3: USB disconnect, device number 8
[ 571.412352] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 571.412375] qcserial 2-3.1.3:1.0: device disconnected
[ 580.337917] usb 2-3.1.3: new high-speed USB device number 9 using xhci_hcd
[ 580.440931] usb 2-3.1.3: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
[ 580.440934] usb 2-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 580.440937] usb 2-3.1.3: Product: QUSB__BULK
[ 580.440939] usb 2-3.1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 580.442090] qcserial 2-3.1.3:1.0: Qualcomm USB modem converter detected
[ 580.442273] usb 2-3.1.3: Qualcomm USB modem converter now attached to ttyUSB0
So it looks like the device still reacts to the soft-reboot but does not boot somehow...
QUSB__BULK appears in this context: https://forums.oneplus.com/threads/...e-for-a-hard-bricked-oneplus-2.347607/page-38
Has the phone bricked itself?!
Edit: Nokia Support told me I need to send the device for repair...
Sounds like a warranty case to me (at least if you still have warranty). I wouldn't doubt, just return the phone.
yes, the phone is 12 days old... support suggested the same.
Would be interesting to know if this is a "common" problem or if I was just unlucky...
Do you happen to know if it was on the January update? I had several random reboots--not the same as you--on the November & December ones...
I got the phone back from repair. The report states as fault code: "416 - Start-Up - SW-failure - reflash"
So somehow the flash got corrupted but they were able to reflash it. So at least no hardware damage.
I'm not sure if this happened due to the January update or not, I got the phone beginning of February and immediately installed the update, thus I never saw the old version.
Let's hope you're safe from now on for those of us who have no issues (I count myself so lucky) the phone is really good. Crossing my fingers for you
would be interesting to know if this breakdown was caused by the hardware (maybe a bad flash chip) or was somehow triggered from the OS.
Would be also interesting to know what exactly was broken. Idk the structure of the chipset but as the device would not even boot the bootloader, I would guess that the bootloader configuration was messed up?
Btw: I would guess that all the bootloader stuff is locked on the N7.1 and probably protected with keys (which are not public), right?
until now, everything works again *knock on wood*
I had a similar issue but it was while I updated the February OTA. The phone prompted that it was ready for install, and so I said yes and it rebooted and hung on the Android One splash screen for a long while and then displayed a system level message similar to booting into the factory reset mode (I can't remember what it is called right now) and it said update failed, try again, or factory reset data. I clicked try again (using volume keys) and it rebooted a couple more times until it froze, powered on, on the Android One screen with a "Download Mode" message in the upper left. Phone would not power off or reboot or anything. Sent it in under warranty to Nokia (eBuilder) (bought in November from Best Buy) and they fixed it in a day and sent it back. Same IMEI and physical phone. No signs of entry. I didn't get a report back of what they fixed though. But now my phone won't detect or pull the February update. Otherwise it seems to be perfectly fine. I did have a few random reboots since the January update initially but I've always had that on various Android phones so thought not much of it. I got it back on the December Pie build and it immediately wanted to update to the January one. I did so tentatively and so far have had no problems.
UCFJake said:
I had a similar issue but it was while I updated the February OTA. The phone prompted that it was ready for install, and so I said yes and it rebooted and hung on the Android One splash screen for a long while and then displayed a system level message similar to booting into the factory reset mode (I can't remember what it is called right now) and it said update failed, try again, or factory reset data. I clicked try again (using volume keys) and it rebooted a couple more times until it froze, powered on, on the Android One screen with a "Download Mode" message in the upper left. Phone would not power off or reboot or anything. Sent it in under warranty to Nokia (eBuilder) (bought in November from Best Buy) and they fixed it in a day and sent it back. Same IMEI and physical phone. No signs of entry. I didn't get a report back of what they fixed though. But now my phone won't detect or pull the February update. Otherwise it seems to be perfectly fine. I did have a few random reboots since the January update initially but I've always had that on various Android phones so thought not much of it. I got it back on the December Pie build and it immediately wanted to update to the January one. I did so tentatively and so far have had no problems.
Click to expand...
Click to collapse
That's what I had. My phone's on the way back to me now. Let's hope it behaves from now on
Well... Bricked the phone again today. Will send it to repair tomorrow...
This time during unlocking, the phone went black and was not able to boot again. Same symptoms as last time -.-
raph3ix said:
Well... Bricked the phone again today. Will send it to repair tomorrow...
This time during unlocking, the phone went black and was not able to boot again. Same symptoms as last time -.-
Click to expand...
Click to collapse
Interesting. The phone goes into RAMDUMP mode randomly and even the emergency download will not help as it is not in EDL mode. This happening a second time looks like a hardware flaw and Nokia should be replacing your mainboard this time. Keep a check. Don't settle for a software flash even if they manage to do it after disasssembly.
singhnsk said:
Interesting. The phone goes into RAMDUMP mode randomly and even the emergency download will not help as it is not in EDL mode. This happening a second time looks like a hardware flaw and Nokia should be replacing your mainboard this time. Keep a check. Don't settle for a software flash even if they manage to do it after disasssembly.
Click to expand...
Click to collapse
I guess that I can not do anything because I am missing the keys to communicate to the Qualcomm chip, right?
It would be interesting to know if one could extract some crash information when this happens...
I'll check if I get a new phone or if they just reflash.
Wow, I just received this mail from the nokia support:
Your Nokia 7.1 is being prepared for shipment to the address you provided. Unfortunately, the fault is not covered by warranty and your
phone is either beyond economical repair (not repairable) or the repair quote has been rejected.
Reason: No Fault Found
Click to expand...
Click to collapse
Now I'm thrilled to have it back to see if it works again....
Got the phone back. The repair paper says that not fault was found... At least they did not nothing, as they factory resetted the device or reflashed. Back on December security updates.
So either the problem somehow fixed itself or their diagnosis tools fixed it somehow.
If anyone has an idea what could have happened, please provide some info
what the ... My phone is in QDL mode again.
Is anyone else experiencing these kinds of trouble?
The phone came good again! The battery drained and I could boot again.
Looks like you can escape from QDL mode by cutting the power.
Now, it would be interesting to know if you can escape the QDL with some command too.
raph3ix said:
The phone came good again! The battery drained and I could boot again.
Looks like you can escape from QDL mode by cutting the power.
Now, it would be interesting to know if you can escape the QDL with some command too.
Click to expand...
Click to collapse
Trying to install the March security update my phone got stuck in Download Mode. I was able to see the phone in fastboot, but when I tried to wipe the data and factory reset, it shows the factory reset animation for a split second and then crashes back to download mode. Phone was stock/not rooted.
Nokia support says they will not help me because I have the phone in the US but the IMEI is supposed to be for Hong Kong -- I guess the ebayer I got it from imported it. I really have no recourse and Nokia has basically stolen my money because they refuse to even let me PAY to send them the phone to repair.
Any ideas?? Running out the battery didn't get me any relief.
thiazzi said:
Nokia has basically stolen my money because they refuse to even let me PAY to send them the phone to repair.
Click to expand...
Click to collapse
Unfortunately, I'm also done with the Nokia support :crying: They can not tell me if I'll get a new phone, as the old one is practially not trustworthy anymore. They just tell me "yeah maybe, that depends"
Bought another phone two days ago.
just some news from my nokia phone... I had a long discussion with the support via email, but all their advises would not work.
So finally I send in the phone one last time and got it back with a long list of repaired stuff oO
They repaired several connectors to the display as well as the speaker. I have no idea why this would fix the issue....
Anyways, I am now using a Samsung which hadn't let me down so far
Related
Hi guys!
Like my brother said: if they don't know it at XDA, there is simply not a solution yet. And having tried a lot of options myself, your expertise is wanted!
How it all began:
I wanted to update my Lumia, so used CAB sender. Fine so far, but there was a bug (no keyboard) so I wanted to repair with Zune. Didn't work, it said it was impossible to repair to the previous version (code 80180083). And since it didn't started up now anymore, it bricked.
Looking for a solution, my laptop OS (Windows Vista 32-bit) didn't recognized my phone anymore as Nokia Lumia 800, but simply as 800. And now, it only recognises my phone as Unkown Device (Qualcomm CDMA Technologies MSM). And Windows does not detects a proper driver for this thing. Tried Nokia USB Connectivity, WindowsUSB and the drivers belonging to Nokia Care Suite but nothing gets it done.
View attachment 1231319
I thought I found the solution with NSS, but I dont get the option below which says Nokia Connection Cable, because yet again: no phone can be found!
View attachment 1231326
Or course I tried also with Nokia Care Suite, but yet again: the laptop can't recognise the brick! Although Windows does notices I put something in the USB port and it sees the Qualcomm device.
Hard reset
Not possible, since I will get a 3 second vibration followed by 3 seconds nothing and then half-a-second vibration.
Putting phone on
If I try, it will give the 3 second start-up vibration which connects to Windows Vista (using the typical sound) shortly followed by the half-a-second vibration (and a triple-short disconnect sound on Windows).
As you guys can understand, I am in quite a bad situation now. Since the phone is bought in my home country The Netherlands and I currently live in Melbourne Australia, I hope to prevent sending it back home at any costs.
So what do you think: is this one permanently bricked, or is it still possible with a specific driver to fix this? Seems to me it's purely a communication/connection problem between my laptop and my phone, but I run out of options to try..
You could try downloading Windows Phone Support Tool from Microsoft.
Turn on your phone by pressing on and the Camera button at the same time, it should then enter flash mode (release power on buzz but keep holding the camera button). When it's in flash mode you can try and get Windows Phone Support Tool to repair the phone for you.
Thank you for your reply!
I tried it before, and this is the message I got:
Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool had difficulty communicating with your device. Please check your device connection and make sure you followed the instructions above. Try recovery again and if the problem persists please contact technical support.
No devices were found.
Click to expand...
Click to collapse
The problem seems to be that there is absolutely nothing is installed on my phone. Therefore, the connection with my phone fails over-and-over. Doesn't matters which program I use. I am almost sure that there is a connection fail between the computer and my phone. I tried it at some other laptops but at every laptop it says 'Qualcomm CDMA Technologies MDM'. But not a single program (NSS/NCS/Phoenix/Windows Phone Support Tool) can make an actual connection with the phone, so it must be driver related.
When I try to turn it on, it starts up but then puts itself off, like if its out of energy. It doesn't charges though. What do you think: driver related or battery related?
------------------
Extra added info: when I try to flash Rainbow os-new with NSS, I get this message:
Checking file selection...Done.
Looking for NAND disk...Not found.
Are you sure you have development Qcom loader ?
Click to expand...
Click to collapse
What does that means?
Some more info about using NSS in an attempt to try flashing my phone
(Command: Flashing > WP7 Tools > Write OS)
Checking file selection...Done.
Looking for NAND disk...Not found.
Are you sure you have development Qcom loader ?
----------------------------------------------------
(Command: Flashing > WP7 Tools > P**** FS)
Looking for NAND disk...Not found.
Things to check:
1. Is the phone connected?(Plug to the USB)
2. Is it in the correct mode?(Try to switch to OSBL mode)
3. Have you installed the Qcom loader ?(Use the Install button)
Preparing update...Done.
------------------------------------------
(Command: Flashing > WP7 Tools > Install)
Init connection...Phone not found!
Does this shows a battery problem? I have had battery problems before with my phone, but I guess that when I try to flash (even with the extra add to NSS) it should ignore any battery level. Or should I screw it open, try it again and see if it will work then?
If it's finding it as an 800 that means it's finding it (it finds mine as an 800 when I've played with it too much).
When you enter flashing mode via camera button, do you not get the image of the phone connected to a PC on the phone?
I had that in the beginning, but those days are long gone.. I don't know how it happened that I don't get that back anymore. Perhaps because my phone doesn't boots itself completely, but falls out of its boot program. Nothing visible on screen
First off, hi all.
I have a bit particular problem.
Few weeks ago I got my self a SGSIII for my birthday (already had one, but it got stolen), and since the beginning I've had the same problem: My computer won't recognize my SIII, not even as Unknown device, won't even charge it, only if I take out battery and get it back then plug it in - it starts to charge but again there is no sign of any kind of hardware being connected on the PC. The cable I'm using already got me connected with my previous SIII device to this very same computer, so you're thinking "it must be your new device then", but no - the same cable and same device work on my other computer.
SO; on my computer (with Win8), it wont connect in any manner - only charges if battery was just removed; it connects to my other computer thru same cable (this one has Win7); but the same cable connected my previous SIII to both Win8 and Win7 with this cable with no problem.
This is what I tried so far:
Kies unistall, install, reinstall, update - all that stuff
Driver only, uninstall, install, rebooting, installing blah blah - did that also
So; anyone here has any IDEA what is going on? Thanks in advance.
Question impossible to understand .
Return the phone to the vendor under warranty .
jje
JJEgan said:
Question impossible to understand .
Return the phone to the vendor under warranty .
jje
Click to expand...
Click to collapse
I'll try to simplify:
My SIII when plugged in to a computer - not recognized, not even as Unknown device in Device manager.
It does not even start with the charging, unless I remove battery and put it back in.
I thought the problem is with my Win8 pc, because my SIII works on my other pc (that has Win7). BUT my previous cellphone (also an SIII) was recognized every time on that same computer with that same cable. So I'm wondering if anyone had this problem or has a clue on a solution - the problem itself is not that hard to understand.
try to set: use as camera - works for me on win8
CsprDroid said:
First off, hi all.
I have a bit particular problem.
Few weeks ago I got my self a SGSIII for my birthday (already had one, but it got stolen), and since the beginning I've had the same problem: My computer won't recognize my SIII, not even as Unknown device, won't even charge it, only if I take out battery and get it back then plug it in - it starts to charge but again there is no sign of any kind of hardware being connected on the PC. The cable I'm using already got me connected with my previous SIII device to this very same computer, so you're thinking "it must be your new device then", but no - the same cable and same device work on my other computer.
SO; on my computer (with Win8), it wont connect in any manner - only charges if battery was just removed; it connects to my other computer thru same cable (this one has Win7); but the same cable connected my previous SIII to both Win8 and Win7 with this cable with no problem.
This is what I tried so far:
Kies unistall, install, reinstall, update - all that stuff
Driver only, uninstall, install, rebooting, installing blah blah - did that also
So; anyone here has any IDEA what is going on? Thanks in advance.
Click to expand...
Click to collapse
did you have usb debugging checked on your phone!?
My LG L9 Optimus P769BK (T-Mobile) is stuck on Boot Logo. Hard reset or any other reset procedure in this world does not recover the phone to a normal state.
History:
-I rooted the phone a few months ago in order to get rid of some of the bloatware
-Ever since adware/malware keeps coming which made my wife's life miserable
- I unrooted it but that didn't change anything, the malware now resides within system apps so the misery continues
-The USB drivers are installed and the connection shows three entries in Device Manager
-LGE Mobile USB Modem
-LGE Mobile USB Serial Port
-LGE Mobile Composite USB Device
These are shown only when the phone is in download mode (VolUp + USB Cable In)
The only software that communicates with the phone and recognizes the USB port connected (Com41) is the LG Flash Tool V1.8.1.
Unfortunately this software processes the first 80% successfully until the reset stage after which the phone get stuck at the bootup logo (non-responsive) and never finishes the started flashing process.
I just want to re-flash it with stock ROM for which I downloaded v20h_00.kdz and converted the other required DLL, FLS and BIN files.
I know this is an older model but it was seldom used and I don't want to trash it. Thanks for any response in advance.
PC Desktop: Windows 7, x32, Clean Installation just for this purpose
Update: OMAP driver added
I noticed that I was missing OMAP drivers that are specific for the TI chip this model uses and I did install them. Now the phone has a new entry in Device Manager as Portable Devices where two drives/partitions are listed (F:\ and G:\) These are visible while the phone is stuck on the boot LG logo. The LG Flashing tool still can't continue after the reset at 80% so there is no really any progress yet. Any clue anyone?
Problem solved
I finally solved my problem with LG-P769
I don't know why I couldn't succeed earlier but it turned out using a laptop is a bad idea. I tried Windows XP, Windows 7 and Windows 10. The final solution worked on my desktop with clean Windows 7. The solution was using the trick with Small HTTP server. I don't know why it didn't work earlier but it seems another thread gave me a little bit more details that I missed at the beginning (maybe the server settings)
Anyway, it seems that this phone model was long time forgotten since there was not a single reply to my original post except my two updates so it turned out I was just talking to my self loud, LOL.
Anyway, I would like to thank this forum for most advanced postings regarding the Android branch of cell phones. Regards to whoever found this interesting enough to read.
Hello Everyone
I am putting my problem in this general section with the hope to ask for help to more people compared to the Mate 8 section where not a lot of people go these days.
Since a while I am not able to connect my phone to a laptop. If I connect it to a laptop it just starts charging but nothing else. I have tried everything like:
Changing Cables (tried more than 5. I dont have the original anymore)
Changing Laptops
Changing the USB port of the phone itself
Updating Drivers
Installing Hisuite (current version 5.0.3.300)
Restore phone to factory settings
Complete formatting
Updating to the latest version (Current version Nxt-L29C185B582)
Changing the USB debugging/ Connection (MTP/PTP/etc)
And what not
The problem is, it doesnt get detected on the computer and cant connect to adb as well. All I want is to unlock bootloader and Install TWRP and Magisk. I have the unlock bootloader code but no way to unlock it since I cant connect.
Can anyone help me in fixing this stupid problem ? It is getting frustrating. If there is a hardware issue, what part needs to be replaced? Any help would be appreciated.
USB connection icon on top of the phone when connecting laptop
gandotratushar said:
Hello Everyone
I am putting my problem in this general section with the hope to ask for help to more people compared to the Mate 8 section where not a lot of people go these days.
Since a while I am not able to connect my phone to a laptop. If I connect it to a laptop it just starts charging but nothing else. I have tried everything like:
Changing Cables (tried more than 5. I dont have the original anymore)
Changing Laptops
Changing the USB port of the phone itself
Updating Drivers
Installing Hisuite (current version 5.0.3.300)
Restore phone to factory settings
Complete formatting
Updating to the latest version (Current version Nxt-L29C185B582)
Changing the USB debugging/ Connection (MTP/PTP/etc)
And what not
The problem is, it doesnt get detected on the computer and cant connect to adb as well. All I want is to unlock bootloader and Install TWRP and Magisk. I have the unlock bootloader code but no way to unlock it since I cant connect.
Can anyone help me in fixing this stupid problem ? It is getting frustrating. If there is a hardware issue, what part needs to be replaced? Any help would be appreciated.
Click to expand...
Click to collapse
Go to the Settings of your phone---> About phone----> Build number tap this 7 to 8 times-----> Developers option is enabled----> back to settings ----> go to developers option ----> enable USB debugging.
When you connect to the phone to the laptop you will find an icon on top of the screen of your phone with a USB mark "like a trident", pull down the top menu and find the USB connection tab, (like changing the sim card if you intend to call through a specific card) e.g quoted, double tap the USB tab to obtain options ---> 3 options 1) MTP 2)PTP 3) USB charging only----> select the first option MTP (Media transfer protocol).
Now connect to the laptop you will find exclamation marks in the device manager of your laptop. Load the appropriate drivers on your computer and viola! this will establish connection with the device you are having. if you find difficulty in installing USB drivers, search the thread "Attempt to load USB drivers for Micromax E484 on win XP is a fiasco" in this forum. You will find the solution for USB drivers
http://forum.xda-developers.com/android/help/attempt-to-load-usb-drivers-micromax-t3696432
Regards,
689alza
Thanks for your reply
Go to the Settings of your phone---> About phone----> Build number tap this 7 to 8 times-----> Developers option is enabled----> back to settings ----> go to developers option ----> enable USB debugging.
Already Tried
When you connect to the phone to the laptop you will find an icon on top of the screen of your phone with a USB mark "like a trident", pull down the top menu and find the USB connection tab, (like changing the sim card if you intend to call through a specific card) e.g quoted, double tap the USB tab to obtain options ---> 3 options 1) MTP 2)PTP 3) USB charging only----> select the first option MTP (Media transfer protocol).
Already tried too
Now connect to the laptop you will find exclamation marks in the device manager of your laptop. Load the appropriate drivers on your computer and viola! this will establish connection with the device you are having. if you find difficulty in installing USB drivers, search the thread "Loading USB drivers in Win XP turned to be a fiasco"
Nope. Doesnt happen
When i connect with the laptop, my laptop doesnt even make that sound for the connection.
What is the model and OS version of the device and the model and OS version of the computer? According to your symptoms your phone appears to be in option 3) USB charging only. The phone will not be detected by your laptop or the like(Computer) in this mode. Merely remains in a charging state. Are you certain the option 1) is picked MTP? If the phone is not detected there appears to be some hardware failure, try another USB port to connect to the laptop. if all else fail a service technician will pinpoint the fault. It may perhaps be a data transmission failure of the devices port to the interior of the phone. This is merely an assumption.
best remedy would be a service technician.
Hope this helps
689alza
alza689 said:
What is the model and OS version of the device and the model and OS version of the computer? According to your symptoms your phone appears to be in option 3) USB charging only. The phone will not be detected by your laptop or the like(Computer) in this mode. Merely remains in a charging state. Are you certain the option 1) is picked MTP? If the phone is not detected there appears to be some hardware failure, try another USB port to connect to the laptop. if all else fail a service technician will pinpoint the fault. It may perhaps be a data transmission failure of the devices port to the interior of the phone. This is merely an assumption.
best remedy would be a service technician.
Hope this helps
689alza
Click to expand...
Click to collapse
I have tried changing the usb charging only to all possible options but it still is the same. I tested in Linux and when I connect the phone nothing shows up in the logs. It's like it's not being connected . I have tried changing the usb port itself from the phone but it remained the same.. can the flex cable be a problem ? Mate series was never launched in India so I don't have any help from the service centre. I have to order the spare from eBay.com so there is no qualified technician who can help.. that's why I have to fix it myself somehow..
Thank you for your help
gandotratushar said:
I have tried changing the usb charging only to all possible options but it still is the same. I tested in Linux and when I connect the phone nothing shows up in the logs. It's like it's not being connected . I have tried changing the usb port itself from the phone but it remained the same.. can the flex cable be a problem ? Mate series was never launched in India so I don't have any help from the service centre. I have to order the spare from eBay.com so there is no qualified technician who can help.. that's why I have to fix it myself somehow..
Thank you for your help
Click to expand...
Click to collapse
I quite doubt the cable will be the culprit as your device charges the battery while in an established connection with the laptop. As you state the phone USB port was replaced, it could be a some glitch before the USB port in the device where there is an interruption in the data transmission signal that cannot be detected by your laptop.
Could you boot your device, computer and connect the two and take a snapshot of your device (whilst connected to the laptop) and paste the same in the forum?
Perhaps visual cue could be better at dealing such mishaps.
alza689 said:
I quite doubt the cable will be the culprit as your device charges the battery while in an established connection with the laptop. As you state the phone USB port was replaced, it could be a some glitch before the USB port in the device where there is an interruption in the data transmission signal that cannot be detected by your laptop.
Could you boot your device, computer and connect the two and take a snapshot of your device (whilst connected to the laptop) and paste the same in the forum?
Perhaps visual cue could be better at dealing such mishaps.
Click to expand...
Click to collapse
Yes of course. It is connected to a computer now. You can see it getting charged but that's about it
alza689 said:
I quite doubt the cable will be the culprit as your device charges the battery while in an established connection with the laptop. As you state the phone USB port was replaced, it could be a some glitch before the USB port in the device where there is an interruption in the data transmission signal that cannot be detected by your laptop.
Could you boot your device, computer and connect the two and take a snapshot of your device (whilst connected to the laptop) and paste the same in the forum?
Perhaps visual cue could be better at dealing such mishaps.
Click to expand...
Click to collapse
Can it be something because of some wrong flash ? This problem has survived through 2 versions and 1 system upgrade through firmware finder .. and a complete format
USB trident is not seen on the device
gandotratushar said:
Yes of course. It is connected to a computer now. You can see it getting charged but that's about it
Click to expand...
Click to collapse
Your USB trident icon is not indicated on the device, If you were to receive power from the laptop the trident would be displayed on top of the screen, even for charging the battery. The power source for your device appears to from other than the laptop.
I have pasted my device after connecting to the computer and the second icon from the top left is the USB Trident icon indicating connection with my laptop. Have taken the snapshot of the menu that I was describing .
I strongly feel you have a hardware failure rather than a simple fix and would require the help of a technician (ordinary if professional is unavailable). Am skeptic you could mend that on your own unless you are proficient in electronics. This mishap is not due to flashing wrongly too, unless you have changed the stock ROM with some custom ROM which has some bug that affect the USB alone.
Take the assistance of a technician whether professional or less is my counsel
Thank you
alza689 said:
Your USB trident icon is not indicated on the device, If you were to receive power from the laptop the trident would be displayed on top of the screen, even for charging the battery. The power source for your device appears to from other than the laptop.
I have pasted my device after connecting to the computer and the second icon from the top left is the USB Trident icon indicating connection with my laptop. Have taken the snapshot of the menu that I was describing .
I strongly feel you have a hardware failure rather than a simple fix and would require the help of a technician (ordinary if professional is unavailable). Am skeptic you could mend that on your own unless you are proficient in electronics. This mishap is not due to flashing wrongly too, unless you have changed the stock ROM with some custom ROM which has some bug that affect the USB alone.
Take the assistance of a technician whether professional or less is my counsel
Thank you
Click to expand...
Click to collapse
I did flash a different rom .. but then back to stock recently.
I can do basic electronics but the if the problem lies in Mobo .. then nothing can be done .. as I don't have the spares available in India. But I would hate to lose this phone as it was a perfect fit for my needs
gandotratushar said:
I did flash a different rom .. but then back to stock recently.
Then the question of wrong flash or ROM issue does not arise
I can do basic electronics but the if the problem lies in Mobo .. then nothing can be done .. as I don't have the spares available in India.
If you do not have spares is best left alone rather than tampering with it and rendering the device useless if any untoward incidents tends to occur.
But I would hate to lose this phone as it was a perfect fit for my needs
Send to the vendor directly if you have warranty for the device stating its complaints or request your relative or friends who live in the area where you bought your phone to hand it to the vendor or service technician and bear its expenses
Click to expand...
Click to collapse
Thank you
alza689 said:
Thank you
Click to expand...
Click to collapse
Is there a way to unlock bootloader somehow without connecting to usb ? That would also solve the purpose.. I want to root it for some of the things to work and with the latest upgrade to latest version I lost the unlocked bootloader and root.. if somehow I can unlock and root .. I should be fine without the usb connection to computer.. but I have ran out of ways
Does Kingroot work for you?
I mean did u try it or u just want magisk?
If u didn't, kingroot may be able to root ur device and unlock ur bootloader, then u can flash TWRP using rasher.. & make a backup BTW...
After that, try using the adb sideload in TWRP to test ur connection with ur computer.
TWRP for ur device : (q.gs/DxuAH)
There is a way to unlock bootloader without USB via developers option.
Go to settings-----> About phone-----> Build number ( Tap this option around 7 or 8 times) till developers option is enabled------> go back to settings-----> developers option-----> OEM unlock option (Enable this option) to unlock the bootloader.
Xeedius said:
Does Kingroot work for you?
I mean did u try it or u just want magisk?
If u didn't, kingroot may be able to root ur device and unlock ur bootloader, then u can flash TWRP using rasher.. & make a backup BTW...
After that, try using the adb sideload in TWRP to test ur connection with ur computer.
TWRP for ur device : (q.gs/DxuAH)
Click to expand...
Click to collapse
Thank you for the advice.. I hadn't tried it earlier but after your suggestion I did.. kingroot says I need to unlock my bootloader to root it.. so I am back to square one..
alza689 said:
There is a way to unlock bootloader without USB via developers option.
Go to settings-----> About phone-----> Build number ( Tap this option around 7 or 8 times) till developers option is enabled------> go back to settings-----> developers option-----> OEM unlock option (Enable this option) to unlock the bootloader.
Click to expand...
Click to collapse
This gives me an frp unlock and not a phone unlock.. still not able to root
There is no FRP unlock.
gandotratushar said:
This gives me an frp unlock and not a phone unlock.. still not able to root
Click to expand...
Click to collapse
There is no FRP unlock, to circumvent FRP you need to factory reset or flash your firmware. The above quotation was to unlock the boot loader as you cannot access through your computer. Your sole option to unlock boot loader was through the above directions.
Moreover, King root application never ask for boot loader to be unlocked. Although a little unstable this is the initial program to root any device. Once you have the TWRP setup then you could switch to Super Su etc. according to your preference.
Could you paste your developers option snapshot here...
Regards,
689alza
gays
me too have this problem ( only usb port for charge and other option's not work)
and i want back to orignal system
and i want know how download orignal system (from Huawei web site) to my phone
can any one help me how
or how can fixed this problem
and i have other problem
when i try to boot to TWRP phone stay on " your device is booting now..."
so any one can help me how reinstall TWRP without PC or why this problem ??
TWRP is not installed duly on your phone
Hello! Omar Dahy,
OmarDahy said:
gays
me too have this problem ( only usb port for charge and other option's not work)
Connect your phone to your computer or laptop, a trident icon appears on your phone notification area, pull down the notifications and identify the notice as USB connection, tap twice you willk be provided with options.
and i want back to orignal system
and i want know how download orignal system (from Huawei web site) to my phone
My phone was Micromax and I am not aware of your phone's firmware, try and google or search the Xda developers forum under your phones model number for the original firmware.
can any one help me how
or how can fixed this problem
and i have other problem
when i try to boot to TWRP phone stay on " your device is booting now..."
Your phone has not installed TWRP duly, therefore it boots straight to the system. Search again in this XDA forum, with your pnone name and model number to obtain instructions
so any one can help me how reinstall TWRP without PC or why this problem ??
Click to expand...
Click to collapse
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.