My set cannot be connected by usb so I tried to use adbwireless. Managed to get connected and device put online. However after putting the device in bootloader, I lose connection because it kept saying < waiting for device > in the command line without any action taking place. I need to unroot my device to send it back to Asus. The usb problem and the speakers went kaput too!
Anyone with experience in adbwireless so that I can do the work through it. I tried to google for more info but only the same..
Thanks
K
fastboot and adb are not the same thing.
You will never be able to communicate with the bootloader (for instance to lock the bootloader) via adb - or via any networking for that matter.
If you think the reason your USB port is not working is due to mechanical damage your best bet is to replace the small sub-assembly that has the USB connector and the headphone jack . See the iFixit teardown of the N7.
By building your own variant of a Stock ROM installer it would be possible to flash a stock ROM and stock recovery in one pass; but to lock the bootloader requires the tablet to be in fastboot mode, and afaik there is no networking possible in that mode using publicly disclosed methods.
The micro USB port on my Nexus 7 is damaged. It can not connection to a PC or charge.
(Now I charge my Nexus 7 with the Asus Nexus 7 Dock.)
I have an RMA to send it back to ASUS, but the boot loader is still unlocked. Is there anyway to re-lock it without a PC connection?
TL;DR: No.
There is an old post (here on XDA) that suggests that the bootloader lockstate can be controlled by flashing the correct partition with a previously recorded snapshot of the bootloader.
But doing this requires that you actually go through the process of locking and unlocking the bootloader, and capturing a raw dump of the bootloader in both the locked and unlocked state. Apparently, you can't just get this dump from someone else - there is some crypto signing that goes on that uses some unique keying material from the tablet, so the signed-lockstate area is unique on every tablet.
Anyway, the point is that you can only use this if you prepared for this in advance - you can't do it after you have lost the ability to communicate with fastboot.
You might want to go online and have a look at the iFixit teardown - the USB connector is on a small daughter-board connected to the mobo with a flex cable. IF you can find that part, it should be fairly inexpensive.
good luck
Hello!
I looked through the threads and I found a lot of people writing about their destroyed screen and solutions.
Unfortunatelly, I haven't found a similar problem to mine.
So here are the facts:
- Nexus 4 with stock Android 5 Lollipop
- Rooted
- Pattern locked screen
- Touchscreen doesn't work anymore, because screen is cracked
- USB Debugging enabled, but computer is not trusted
- TWRP installed
So I can't just enable adb sideload or something in recovery because it requires my touchscreen and I cant unlock the screen in order to access my files.
I read following thread: http://forum.xda-developers.com/showthread.php?t=2786395 about how to control a device with your PC. However, the tool can't find my Nexus, I think it's because my PC is not a trusted debugging device.
Also I'm afraid the stock kernel doesn't support USB OTG, so this isn't an option either and I can't just sideload another kernel or recovery because TWRP requires touch function.
I hope you can help me asap!
Hi all,
My Samsung Galaxy S7 Edge (SM-G935FD) has broken screen after a drop. The screen is black or flickering with green, but I think that it still reacts to touch. The firmware was upgraded to Oreo stock very recently, and the phone is not password or pattern protected. USB debugging is disabled (it has never been enabled) and the phone is OEM protected, so flashing a custom recovery with ODIN doesn't work (I tried). I'd like to backup the data, and I need to find a way to enable USB debugging for that. I see two options:
- Boot into maintenance mode to activate USB debugging in spite of the black screen, using physical keys. The thing is that I can't seem to boot into maintenance mode with that version of the phone following instructions found online (maybe this maintenance mode is specific to some versions or carriers, or am I missing something here?).
- Blindly activate USB debugging using an external keyboard. To do that, I would greatly appreciate help from one of you to know the exact sequence of keys.
Hope I can get this working!
Thanks
No one with a keyboard and OTG adapter to help me on that?
Thanks!
Hi XDA!
(tl;dr - The "specific technical questions" are in the last section. )
I'll spare everyone a detailed explanation of what I've been through with this phone in the last few weeks, except to say that I have exhausted all simple solutions.
The current state of the phone is that both its main and recovery partitions hang with a white LED.
There are two states in which I understand it should at least register to a USB host as a visible device, whether or not proper drivers are installed (though I have tried many drivers as well):
1. FastBoot
I can Power+Vol-Up into the FastBoot menu, which appears and operates, but there is no contact with the computer over USB.
2. Qualcomm
I can Vol-Up then plug-in which should boot into "Qualcomm mode" (a.k.a. EDL mode?), but there is also no indication of a low-level device reporting itself as "Qualcomm" or "QHUSB_BULK", or the presence of any device at all on four different laptops, both Windows (via Device Manager) and Linux (via lsusb).
2a. Each of these cable/port/laptop combinations do work for charging the OnePlus 5
2b. The same cable and ports function properly for FastBoot/data with another phone.
2c. The vol-up+plug-in method for inducing "Qualcomm mode" does appear to do something, which is that it stays on a black screen doing nothing instead of booting upon plug-in, which is what it does with no vol-up. (Before, plugging it in would send it to the "battery charge" screen, but now, having broken it further, it boots into white-LED failure).
Failure modes eliminated:
1. The USB-C/headphone port assembly was also replaced because the previous one had been unstable for a while and I wanted to ensure that a loose connection was not the cause of the FastBoot issue. The new port is now solid and reliable. I also inspected the internal ribbon port where the ports connect to the board to ensure that the tiny fragile connectors were not damaged during the swap.
2. I have also tried all methods of gaining access after disconnecting the battery for a while, and attempting to connect before pressing any keys.
Specific Technical Questions:
1. Is there another way to get the OnePlus 5 into EDL mode other than Vol-Up+cable-connect? Such as with an EDL cable or by shorting test points on the board?
2. Is there a way to boot from another device, such as via OTG, connecting to a port on the board, or using special service hardware?
3. Is it possible to communicate with a USB device even when it does not appear to low-level USB inspection tools running on the host machine, such as lsusb (Linux) or various Windows USB utilities that scan all attached USB controllers for registered devices? (Or shall I continue to interpret the phone's invisibility to any such tool as an indication that no possible driver could recognize it, and thus avoid trying the dozen or so candidates I've collected?)
4. Is it theoretically possible for (buggy, incorrect, malicious) software being written to the recovery partition to break USB data connectivity or impair FastBoot?
5. Is it possible that a hardware issue might break the USB port for data, while allowing it to function correctly for charging?
6. Are there any other suggestions for a way forward I haven't considered here?
Thanks!
Pseudorando said:
2. Is there a way to boot from another device, such as via OTG, connecting to a port on the board, or using special service hardware?
Click to expand...
Click to collapse
The only ability Android platforms have for external boot is by providing a boot image via ADB. This is done while the device is in bootloader mode, with this command:
fastboot boot <image>
This instructs the device to boot the image provided instead of what is written to the /boot partition.
If the bootloader is corrupt, the only thing that can be done is a low level reflash, as the board does not have the capability to load external software on its own - only the bootloader can.
Pseudorando said:
3. Is it possible to communicate with a USB device even when it does not appear to low-level USB inspection tools running on the host machine, such as lsusb (Linux) or various Windows USB utilities that scan all attached USB controllers for registered devices? (Or shall I continue to interpret the phone's invisibility to any such tool as an indication that no possible driver could recognize it, and thus avoid trying the dozen or so candidates I've collected?)
Click to expand...
Click to collapse
No - if Windows does not even display an unidentified USB device, it's dead as a stone.
Pseudorando said:
4. Is it theoretically possible for (buggy, incorrect, malicious) software being written to the recovery partition to break USB data connectivity or impair FastBoot?
Click to expand...
Click to collapse
I'm not familiar with OnePlus, but /recovery is a separate partition from /bootloader; as long as /bootloader is not corrupt, the device should at least start into bootloader mode, which would allow flashing partitions such as /recovery (if the bootloader is unlocked).
Fastbootd is a part of recovery mode that allows directly flashing partitions as well; normally, the recovery engine does not allow external flashing of partitions, and is meant to unpack and flash software packages.
Pseudorando said:
5. Is it possible that a hardware issue might break the USB port for data, while allowing it to function correctly for charging?
Click to expand...
Click to collapse
Yes. As noted above, if any of the "cold boot" code such as bootloader is corrupt, the device may not communicate via USB, because that's a software issue. However, the onboard power management hardware continues to function and will charge the battery when power is connected via USB.
Pseudorando said:
6. Are there any other suggestions for a way forward I haven't considered here?
Click to expand...
Click to collapse
Again...I'm not familiar with OnePlus devices, but as a generally universal rule of thumb, a device in a state such as yours is completely bricked and cannot be resurrected. If you can seek repair, do so - it most likely won't be cheap, as you'll be buying a new mainboard for the device, and you'll lose all your data anyway. Best course of action: Buy a replacement device.
V0latyle said:
The only ability Android platforms have for external boot is by providing a boot image via ADB. This is done while the device is in bootloader mode, with this command:
fastboot boot <image>
This instructs the device to boot the image provided instead of what is written to the /boot partition.
If the bootloader is corrupt, the only thing that can be done is a low level reflash, as the board does not have the capability to load external software on its own - only the bootloader can.
No - if Windows does not even display an unidentified USB device, it's dead as a stone.
I'm not familiar with OnePlus, but /recovery is a separate partition from /bootloader; as long as /bootloader is not corrupt, the device should at least start into bootloader mode, which would allow flashing partitions such as /recovery (if the bootloader is unlocked).
Fastbootd is a part of recovery mode that allows directly flashing partitions as well; normally, the recovery engine does not allow external flashing of partitions, and is meant to unpack and flash software packages.
Yes. As noted above, if any of the "cold boot" code such as bootloader is corrupt, the device may not communicate via USB, because that's a software issue. However, the onboard power management hardware continues to function and will charge the battery when power is connected via USB.
Again...I'm not familiar with OnePlus devices, but as a generally universal rule of thumb, a device in a state such as yours is completely bricked and cannot be resurrected. If you can seek repair, do so - it most likely won't be cheap, as you'll be buying a new mainboard for the device, and you'll lose all your data anyway. Best course of action: Buy a replacement device.
Click to expand...
Click to collapse
Thanks for your fast and detailed reply. I'm still holding out some hope that I just need to properly induce a mode where the phone will become responsive to flashing tools which address the Qualcomm controller directly, which appears to be a mode separate from the /bootloader (which itself does appear to at least load properly, displaying the FastBoot menu, which lets me navigate to select a boot partition, restart the bootloader, or power off).
Other phones which use this Qualcomm chip can be put into EDL mode by either on-board test points or a cable that shorts out (or otherwise modifies the signal on) specific pins. But in the case of the OnePlus 5, the mode is either software accessible (not in my case), or accessible by a held key-combo (which appears not to work for me).
I found this nicely-detailed write-up of the EDL mode and its internals:
Exploiting Qualcomm EDL Programmers (1): Gaining Access & PBL Internals
Research & Exploitation of Qualcomm EDL Firehose Programmers: From PBL (Boot ROM) Extraction, Research & Analysis to Secure Boot Bypass in Nokia 6. (Part 1)
alephsecurity.com
Pseudorando said:
Thanks for your fast and detailed reply. I'm still holding out some hope that I just need to properly induce a mode where the phone will become responsive to flashing tools which address the Qualcomm controller directly, which appears to be a mode separate from the /bootloader (which itself does appear to at least load properly, displaying the FastBoot menu, which lets me navigate to select a boot partition, restart the bootloader, or power off).
Other phones which us this Qualcomm chip can be put into EDL mode by either on-board test points or a cable that shorts out (or otherwise modifies the signal on) specific pins. But in the case of the OnePlus 5, the mode is either software accessible (not in my case), or accessible by a held key-combo (which appears not to work for me).
I found this nicely-detailed write-up of the EDL mode and its internals:
Exploiting Qualcomm EDL Programmers (1): Gaining Access & PBL Internals
Research & Exploitation of Qualcomm EDL Firehose Programmers: From PBL (Boot ROM) Extraction, Research & Analysis to Secure Boot Bypass in Nokia 6. (Part 1)
alephsecurity.com
Click to expand...
Click to collapse
I'm familiar with EDL mode, many Qualcomm devices automatically go into EDL mode when the bootloader fails to start. However if EDL mode is corrupted too...there's nothing you can do.
Maybe you can try an EDL Deep Flash Cable, which gets the device into EDL Mode with the press of a button on the cable. It also works on hard-bricked devices.
@Pseudorando
Has your issue resolved or do you still need help to get in edl mode?
Well this is a pretty thorough brick so the follow-up is not as much for help as for closure.
(tl;dr: The old data is still inaccessible, I have replaced it with a new phone, and the old one is a time-capsule project for another day.)
I got my hands on another OnePlus 5 to verify that my diagnostic procedures were being done correctly by seeing if they work on a non-bricked device.
And they do. In every mode, the new phone identified itself (even without drivers) as predicted-- FastBoot, EDL, and as a storage device when booted normally.
I also eliminated a hardware issue with the USB-C connector assembly by swapping the phones' rear panels which include the jacks and the ribbon cable to the board. The new phone worked with the old phone's jacks, and the old phone did not work with the new phone's jacks.
Upon swapping the back panels to the original phones again, I damaged the USB port's ribbon connector to the motherboard of the old phone, which seems unrecoverable without just replacing the motherboard. This led me to stripping the board to identify the flash chip where all my data is still stored.
It's a Samsung KLUCG4J1ED. (eUFS, BGA 153, UFS 2.1, 1.8/3.3v, 11.5 x 13 x 1mm, G3 2-lane)
My current plan for recovering the photos and Signal account to let my contacts know I'm still alive is to extract the flash chip and read it with a test socket.
Thanks for asking