Nexus 5 vs Nexus 5x
-
Depends what you want out of the phone and if you're willing to wait, Ubuntu Touch on the Nexus 5x is very early days whereas on the Nexus 5 it's quite mature, as well as that Ubuntu Touch on the Nexus 5 is plenty fast enough for everything you could want to do and the camera is actually alright, plus the Nexus 5 can be had for bargin prices
-
@rocket2nfinity said in Nexus 5 vs Nexus 5x:
@jjconstr Which unlock service did you use? Some of them take some time to send you the unlock code. All the ones in that article were vetted at the time.
code-unlock-store.com is the unlock store and they emailed me saying:
Dear Jerry Johnson,Sorry I have been unable to generate the correct unlock code for your mobile. There are so many mobile out there sometimes the firmware on certain versions mean I can't generate the code.
I have sent your details over the accounts team who will send you a refund. Although normally quicker please allow up to 5 days for the refund to get back into your account.
Once again I apologise for not being able to get the correct code for your mobile. Your only option may be your network operator or a local shop who can unlock via a cable.
Thanks
Tom
-
@ImmyChan Now have 3 Nexus 5's and am very pleased with UT. I agree with your accessment. Thanks for your input.
-
@jjconstr So you successfully replaced the power switch and all is good?
-
@rocket2nfinity Good timing. Was just wondering where that switch is. I ordered it the day you gave me the link. Usually by the time I'm wondering, the order arrives shortly.
cheers -
@rocket2nfinity said in Nexus 5 vs Nexus 5x:
@jjconstr So you successfully replaced the power switch and all is good?
No, not so good. I replaced the switch and the Nexus 5 still had a boot loop, but was able to access UBports installer, unlock OEM, but after that, the boot loader would not stay on. By that I mean a couple times I saw the screen of arrows coming down. Other times, the installer would say 'waiting for device'. After a while. it would say 'yikes', error. Selecting 'recovery' did not fix the interrupted install as it did in my first two Nexus 5's. The phone displayed a new, smaller icon and the words, 'No Command'.
When 'waiting for device' timed out, the phone no longer was OEM unlocked. Repeating the installation process several times resulted in an error message;
Error:fastboot:flash:error:flashing failed:error:{"error":{"killed" :false,"code":1,"signal":null,:"cmd":/snap/ubports-installer/275/app/resources/app.aser.unpacked/platform-tools/linux/fastboot flash recovery "/home/jjconstr/snap/ubports-installer/275/.cache/ubports/hammerhead/firmware/recovery-hammerhead.img""},"stdout":"",stderr":"Sending 'recovery' (11828 KB) OKAY [ 0.740s]\nWriting 'recovery' FAILED (remote: 'flash write failure')\nfastboot: error: Command failed"}
Thanks,
jjconstr -
@jjconstr Do you know how to use TWRP? The bootloader is likely corrupted - it happens often after the power switch problem.
You need to reflash the boot loader and maybe the partitions. Try flashing the OTA factory images from Google or Lineage 14. If Android successfully reinstalls and is stable, unlock the boot loader and run the script again.
https://developers.google.com/android/ota
You need the 5.1 image Lineage OS 14http://docs.halium.org/en/latest/supplementary/devices/hammerhead.html
-
@rocket2nfinity No, I've never used it. I'll give it a try. If there are instructions, maybe it will work for me. Thanks for the help. Where do I get Twrp? Snapstore?
-
https://twrp.me/lg/lgnexus5.html
Basically, you need to install a stock Android image so that all your software is in the right place. You can flash a factory image just using fastboot by following Google's instructions, but if you run into trouble, TWRP gives you other options to try. It's also the easiest way to install an after market ROM, or flash Google play store.
Be sure to go to the XDA-Developers support page, TWRPs home page or Lineage device page to make sure you understand what you are supposed to be doing before you do it.
-
@jjconstr It is concerning that fastboot did not retain a connection. But as long as you got one, you're doing better than you were before.
Checking via terminal using the commands:
adb devices
fastboot devicesApplies here. But by your description above, fastboot appears to have been connecting.
-
@jjconstr I had a similar issue when I received my brand new N5 in last february. I was unable to install corretly UT (lot of bugs, even after multiple reinstallations). I had to flash a new factory image.
To do so, the easiest way (from my side), if you have a Microsoft Windows PC, is to use "Nexus tookit" software:Just install the programm and follow the instructions, everything is done through the software. It's exceptionaly easy.
Once done, install UT again using UT installer
My experience was conclusive. Never encoutered any problem since... -
Wow, that's quite a tool. He's using Ubuntu, so in his case, he should try using it through WINE or Windows in a Virtual Machine. I use Virtual box for those occasions but I haven't looked to see what's new and easy. There might be something better these days.
-
@rocket2nfinity Or maybe by a friend or relative who has a Windows PC.
Nexus toolkit is very easy to use, even for newbies like me. It restores Android with latest rom, factory image and firmwares, the whole process in a few clicks.Than activate developer mode, enable USB debugging, reboot in bootloader, connect to Ubuntu PC (warning: fastboot and ADB should beforehand been installed), run UT installer and... enjoy
That’s what I did to make my N5 working smoothly on UT.
-
@stanwood I gave it a try on Windows 7, found since the phone wouldn't boot, and I couldn't enable USB Debugging or Developer Options in phone, the option I needed to use is Flash Stock + Unroot with Soft-Bricked Bootloop option. This option does not need USB Debugging enabled.
Working from Windows 7, Errors received were;
Setup ADB driver- Warning 1909 Could not create Shortcut Start ADB.lnk. Verify the destination folder exists and you can access it. Install did continue successfully. I changed cables and Google Nexus Bootloader Interface is Ready to Use.
Retrying, Nexus Factory Image Downloader
Requires unlocked device..done
Waiting for device to finish booting.
Install of device driver software was unsuccessful.Turned on Windows Updates. Does that activate driver updates for other programs?
Fastboot not found.
MTB USB Device - Failed- Consult manufacturer.
Can't access update server.
Flashing successful - unlocking bootloader.
Fastboot connected -rebooting device - wait.
Device driver not successfully installed - repeats.That's where I'm at. Thanks for your time.
-
@jjconstr Indeed, developer mode must be enabled from Android settings (or UT). Go through "Settings", "About" and press 7x on "Built number" to activate developer mode. Enter in "developer mode" and activate "USB debugging". Than reboot your device in bootloader and flash it using Nexus toolkit.
Of course, if device can't be turned on for any technical reasons, it won't be possible to activate developer mode easily.Did you first install ADB drivers in Windows? :
As I said, I'm newbie and don't have any technical nor computing knowledge. FYI I'm using Windows 10 on my second computer (Ubunbtu 19.10 on my prime) Windows 7 is not supported anymore since January 14, 2020. I would strongly recommand to proceed with W10...
Btw if I well remember @Flohack saids recently it's virtually impossible to brick a N5, so there should be a way to reinstall the whole system. I'm unfortunatly unqualified to help you further... Sorry
-
@jjconstr Did you install adb and fastboot on the windows computer? The errors indicate it isn't installed, or was not opened in the right folder. Unlike Ubuntu, in Windows you need to be in the folder where you put ADB and Fastboot tools to use them.
https://wiki.lineageos.org/adb_fastboot_guide.html#on-windows
-
@rocket2nfinity Correct, ADB and Fastboot must be installed on Windows for reflashing your device. But, as far as I remember, those have been automatically installed when I ran Nexus Toolkit, I had no process to run separately.
I would again recommand you to try again with Windows 10 if you can somehow.
Nexus Toolkit informs as follow:VERSION 2.1.9 – This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, utility set for merging custom build.prop tweaks, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings official support for the new ZIP style factory packages.
If you have no other option, try install separately ADB and Fastboot on Windows 7 (*if allowed...)
-
@stanwood Windows 10 does sound like the solution. Somewhere it said easy with Win 10, not so with Win 7. Not automated.
I downloaded ADB and Fastboot tools to default, Download folder. I don't know where in Windows to put it.
-
@stanwood Too many features to list! But you seem to have done it! Fabulous if I can get it working. I didn't find a separate download file for Fastboot. I downloaded a combination file. NRT ends up saying Fastboot not found.
-
I can not tell you... Maybe in C:\program files (copy in C:\user)
