Database Users

A load of problems...

So recently flashed CM 10.1 FUSION. Nexus battery drains, I end up turning it back on while on the charger. Then, it shuts down on me.. so I let it charge overnight. Turned it back, and I get stuck at a boot screen (FUSION). I attempt to turn my device off, and it just restarts. I have to turn it off from the bootloader (P+Up+Down).. I tried using the toolkit, but I freeze in the bootloader when I plug my device in.
Help.
Running 4.2.1
Yes I'm aware of the common problems, none of the solutions seem to be working.

Rovon said:
Yes I'm aware of the common problems, none of the solutions seem to be working.
Click to expand...
Click to collapse
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers

bftb0 said:
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
Click to expand...
Click to collapse
I tried watching a majority of the "unbrick nexus 7" vids on youtube. They didn't get me too far
Holding power for a long time
Restarting bootloader
Root toolkit
If I don't connect it to a device, I can move through the bootloader but can't access recovery

Rovon said:
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Click to expand...
Click to collapse
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?

bftb0 said:
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
Click to expand...
Click to collapse
Sorry, I meant its frozen on the fastboot screen...
I can scroll through the fastboot, but that's it. None of the commands work, unless I hit power off. The toolkit tells me "fastboot device not found", when I try the Flash Stock + Unroot button. There is no device ID I can see on the toolkit. Also, drivers fail to install when I plug it in to my computer.

Rovon said:
None of the commands work, unless I hit power off.
Click to expand...
Click to collapse
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?

bftb0 said:
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
Click to expand...
Click to collapse
I should've been more specific. When I say none of the commands work, I mean they don't do what they're supposed to. So if I hit "recovery mode" it will not go into recovery mode, it just stays stuck at the Google logo when it restarts.
As for device manager, when plugged in to the computer with Fastboot, I do get "android" under other devices. However, when I'm booting the device up regularly, the computer attempts to install drivers and fails. I do get "MTP USB Device" under portable devices. I have an unknown device under portable as well.
All 3 seem to have error symbols next to them.

Rovon said:
All 3 seem to have error symbols next to them.
Click to expand...
Click to collapse
Well, if you can't communicate with the device successfully, there's no hope of doing something correctly from the PC. So, try a few simple things on that angle of the problem first. The problem you are seeing could come from any number of places:
- damaged USB (or other) hardware on tablet
- bad / cheap USB cable
- damaged USB port on PC
- driver install issues
The symptoms you describe for fastboot sound a bit like the custom recovery got damaged or erased, although more severe (and not fixable) problems are also a possibility.
Since you previously installed a ROM, I would take it to mean that at one time you had at least one driver working (fastboot at a minimum), and possibly also ADB mode (in the OS and/or in the recovery). That's why I put "driver install issues" last in the short list above. If you never touched any of the drivers after you did your initial ROM installs, I would not expect driver issues ... but I don't know what you might have tried subsequently with the toolkit (which does fool around with drivers).
Are you using the OEM cable? Some aftermarket/charger cables have a short mini-USB connector, and one dollar cables off of eBay can be poorly constructed (bad shielding or impedance control, so they cause data errors at high speeds).
If you have an 2nd cable, I would try to see if you experience a different set of symptoms with that; same goes for trying a different USB port on your PC.
If you see errors in the Device Manager associated with fastboot I certainly would not be attempting any operation from the PC until you get that resolved. Note there is a huge difference between "unknown device" and a device showing errors - the latter suggests that the OS is aware of a driver which is supposed to be loaded when the tablet shows up on the USB bus, but then some malfunction occurs. That malfunction could either be hardware or an inappropriate driver.
Drivers
http://www.asus.com/Tablet_Mobile/Nexus_7#support_Download
http://forum.xda-developers.com/showthread.php?t=1426502
Note that you should be able to use the Asus driver for every mode of your Nexus 7 (except MTP and PTP, which are handled by Windows generic class drivers), including your custom recovery by doing the following:
A) Download the Asus Driver and unzip it someplace.
B) make a backup copy of the "android_winusb.inf" file (for instance "android_winusb.inf.backup")
C) Open up the "android_winusb.inf" file with the Notepad program (Note: not Wordpad!)
D) Find the ";Google Nexus 7" stanza in the [Google.NTx86] section and add this line:
%CustRecoveryADBAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
E) Add the same line (step D above) in the [Google.NTamd64] section
F) At the very bottom of the file in the [Strings] section, add the line
CustRecoveryADBAdbInterface = "Nexus 7 Custom Recovery ADB Interface"
G) Save the file and then proceed to do a manual de-installation of the drivers for fastboot and ADB.
H) Disconnect from the internet and then re-install the Asus driver for fastboot and ADB using the "Choose Location" method.
Don't know if that will work, but it's something to try; the problem you are having might lie outside the scope of what all of the above deals with
good luck

Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!

