I recently got an HTC 10, and observed this immediately with the unmodified Verizon-branded firmware. I then got the phone S-OFF'd, and installed the latest "US Unlocked" firmware direct from HTC's website, and then observed the same thing:
When USB debugging is enabled, it immediately accepts the connection, without first prompting with the host's RSA key. Tapping "revoke authorizations" does nothing, other than prompt you.
The only upshot is that it seems MTP File Transfer has to be enabled first for each USB connection, otherwise the default is charging only and adb won't connect. Still, I'd like to know why the RSA authentication is broken and whether or not it can be fixed.
I noticed the same exact thing a couple of years ago, in fact, on my HTC M8. However, I had simply assumed it was broken in the custom ROM I was using, and anyway, it went away once I switched to the (official) GPE firmware. Now, with the 10, I'm seeing it on the unmodified vendor ROM.
Anyone have any idea, what's going on here?
Related
I need to retrieve a file off a phone that has been incapacitated by an OTA update gone bad.
I figure my best hope is to use adb to do a pull of the relevant file.
However, this phone did not have USB Debugging enabled when the OTA update went south. While the phone boots to a desktop, it ignores most user input.
Phone is a Moto Droid X. OTA Update was from Froyo to Gingerbread (or so I am told). Phone was never rooted.
After a battery pull/reinstall, I can power on the phone. The Moto logo is now red, and it comes up to the desktop. However, I can only get in a few UI manipulations before the phone 'freezes'. Once in a 'frozen' state, the only UI element the phone responds to is the power button. Eventually, that also becomes unresponsive.
I can invoke the recovery console. I have cleared cache, but the issue still exists. I cannot do a factory wipe, as that will wipe my data.
I bought a second Droid X, and have reinstalled all the critical apps on that unit. However, the database for the gbaHours app is worth several thousand dollars to me. I need to retrieve it off the old phone.
I have used the new phone to validate an install of the Android SDK and adb communications with the new phone.
I remain stuck, however, in getting USB debugging enabled on the old phone, due to the UI 'freeze'.
Any suggestions?
Nexus 5 running 5.1 stock
I had recently and sadly had an accident with my phone where the screen is completely useless. Shattered is a harsh word, but it's sitting in that condition. It does however still turn on. There are parts of the screen that display, but for some odd reason, its completely mirrored and upside down.
I have Android tools and drivers installed. And knowing something like this might happen, I had USB debugging enabled. BUT, for even stranger reasons, I'm guessing it's disabled because through cmd on platform-tools, it says it's unauthorized. Though the little window of display my phone pushes, I'm guessing I'm getting a dialog asking for USB debugging to be enabled. I'm not too sure how I got to this window, but it randomly appears on restarts of the device, and half the time, it just restarts normally like any restart.
I was wondering if there was a way I can push a command line using cmd on my PC to accept or continue from the dialog box that I literally can't see.
I looked far and wide on Google and this beloved website, but am having a hard time finding a solution.
The device is bootload unlocked, running stock on Lollipop.
I do not know if rooting and installing TWP will affect my data, as it is the only thing I really don't want to lose. I wish to keep stock as I am completely fine with it and I have tried custom Roms, but I still wish to continue using stock.
I'm not too familiar with some words used in explanations on this site, so please respond as if I'm 7 years old :silly:
My initial goal was to (while having usb debug enabled) fastboot (i think i'm using the right term) Mobizen, then mirror the screen on my pc, and control the device to upload everything to my cloud storage.
momostarz said:
Nexus 5 running 5.1 stock
I had recently and sadly had an accident with my phone where the screen is completely useless. Shattered is a harsh word, but it's sitting in that condition. It does however still turn on. There are parts of the screen that display, but for some odd reason, its completely mirrored and upside down.
I have Android tools and drivers installed. And knowing something like this might happen, I had USB debugging enabled. BUT, for even stranger reasons, I'm guessing it's disabled because through cmd on platform-tools, it says it's unauthorized. Though the little window of display my phone pushes, I'm guessing I'm getting a dialog asking for USB debugging to be enabled. I'm not too sure how I got to this window, but it randomly appears on restarts of the device, and half the time, it just restarts normally like any restart.
I was wondering if there was a way I can push a command line using cmd on my PC to accept or continue from the dialog box that I literally can't see.
I looked far and wide on Google and this beloved website, but am having a hard time finding a solution.
The device is bootload unlocked, running stock on Lollipop.
I do not know if rooting and installing TWP will affect my data, as it is the only thing I really don't want to lose. I wish to keep stock as I am completely fine with it and I have tried custom Roms, but I still wish to continue using stock.
I'm not too familiar with some words used in explanations on this site, so please respond as if I'm 7 years old :silly:
My initial goal was to (while having usb debug enabled) fastboot (i think i'm using the right term) Mobizen, then mirror the screen on my pc, and control the device to upload everything to my cloud storage.
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please direct your question here for further assistance:
http://forum.xda-developers.com/google-nexus-5/help/help-thread-nexus-5-question-t2496506
Good luck!
So my G8141 recently started rebooting whenever it would get disconnected from an audio out source via the headphone jack. That's been happening for about two days. Today, I had it plugged into my car, shut my car off, and my phone rebooted. And continued rebooting. Endlessly. Only way I managed to get it to shut off was Volume Up + Power + Camera (not sure what about that specific sequence did it, but I got one vibration followed by three vibrations, let go, and it was off). I got home, held Volume Down, plugged it into my Windows computer. The LED came on green, Windows found a new device...and nothing. Granted, I just wiped my desktop, so I don't have any of my android debug stuff installed, and I never got around to installing the drivers for this phone before now. So I downloaded the drivers from Sony, tried to install them, and...nothing. Windows says it can't find a driver for the device in the directory. Am I missing something, or is the phone FUBAR?
The phone already needs to go back to Sony for repair (the back cracked about a week after I got it)...do I have any shot of salvaging what's on it before sending it in? I don't think there's much if anything that's important, but I'd like to see what I can do before sending it in...because I bought the UK model from the UK and live in the US...so I have to ship it to the UK repair facility, per Sony help. Also, if I can get it working again, I'm not terribly worried about the back now that I have a case on the way, so I may just live with the cracked back, as long as the phone is stable.
Update: Plugged it into my work MacBook Pro, fastboot devices is giving me
Code:
???????????? fastboot
Same result whether sudo-ed or not.
---
Update 2: fastboot reboot-bootloader followed by fastboot devices lists an actual device. LED is blue. Progress?
Never unlocked the bootloader on this phone, so not sure what I can do from here...thoughts? I can't tell if it's a hardware issue or a software issue...device has updated a couple of times, so it's possible one of those updates introduced a bug. That said, the spontaneous reboot feels more hardware-y to me...reminds me of a PC with bad memory or something. If I could somehow get logs out of it, I suspect I'd find a kernel panic in there.
---
Update 3: Contacted Sony Support, they suggested using Xperia Companion to "repair" the phone. Currently doing what I believe is a stock reimage of the device using Companion. Next step is probably sending it to Sony UK :-/
Just a note for others that might be interested, green is download mode, blue is fastboot.
Well if you haven't unlocked bootloader just repair it? I don't really understand what the issue is about in your post.
My wife's Pixel 3 XL hard-bricked a couple of nights ago. This seems to be a fairly common issue possibly related to recent updates to the phone. Here are a couple of example forum posts on the same issue:
https://www.reddit.com/r/GooglePixel/comments/miltpe
[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting...
forum.xda-developers.com
Pixel is not working. qusb__bulk - Google Pixel Community
Honestly, there are many more posts, but they're all pretty similar. From reading many MANY topics over the last 48 hours ago, I've been able to figure this much out: There is a potential way of un-bricking the phone using Qualcomm's QFIL tool with the proper files for the Pixel 3 XL (.mbn and a couple of .xml). HOWEVER, these files are very specific to the phone and are nowhere to be found, and even if I could find them, I can't actually get the phone to connect to QFIL (or to the QPST Configurator). It detects the chip on a COM port, but then just stays stuck at "downloading" (the loading bar under state stays stuck at about 1/5 way).
Both adb and fastboot don't recognize the device, and neither does QFIL. So at this point, I'm pretty well ready to say that I'm SOL. So I'm pretty well giving up on the idea that I'll be able to bring the phone back to life, but I'm still wondering if there's some way that I can recover the data from the phone when it's this far gone. None of the usual methods work since the phone would need to be recognized in a higher-level state than just recognizing the Qualcomm chip. And since the screen doesn't react, I have no idea if the button combinations I'm pressing are actually getting me into the bootloader menu or not. Heck, maybe it's so far gone that I can't even get that far.
So my question is this. Is there some low-level method I could try to recover the data off the phone when it's in this state? Any input is appreciated!
If USB MTP Mode was enabled on bricked phone it may possible to access the phone's data you are interested in to recover: This requires an USB-connection via USB-C cable what Pixel 3 phones support by default.
jwoegerbauer said:
If USB MTP Mode was enabled on bricked phone it may possible to access the phone's data you are interested in to recover: This requires an USB-connection via USB-C cable what Pixel 3 phones support by default.
Click to expand...
Click to collapse
Thanks for the reply, but MTP is not possible in this state. The phone would need to be functional for MTP to be enabled.
I'm in the same situation, need .mbn file so I can use the Qualcomm EDL mode to try and bring the thing back to life.
So I had a broken USB port for a while, but since I want to pull data off my phone (including, if possible, the apps that I needed 2FA to enable like WhatsApp and so on, since I'm currently in Europe for the next 6-12 months and AT&T prepaid doesn't allow me to receive text messages or phone calls).
I bought a replacement daughterboard for the USB connector, and pulled the back of the phone off, removed the old USB connection board, and replaced it with this one. However, I've got some weird problems and I'm not sure if its hardware or software related.
When plugging the phone into USB, there's no indication on the telephone that the phone is charging, there's no indication that the phone has some connection to the computer, the computer doesn't display anything about the phone or allow me to access storage, and ADB can't find the device despite trying about 7 different methods and combinations of drivers, ADB programs, etc.
So I'd believe that my new daughterboard is either broken internally or some other issue ... except ODIN works flawlessly, as I got the inital step of loading the combo firmware to work without issue. (linked here: https://forum.xda-developers.com/t/root_method_rev_b-11_bootloader_using_combo_firmware.4374741/). But I can't get safestrap to work, because it relies on ADB, and ADB still doesn't have any way to connect to the device.
When I start the phone in download mode, I'm able to pull up a device with the Hardware ID USB\VID_04E8&PID_685D&REV_0100, but ADB doesn't recognize it. When I start the phone in any other method, the device doesn't register in device manager. It's a similar story when I tried reaching the phone with ADB from my linux desktop, as "something" exists in download mode, but adb has no ability to actually see the device or make a connection.
As far as avoiding obvious pitfalls, I enabled development mode / USB debugging / OEM unlock in the stock firmware I was running before, and also enabled dev mod/usb debug in the flashed firmware from that page.
It's quite possible that flashing the Combination firmware already wiped my data, as I'm not sure if it does it or not (after scouring the internet, it's pretty much the only option to get root with the B/11 bootloader so it was worth a shot), but ultimately I'd like to try and resolve this ADB issue so that I can actually finish the steps and see if it will work or not.
I just don't know what to troubleshoot next to try and get ADB to work.
To add on to this, I tried reaching out to AT&T to see if I can use my S8+ (VoLTE and all that jazz capable) to receive text messages while abroad here, but they won't let me use the phone even though I'm already abroad, since if it's not compatible with their network in the US it won't be compatible with their roaming network abroad. So I really do have to do the ole root trick.