Nexus 5 vs Nexus 5x
-
@stanwood Should I be in Windows to do it?
-
@jjconstr Once again, running Nexus toolkit from Windows 10 is very easy. Nothing else to do... I'm afraid you'll put a mess in your W7 PC...
-
@jjconstr It seems to from the description. I have never used this tool. But getting it directly from the manufacturer (or XDA) and installing it manually once in normal boot, once in recovery (maybe using one of your known working Nexus 5s) will solve the problem.
Windows will put the driver where it needs to go. You only need to make sure you have fastboot and adb installed in the same folder with the Nexus tool
-
@stanwood No, not working yet. Sorry to be unclear. But the problem may be narrowed down. Maybe this folder stuff is hanging up the install. I'll also check for Nexus 5 windows driver is installed on the computer.
-
Well, I can't help you further through Windows 7 (no skill to do it).
Otherwise, you can try to do so in Ubuntu:
Install ADB + Fastboot:
sudo apt install adb
sudo apt install fastbootThan download factory image here and follow instructions:
-
@rocket2nfinity If I do upgrade to win 10, can I restore Win 7 later if I want? I have been making Windows Image Backups.
-
@stanwood I'll certainly try that before upgrading to Win 10. I've heard some say they regret switching to it.
-
@jjconstr I believe not. Try to make an iso back-up. But no guarantee...
-
@jjconstr Nobody in your social circle (friends, family, colleague) has W10 and would let you do this? It's fast to run, and you only need it for a once...
-
@stanwood Well, I'll try to get the Nexus 5 driver Ubuntu using your commands. Will NRT be able to access it? From Windows?
-
@jjconstr You need to make sure your computer can handle Win 10 first, or you will put yourself in a special level of hell. Upgrading can take a very long time, downgrading to Win7 may also become difficult afterwards. So make sure you are confident with how to downgrade.
If it were me, I'd manually install the drivers twice -once in normal boot, then once in recovery using one of my working N5s and try the tool again before going through all that effort to upgrade Windows. But, if you're confident your machine can handle it, then upgrading to Win10 seems to be the simplest solution to get the tool working
-
@stanwood I do have someone I know with Win 10. He regrets it! I'm just a little cynical at the moment regarding how easy it is supposed to be. I'm not very proficient even with windows as you see.
-
@jjconstr No, you have to choose one route or the other - either use Windows, or Ubuntu and load the tool with Wine or in a virtual machine that is using Windows. This will take some research for you to use the Ubuntu options if you have never used Wine, or a virtual machine like VirtualBox.
In short, you've taken the red pill Neo....
-
@rocket2nfinity Sounds like words from the wise.
@rocket2nfinity said in Nexus 5 vs Nexus 5x:
@jjconstr You need to make sure your computer can handle Win 10 first, or you will put yourself in a special level of hell. Upgrading can take a very long time, downgrading to Win7 may also become difficult afterwards. So make sure you are confident with how to downgrade.
If it were me, I'd manually install the drivers twice -once in normal boot, then once in recovery using one of my working N5s and try the tool again before going through all that effort to upgrade Windows. But, if you're confident your machine can handle it, then upgrading to Win10 seems to be the simplest solution to get the tool working
Install the drivers into windows? The tools install drivers into the phone. Will they install them the other direction?
-
@jjconstr Windows is not like Linux. The drivers are (normally) already built in with Linux. With Windows (and very new hardware in Linux) you must install drivers for Windows to be able to know what to do with the hardware you just plugged in. The drivers are installed in Windows, not the phone. Without the drivers, it will tell you it detected an unknown device. Windows reads the recovery mode of your phone as another device even though it is the same hardware. So the driver must be installed again. That's just the way Windows works.
You also need fastboot and adb installed in Windows before running the tool, and the tool to be in the same folder you put ADB and fastboot
What the tool does, is to execute the fastboot devices command, detects the phone, and then automatically does what the Google factory images page tells you to do manually - install bootloader, recovery, radio, data, vendor, system, usually with just the flash-all script included in the file. You can also do this manually one at a time but this is going to get even more confusing if I go into that.
So where's that leave you? Easiest thing would be to borrow a friend's computer that has Win10 on it and try it on that. Harder but doable would be to forget the tool, and manually install the Nexus 5 drivers (remember to do it twice) and follow the instructions we provided above to flash a stock image from Google's factory images page. I would go with an OTA image first since I can guarantee all the needed files will be there. I discovered they sometimes aren't with the straight factory images.
Another option is to upgrade to Win 10 but a lot of older hardware doesn't play nice with Win10, so be sure yours does before trying. Or else you will find yourself in that special level of hell.
Last option, do some research, learn how to install VirtualBox or Wine, load the tool and/or Windows in that. Or go further down the rabbit hole and learn to do it manually -It's educational! Click the check box on your employers yearly continuing Ed requirements.
-
@jjconstr I want to stress, your primary goal here is to get any working image of Android to run on the phone at the moment. Using the tool is not necessary, just helpful. Flashing the last OTA image from Google will get you on the right path, or flashing the factory non-OTA will ensure everything is where it needs to be. The OTA assumes your partitions are correct. The factory build does not. Then you can progress from there.
But first you must ensure you have the Nexus 5 drivers installed on your computer in both normal boot and recovery mode so that it can talk to your phone via adb and fastboot.
Welcome to the Matrix....
-
@rocket2nfinity said in Nexus 5 vs Nexus 5x:
Without the drivers, it will tell you it detected an unknown device. Windows reads the recovery mode of your phone as another device even though it is the same hardware. So the driver must be installed again. That's just the way Windows works.
Yes, exactly.
I had to "install" ADB drivers 3 times for my MX4 to work with unports installer, in normal dev enabled boot, in fastboot, and in recovery : https://forums.ubports.com/topic/4026/solved-problem-upgrading-mx4-from-ota15-to-ubport/13 -
@rocket2nfinity Nice summary.
-
@rocket2nfinity What is OTA? Maybe I'll try getting the drivers loaded twice before I use a different method.
-
@jjconstr Posted somewhere above are the links for both OTA and initial factory installs from Google. What the phone came with out of the factory is, naturally, a factory install. With such an install, the manufacturer sets the drive up on the device, including partitions - what sections (vendor, recovery, system, etc) gets how much space, etc.
When you turn on the phone and get an update notice and apply it, that installs an over the air (OTA) update from the manufacturer or distilled by your carrier from the manufacturer's update. That update usually makes certain assumptions about your partitions and doesn't mess with them as deeply as a factory install might. Those assumptions primarily being, that if you are installing the OTA update, then logically you must have a working device that is set up as the manufacturer specified.
However, people don't always do what the manufacturer expects, such as - installing after market ROMs, changing the sizes of the partitions to increase swap space, etc. That will cause an OTA update to fail. If the modder screws it up, the device will bootloop. If a power, or volume switch sticks, it can also cause a bootloop and software corruption. That is likely the problem you are experiencing.
What the tool, or installing a factory build, does is reset everything back to the way it's supposed to be. An OTA can do this as well, if your partitions haven't been messed with. Why I suggested using an OTA build from Google, is that I discovered sometimes Google leaves a file out or compresses it in the factory build which you have to uncompress. Since you are new at this, I'm simply trying to make it easier and less confusing for you.