Rovon said:
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Click to expand...
Click to collapse
Please describe what you found out and what DID work for you. Even if it was just a simple mis-understanding. It might help others in the future.
Probably you should also alter the title of your thread to be something much more descriptive - and add the keyword "[SOLVED]" to the title as well.

[Q] Nexus 7 3G in trouble

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.

Google Nexus 4 Does not show up as USB device but charging OK.

Got myself a google LG Nexus 4.
Connecting via USB - 2 different cables, 2 computers, 3 different operating systems (archlinux, debian, windows vista ) - i get nothing (*).
the phone does not acknowledge that it is connected to a computer, but it charges ok.
the computers do not recognize the phone in any way, not even in dmesg (or device manager in windows).
i have tried changing options inside the phone (debugging on/off, mtp/ptp...), even a full factory reset, and going into recovery and wiping cache/dalvik cache. - nothing.
wiggling the cable and such does not help.
i even replaced the usb connector, no change whatsoever.
so something tells me that it is not a hardware problem.
the phone has been upgraded to android 5.0 (before i became the owner).
my endless searches show that nobody knows what's going on, it might be hardware fatigue, it might be related to the upgrade to 5.x, it might be a firmware problem...
any helpful pointers, including downgrading & softbricking the system would be helpful (i just want to install ubuntu phone onto it).
(*) my other android phone connects ok with both cables, to all machines and operating systems.

With the phone in fastboot or recovery mode, is it recognized?
The fact that the usb port has been changed could indicate a problem with the motherboard connector.

Go into device manager with your phone connected and uninstall the drivers. Then install "universal adb driver"(google it it's from Koush) with your phone NOT connected.

audit13 said:
With the phone in fastboot or recovery mode, is it recognized?
Click to expand...
Click to collapse
i tried adb, the device list is empty.
booting into recovery, replugging the usb cable, i still get nothing. it's like there's nothing to communicate to, both from the computer's and the phone's point of view.
i will have to play with fastboot (i gather it works only while the phone is booted into recovery?), but i doubt it'll change anything.
The fact that the usb port has been changed could indicate a problem with the motherboard connector.
Click to expand...
Click to collapse
do you mean the connector from the usb port, that flat cable snap-on thingy (far right on this image)?
is it realistic to try to fix that?
PS:
meanwhile the battery drained completely and i had a "Red light of death" which i managed to fix like this. i think it will take a while to recharge properly.

Adb commands will work with the phone booted into the rom. Use fastboot commands with the phone in fastboot mode.
Yes, the flat part at the it her end of the USB cable is what connects to the motherboard and is not worth fixing if that is causing the charging problem.
With a red LED, just connect it to a 2.0 amp charger using the original charging cable and let it charge for a few hours.

thanks again.
next thing i realized that the volume rocker isn't working (anymore?).
so i can't boot into recovery.
i don't know how, but once i managed to get into recovery, but couldn't make any choices in there.
anyhow, that sort of cinches it: i'm done with this phone. project failed.
(nevermind, it was a cheap ebay shot)
ubuntu phone will have to wait.

Nexus 6p unresponsive screen with OS lock

Hello Everyone,
I have an issue with my nexus 6p screen all of a sudden being unresponsive to touch. The big error on my part was not setting up my videos and images to automatically backup. So now what i'm trying to do is unlock the phone using ADB and a usb cable but haven't had any luck. I've gotten as far as listing my devices, which show up an unauthorized and seem I can only authorize it from my phone. Q1. is this true? Could there be any other way to authorize my phone, or am I out of luck and my data is kaput? I've also tried an OTG cable but it doesn't load since i'm guessing the OS has to fully load for the cable work.
Do I have any choice on saving my data with a USB cable and command line or can someone suggest a tool that would help me out of this situation?

Put it into fastboot/download mode and flash the latest TWRP recovery.
Use TWRP's file manager or ADB Pull commands to pull your data off. Use ADB push to push a new ROM image and flash over everything except userdata (back it up just in case).

Deep in the weeds with a bricked OnePlus 5 - Specific technical questions for you experts!

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