Installing UT on N5 stuck in boot loop
-
@Lakotaubp That didn't fix it. Made the google pause for a few seconds longer. Maybe there is a Youtube vidio on tearing down a N5. i could replace the
battery at the same time. Other than the power switch, would the problem be software related? -
@jjconstr Could be software - plug it in and type in terminal:
sudo adb devices
Twice, then:
sudo fastboot devices
Does it show any?
If not, it's likely the power switch. Yes, there are many teardown and switch replacement videos online. Search Nexus 5 battery replacement, Nexus 5 power switch replacement
-
@rocket2nfinity Terminal says command not found, on both those commands.
-
-
@rocket2nfinity Will try those now.
-
@jjconstr 99% power button by the way. It's very common
-
@rocket2nfinity It loaded some packages, starting with "Android" And asks if I want to load 2500kb more. Do it?
-
@jjconstr yes
-
@Lakotaubp Are new ones available?
-
-
@rocket2nfinity that link was quick and long too! Terminal unpacked, set up android, processed triggers. Terminal finished. I ran just the first command. N5 still plugged in and flashing google.
-
By the way, the device must be connected to the computer before typing
sudo adb devices
Just in case it wasn't clear...
-
@jjconstr and did it show a device with either adb (do the adb devices command twice) and fastboot devices?
-
@rocket2nfinity said in Installing UT on N5 stuck in boot loop:
sudo apt install fastboot
Yes, the N5 was connected. and do I run the second command now? sudo apt install fastboot
-
@jjconstr yes install fastboot then do fastboot devices
-
@jjconstr did it show a device with either fastboot or adb?
-
@rocket2nfinity Here are two lines showing the adb sequence. I didn't go far to find them. I only ran the first command once and not the second. this refers to the second pair of commands. The first pair I rand the first command twice and the second once.
-
@jjconstr copy and past failed.
-
@rocket2nfinity adb was repeated in the output
-
@jjconstr if no devices showed up after inputting adb devices it doesn't see it. If a device showed up, type:
adb reboot recovery
