Bricked my N5 or what? :/

soykje · 4 Aug 2017, 22:23

Hi everyone,

I finally bought an old (second hand) Nexus 5, in order to install UT on it. So two days ago I give it my first try and... unfortunately the USB cable has been accidentally unplugged while it was working...
Now, the N5 seems fine but it doesn't mount on my Ubuntu laptop or on my Windows desktop. adb devices and lsusb gives nothing and I am quite lost, as I can't figure out how to restore the phone, in order to try the UT install again...
Anyone having the same issue? If so, or if anyone has an idea that could help to restore the phone... It would be really great!

Thx in advance for your help!

doniks · 27 Feb 2017, 19:58

@soykje said in Bricked my N5 or what? :

while it was working...

"working" means installing? How did you try to install? With android on the phone and ubuntu-device-flash on Ubunut? Exact commandline?

Now, the N5 seems fine

What does "fine" mean? It's running Android? Ubuntu Touch? What happens if you enable developer mode? What does adb and lsusb give when you boot into recovery? Which recovery do you have?

soykje · 27 Feb 2017, 21:58

Hello,

Sorry if my initial message was not clear enough... So:

while it was working means during the install, as described here. The following command was executing:
sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --channel=ubuntu-touch/stable --device=hammerhead --bootstrap
Now, the N5 seems fine means that I can boot (with Android 6 on it). It seems functional even if the device can't mount... With USB debug mode activated (with MTP, or PTP), the device only stay on "slow charging" when I plug it on my machine.

I also tried lsusb and adb devices, but without success: the first one gives me only a list with no device, and the second returns me an empty result. I don't have any particular recovery, just the Android one.
I am not an expert, but I guess it is bricked, no? Is there a way I can fix this in order to give a second try to my UT install?

Thx again for your help, hoping there will be a happy ending!

doniks · 28 Feb 2017, 05:39

Can you paste the output of lsusb with: 1. nothing plugged in, 2. the device booted into Android plugged in and 3. the device booted into recovery plugged in. Also, run a tail -f /var/log/syslog in a terminal and paste what happens at the time of plugging in (2 & 3).

Can you try again with another usb cable and on another usb port of your laptop - does that change anything?

allaoua · 28 Feb 2017, 09:04

Hello
If you use ubuntu 16.04 or 16.10 it will not work, try with ubuntu 15.04 (vivid), it will recognize the nexus when you plug it in.

Best regards

soykje · 1 Mar 2017, 21:09

@doniks Here are the results from what you asked. As I was trying, I noticed that the N5 finally mounted on my laptop! But for some reason, sometimes it still loses the connection... So is it bricked, or is the USB connector which is to replace (from the N5, maybe, as I tried several cables) ?
Anyway, here are the results, with a great thank you also for your time and your kindness:

1. lsusb (without anything plugged in)

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

2. lsusb (with the N5 booted)

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 030: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

3. lsusb (with device into recovery mode)

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

4. tail -f /var/log/syslog (with device into recovery mode)

Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:20921): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:20921): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:20921): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:20921): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Feb 28 23:24:54 localhost dbus[814]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 28 23:24:54 localhost systemd[1]: Starting Hostname Service...
Feb 28 23:24:54 localhost gnome-session[2211]: (nautilus:2394): Gtk-WARNING **: Refusing to add non-unique action 'TerminalNautilus:OpenFolderLocal' to action group 'ExtensionsMenuGroup'
Feb 28 23:24:54 localhost dbus[814]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 28 23:24:54 localhost systemd[1]: Started Hostname Service.
Feb 28 23:25:01 localhost CRON[20942]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)

5. tail -f /var/log/syslog (with device into recovery mode)

