I accidentally bricked my Nexus 9 recently. It won't boot up, and I'm getting the red "your device is corrupt" message. Normally, you would connect the device to your computer via USB and use the Android Debug Bridge to unlock the bootloader, and flash a new system image. However, the tablet doesn't show up when I connect it to my laptop and run ./adb devices. Anybody know why this could be happening? More specifics:
* I walked around outside with it, and it rained lightly a bit. It had a case and screen protector on it, so I didn't worry. Later, I noticed that the speakers were acting funny, but rebooting seemed to fix that. Later, USB Debugging with Android Studio wasn't working, and it wasn't showing that it had been unplugged when it had been. Then, I tried to install 6.0.1 OTA, and that failed, bricking the device, and I got the "your device is corrupt message."
* I cracked open the back cover to peek inside for moisture, but I didn't see any. (I didn't take the cover all the way off though, didn't wanna have to reattach the camera.
* I have tried factory reset from the bootloader a few times -- I don't think I gave it enough time the first time, the second time it ran out of battery, and the third time I let it run overnight while it was plugged in. When I checked it in the morning, it had powered down, and nothing seemed to have changed.
* I have the latest version of ADB and platform-tools, and I've got some experience with the SDK. I also tried using different USB cables to connect, no luck there.
* I can't access the OS at all, just the bootloader and recovery mode.
* The tablet is a black 32GB Nexus 9, formerly running stock 6.0.0. The laptop I'm using is Linux Mint 17.2.
* The bootloader is locked, I never had any reason to unlock it. I didn't enable OEM Unlocking in the Developer Options in the OS either, but that shouldn't prevent it from connecting to the ADB.
* I got into recovery mode, and wiped the cache partition, but that didn't seem to do anything.
* I got it from BestBuy more than a year ago, so I'm pretty sure it's out of warranty.
Does anybody have any ideas about how I could get my tablet to connect to the ADB? Thanks.
Have you tried this?
http://forum.xda-developers.com/nexus-9/help/marshmallow-ota-update-bricked-nexus-9-t3334871
if it doesnt works maybe I have the same problem that you have.. (read that topic and read my comments :/)
No, I hadn't tried sideloading the OTA, thanks! I tried it, and it worked, so now I'm all set! Thanks so much!
Apparently adb devices only works when the device is fully booted into the OS, but fastboot devices and adb sideload will work when you're in recovery mode, the way I understand it.
Sorry you're having trouble, hope you find a solution!
weirdo16 said:
I accidentally bricked my Nexus 9 recently. It won't boot up, and I'm getting the red "your device is corrupt" message. Normally, you would connect the device to your computer via USB and use the Android Debug Bridge to unlock the bootloader, and flash a new system image. However, the tablet doesn't show up when I connect it to my laptop and run ./adb devices. Anybody know why this could be happening? More specifics:
* I walked around outside with it, and it rained lightly a bit. It had a case and screen protector on it, so I didn't worry. Later, I noticed that the speakers were acting funny, but rebooting seemed to fix that. Later, USB Debugging with Android Studio wasn't working, and it wasn't showing that it had been unplugged when it had been. Then, I tried to install 6.0.1 OTA, and that failed, bricking the device, and I got the "your device is corrupt message."
* I cracked open the back cover to peek inside for moisture, but I didn't see any. (I didn't take the cover all the way off though, didn't wanna have to reattach the camera.
* I have tried factory reset from the bootloader a few times -- I don't think I gave it enough time the first time, the second time it ran out of battery, and the third time I let it run overnight while it was plugged in. When I checked it in the morning, it had powered down, and nothing seemed to have changed.
* I have the latest version of ADB and platform-tools, and I've got some experience with the SDK. I also tried using different USB cables to connect, no luck there.
* I can't access the OS at all, just the bootloader and recovery mode.
* The tablet is a black 32GB Nexus 9, formerly running stock 6.0.0. The laptop I'm using is Linux Mint 17.2.
* The bootloader is locked, I never had any reason to unlock it. I didn't enable OEM Unlocking in the Developer Options in the OS either, but that shouldn't prevent it from connecting to the ADB.
* I got into recovery mode, and wiped the cache partition, but that didn't seem to do anything.
* I got it from BestBuy more than a year ago, so I'm pretty sure it's out of warranty.
Does anybody have any ideas about how I could get my tablet to connect to the ADB? Thanks.
Click to expand...
Click to collapse
If you were using a waterproof case it should not be damaged and even without a waterproof case you shouldn't get water damage in light rain. The speakers thing happened to someone with a S7 after they put it under water but it went away.
Can you charge the tablet. Maybe the USB port is broken and needs to be replaced.
One small tip : Before I run the OTA update I always enable OEM Unlock so I can flash if it bricks. My Nexus 9 has never got bricked for a OTA but it could happen
Related
Hello to all since this is my first post on these forums! And to just say thank you to everyone who will respond to me if I don't say it.
I rooted and installed CWM 6.0.1.8 on my phone about a year ago. I did not unlock the boot loader, because I didn't want to have any custom ROMs on my phone. Now just recently I was looking at android 4.4 and thought that this is a good update for any phone. So, I started to do my research for what to do to flash a ROM. I downloaded CWM 6.0.4.5 on my micro SD card and used "[ROOT]Recovery Tools - Flasher". Now this is where everything goes south...
I went through the app, found the CWM file to flash, and then I got the security error... After researching why this happened it was because of not unlocking the boot loader which was a huge mistake that I forgot to do.
I have searched on here a lot. I found a lot of great and useful information, but I can't try any of the suggestions yet. Not until my computer can recognize my phone. I know before this all happened, I had debugging enabled on my phone. I do not have fastboot installed on my computer anymore (reformatted a long time ago). I do have B2CApp.exe installed so I could try to do a factory reset on my phone. I have installed the driver for the phone from the LG program and from their website.
But like I said before, when I plug in my phone to my computer, the computer does nothing. It doesn't recognize that there is even a device there, but there is power getting to it. How I know is because I took out the battery and "S/W Upgrading" could be enabled.
If I can get past this, I'm 100% positive I can fix it then. If anyone has some sort of useful information about my computer not recognizing my phone, please share it! Also, for context, my computer is a windows 7 x64.
Thank you for your time and your responses!
Paul
Well I haven't heard from anyone yet and I've been still digging around. I might know why my computer doesn't discover my phone. I think it has to do with the charging port. It makes sense since that is where the connection lies. And I already know that my cords are all good as well as my computers. But anyways, I have bought a replacement part and hopefully that fixes the issue.
I'll post my results as soon as I replace the part. Wish me luck!!
Paul
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
Long story short, i did not unlock my bootloader, as this was for my son and I didn't want to get into a habit of updating roms, blah blah blah. Well lessons learned, for the 2nd month in a row an OTA broke my sons tablet, bootloop, can't mount cache to wipe. Last time I was able to plug it in, reload the OTA via ADB sideload. However, no such luck this time. I cannot get windows 10 to see the tablet at all. nothing happens at all when I plug it in. No dings, nothing pops up in device manager, nothing shows up if I scan for it. This is consistent while its bootlooping, hboot, fastboot and in adb sideload from recovery. I've tried several micro USB cables. I do recall having similar issues last month, but eventually one of my cables worked. I do not have that cable with me at the moment and not even sure if it would work this time.
Let's pretend by some miracle I can get this recognized again to reload the OTA, is there anyway I can backup my son's data prior to unlocking the bootloader and rooting? Should have known it would be better to keep it unlocked and rooted.....
ok so fastboot factory reset, did not help, i again had bootloop, wiped cache and that seem to actually be successful this time, but still bootlooping when trying to boot up, and cannot get windows to recognize it any way shape or form in fastboot, recovery, hboot, recovery adb sideload, windows never recognizes it, tried a 2nd machine same result, windows doesn't even attempt to install a driver. The only thing left for me to try is the recovery wipe data/factory reset, which I will be trying shortly once I get some juice, unless someone has a better idea. I'm already past the point of data recovery anyway I presume....son is going to be so disappointed.....
I'll have to say having owned the nexus 7, nexus 7 2, galaxy nexus, nexus 5, nexus 6, nexus 6p and the nexus 9....the Nexus 9 has been the biggest piece of junk...
Sorry I didn't see this sooner. I've had exactly the same issue (N9 not being recognized when it had been windows 10, too. What worked for me, twice, was removing all drivers related to usb then allowing pc to re-install thereby giving me the opportunity to grant the pc/tablet permanent access. I can't remember if I had to choose HBOOT to be recognized. The first time, I followed Wug's NRT toolkit for removal and re-install of drivers (adb). The second time, I think I just used usb deview to wipe drivers. Of course, this messed up the situation for my N5 and N5x (the only device not unlocked and rooted). Those drivers repopulated though. At least you had the foresight to tick off "enable OEM unlocking " as well as adb debugging. Now, if you must, you can start from the beginning.
Yes, I've never had a Nexus device quote like this one. Of the new HTC Nexus phones are priced as suggested, my N5 won't get updated this year. I cannot trust htc after this experience and definitely will not pay a premium to repeat this experience.
Unlocked bootloader has no effect on flashing ota's.
Sent from my Nexus 9 using Tapatalk
Yeah, the problem seems to be with the port, as holding one of a various amount of cables just the right way at least gets W10 to recognize it and install drivers, but it immediately detaches and can no longer see the device. It's unfortunate, as I'm not sure right now what to replace his N9 with. Pixel is just to expensive, and everything else seems to be getting pretty dated.
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.
Hi, I've got a 7.1 which recently became unresponsive. I think I've tried the basic stuff, but I'm out of my league with this phone.
Screen is black and I always thought it just wasn't powering up because the battery was dead but after messing around I found windows seems to be able to mount/dismount because I hear the sounds sounds and device manager shows a QUSB_BULK device and the yellow triangle! symbol. I tried looking for drivers, but thought it's PNP.
ADB devices comes back with nothing, so maybe it's a driver thing, but it was a generic PNP device before and I don't think that would have changed.
I'd really like to wipe the phone, but I've exhausted all the options I know of.
I also don't want to install any non-official firmware because there may be a chance this could get sent in if any wipe/reset attempts aren't successful.
Is there a guide I could use? I think it's a bad sign that ADB can't even locate the device.
FWIW, I likely had developer option enabled, but can't say for sure. I can't unlock the phone now because I can't see anything. I've tried a bright light to see if it's a backlight issue but couldn't make out anything.
Is there any chance a screen protector could have caused a problem? It's got one and I haven't removed in the event it can be woken up...
Thanks
I'm wondering if I've got a bad adb, I tried two other devices, one LG which is stuck in a reboot loop and a zte which boots. In all cases the adb I'm using shows no devices with a
Code:
adb devices
running on win10 with adb found in platform tools r32.0.0.
Are you sure you have ADB enabled in developer settings?
Andrive said:
Are you sure you have ADB enabled in developer settings?
Click to expand...
Click to collapse
Not 100%, but it is something I normally would do for the rare occasion where it's needed.
Are there options to reset/update if adb isn't enabled? I'm pretty sure update is no, but I'm not sure about reset.
I think I've exhausted all options to get this this back myself and will likely see what Nokia charges to bring it back...