Feb 28 23:19:08 localhost kernel: [35096.841602] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 28 23:19:08 localhost kernel: [35096.841607] usb 1-1: Product: Android
Feb 28 23:19:08 localhost kernel: [35096.841611] usb 1-1: Manufacturer: Google
Feb 28 23:19:08 localhost kernel: [35096.841614] usb 1-1: SerialNumber: 02e845da21307082
Feb 28 23:19:08 localhost mtp-probe: checking bus 1, device 38: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Feb 28 23:19:08 localhost mtp-probe: bus: 1, device: 38 was not an MTP device
Feb 28 23:19:30 localhost smartd[926]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 68 to 59
Feb 28 23:20:49 localhost kernel: [35198.190092] usb 1-1: USB disconnect, device number 38
Feb 28 23:20:51 localhost kernel: [35200.286754] usb 1-1: new full-speed USB device number 39 using xhci_hcd
Feb 28 23:20:51 localhost kernel: [35200.398788] usb 1-1: device descriptor read/64, error -71

soykje · 28 Feb 2017, 22:34

@allaoua What wouldn't work? As I said just before, for some reason the problem seems in my case related to the USB connection (for some hardware or software reason)... But when I got it, the N5 is well recognized.

doniks · 1 Mar 2017, 21:09

@soykje said in Bricked my N5 or what? :

@doniks Here are the results from what you asked.

So, from the posted snippets, it looks like ( 3&4 ) nothing is recognized in recovery. While (2&4) it works (somewhat ... N4 instead of N5 ...) in Android. Now if that were consistently the case, then one could assume that "only" something is wrong on the software side of the recovery. However, when you say

As I was trying, I noticed that the N5 finally mounted on my laptop! But for some reason, sometimes it still loses the connection...

and furthermore

I tried several cables) ?

it sounds a bit more like a hardware problem. I understand you got the device recently and it's not like you have used it stably for weeks and months before the current problems occurred, correct? How does the usb port on the device look like and "feel" does the plug sit firmly or does seem worn?

Anyway, here are the results, with a great thank you also for your time and your kindness:

You're welcome. I just fishing in the dark here. Maybe

sometimes it still loses the connection...

can still happen due to some software problem on the Android side.

What you could also try is post syslog and lsusb and adb device output also for the fastboot mode. Totally forgot about that. What does it look like there?

And if you have an ok connection there, you could try flashing some other/newer recovery and then see whether that changes anything. I'm really not the expert on these, I recall names like CWM (Clockwork mod) and TWRP. If you check N5 forums on xda-developers.com you should be able to spot which are the most recommended recoveries for N5.

doniks · 3 Jan 2017, 21:12

@doniks

So, from the posted snippets, it looks like ( 3&4 ) nothing is recognized in recovery. While (2&4) it works

Hold on. I got the numbers mixed up. No, wait, I guess you copy/pasted something wrong here :

4. tail -f /var/log/syslog (with device into recovery mode)

5. tail -f /var/log/syslog (with device into recovery mode)

You don't mean 4 AND 5 are from recovery mode right? I assume 5 is in Android?

soykje · 2 Mar 2017, 18:42

@doniks My mistake, I did a bad copy/paste in my results... So here are the new ones (with he lsusb and adb devices on fastboot mode):

4. tail -f /var/log/syslog (with the N5 booted)

Mar  2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Mar  2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Mar  2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Mar  2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Mar  2 19:28:01 localhost gnome-session[2002]: (nautilus:7007): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar  2 19:28:01 localhost dbus[811]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar  2 19:28:01 localhost systemd[1]: Starting Hostname Service...
Mar  2 19:28:01 localhost org.freedesktop.FileManager1[1864]: (nautilus:2391): Gtk-WARNING **: Refusing to add non-unique action 'TerminalNautilus:OpenFolderLocal' to action group 'ExtensionsMenuGroup'
Mar  2 19:28:01 localhost dbus[811]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar  2 19:28:01 localhost systemd[1]: Started Hostname Service.

5. tail -f /var/log/syslog (with device into recovery mode)

Mar  2 19:19:06 localhost systemd[1]: Started Hostname Service.
Mar  2 19:19:30 localhost org.freedesktop.FileManager1[1864]: App load time: 428ms
Mar  2 19:20:03 localhost dbus[811]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar  2 19:20:03 localhost systemd[1]: Starting Hostname Service...
Mar  2 19:20:03 localhost dbus[811]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar  2 19:20:03 localhost systemd[1]: Started Hostname Service.
Mar  2 19:24:54 localhost systemd[1]: Starting Cleanup of Temporary Directories...
Mar  2 19:24:54 localhost systemd-tmpfiles[6612]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Mar  2 19:24:54 localhost systemd[1]: Started Cleanup of Temporary Directories.
Mar  2 19:25:01 localhost CRON[6625]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mar  2 19:26:39 localhost org.freedesktop.Notifications[1864]: ** (notify-osd:2326): WARNING **: stack_close_notification_handler(): notification id == 0, likely wrong

6. lsusb (with device on fastboot mode)

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 8087:0a2a Intel Corp.
Bus 001 Device 014: ID 18d1:4ee0 Google Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

7. adb devices (with device on fastboot mode)

List of devices attached

About the possible hardware issue... I can't say: I bought the N5 in second hand, and if it seemed ok, I noticed that my cables didn't fit perfectly with the USB port
Anyway, if those new results tell you something you're welcome. Meanwhile I'll be looking for TWRP (the one I know best) for N5, if it can help...
The problem for me actually is also to be sure about the origin of my problem : hardware/software original state of this second hand device, caused by the "first try accident", ... And at the end, installing this damn' UT on this N5 !

soykje · 5 Mar 2017, 21:52

Hi everyone,

So, here's the thing: I finally succeed!

I installed TWRP on my Nexus 5, and then unlocked it before following the Ubuntu official recipe to reinstall Android on a phone. Don't think the TWRP step has been really useful, but anyway... After reinstalling Android, I tried to install Ubuntu Touch, the same way I used on my first try. And it worked!!!
I used the channel devel_rc, as I saw it was highly suggested on this forum... I am also not sure but I guess the USB issue may have been related to hardware and software, as the first try failed interrupting the install with hard unplug (thx to my cat...). I may have resolved this part reinstalling Android, luckily, but I guess I'll have to replace the USB port from the N5, sooner or later.
Anyway, I am sooo happy to finally discover UT on my Nexus 5, and for now, it seems just great, even if I noticed two issues on wifi and battery display. Next step will be a small report after a week, and working with launchpad to help reporting bugs.

Many thanks to all of you who helped me, and long live to UB Ports !!

doniks · 3 May 2017, 22:41

@soykje said in Bricked my N5 or what? :

4. tail -f /var/log/syslog (with the N5 booted)
5. tail -f /var/log/syslog (with device into recovery mode)

No sign of anything here in either mode ... so if those snippets are from the time of plugging the device in, then that's indeed more signs for usb being unreliable

6. lsusb (with device on fastboot mode)
Bus 001 Device 014: ID 18d1:4ee0 Google Inc.

@soykje said in Bricked my N5 or what? :

2. lsusb (with the N5 booted)
Bus 001 Device 030: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)

ok, fwiw, we have the two different device id's 4ee0 and 4ee2 in fastboot and adb mode respectively. That shows that under the right kind of circumstances and with the right kind of luck some communication IS possible ...

7. adb devices (with device on fastboot mode)

Nothing here. Of course! It was a stupid question of me! When booted into fastboot mode the device is not expected to show up with adb, but instead with :
fastboot devices

and if it seemed ok, I noticed that my cables didn't fit perfectly with the USB port

Ok. Can be taken as another indication ...

@soykje said in Bricked my N5 or what? :

So, here's the thing: I finally succeed!

Ha! Nice! Enjoy

and then unlocked it

Ah, so it wasn't unlocked yet. Well, I guess neither installing UT, nor Android could have worked without it being unlocked. Actually, I'm surprised that you say you WERE able to install a new recovery BEFORE unlocking it.

However, I don't think the unlocking can explain the observed USB instability

So, I'd say for any kind of flashing/accessing experiment

verify with syslog and lsusb whether it shows up ok
verify with either adb or fastboot whether is shows up ok
- adb when booted into Android, recovery, UT
- fastboot when booted into fastboot mode
make sure not to move the phone or cable while accessing
(make sure to have the cat in another room )

soykje · 6 Mar 2017, 06:42

Hi,

Yes, and also, having some candles to light, before any USB plug...
Again, I really want to thank you for your time. I finally can enjoy the UT experience, and maybe try to participate to it