Installing on Nexus 5
Thanks for the info. It gave me the confidence to start.
I eventually found the udev rules after I scrolled way down, past all of the cruft on the page that you linked. I included those rules in the properly named/permissioned file.
However, I think that the main problem in getting the ubports-installer to see the device is that Android has a USB connect option that has to be enabled (in addition to enabling "developer mode"), plus there is an additional USB authorization dialogue that has to be checked/approved. As soon as I enabled all of the USB obstacles in Android, ubports-installer found my device.
These specific Android USB-enabling steps should be included in all Ubports installation instructions.
(Sorry for the lengthy saga that follows, but there might be some info in it that is helpful to someone attempting a first time install.)
I couldn't install nor run TWRP to backup the Android on my phone. I downloaded TWRP through my phone over wifi, but it is apparently impossible to install TWRP when downloading it with the Chrome web browser. The kind folks at Google want to protect us from alternative software.
Also, there is no file manager on stock Android that would allow installation of the TWRP apk file. It was out of the question to get the Android apps that would enable me to install TWRP, as my whole reason for using UB Touch is to protect my privacy (which would be difficult to do using the Android app store).
I also tried to use MDT with a Lubuntu liveUSB to backup the Android installation, but I couldn't get that to work.
I finally decided to just install without a backup, as there seems to be ways of restoring stock Android without a backup.
So, I tried MDT again (with the Lubuntu liveUSB) for the Ubports installation -- it didn't work.
Then, I went back to ubports-installer and it started to work, with the "Ubports Recovery" screen instantly appearing on my phone. It was the first time I had encountered that screen, and, without any installation instructions warning of its appearance, I thought the screen indicated that my last MDT attempt had worked. I panicked that ubports-installer was borking the non-extistent Ubports install, so I immediately (and mistakenly) hit the reboot option. Afterwards, nothing would boot (Android was already wiped/borked).
All Ubports installation instructions should have a warning to expect the "Ubports Recovery" screen and to do nothing when it appears. It is confusing and counter-intuitive for a "recovery" screen to appear while an installation is successfully in progress, so some people assume that something went wrong with the installation, and they mistakenly click on a recovery screen option.
At any rate, the phone seemed bricked. The only thing that would appear on the phone's screen was a Google logo with an icon of a small, open lock.
I tried several times get back into fastboot by pressing the prescribed combination of the phone's buttons, and I tried every other combination of button presses -- all to no avail.
I remembered that fastboot was installed on my computer, so I connected the Nexus 5 and ran "fastboot oem unlock" in a terminal (can't remember if I was root) and the fastboot screen appeared on the phone!
I then ran ubports-installer which didn't see the phone, but it still installed Ubports after I selected my device from its list. This time, when the "recovery" screen appeared I did nothing, and the OS installed on its own!
So, I have Ubuntu Touch on my phone!
Now, my question is do I have OTA2 installed? If not, how can I install it?
Flohack last edited by
congratulations for this adventure, and yes, the guides will need more infos. Why there is no description for unlocking the phone and enabling adb: We are thinking that people who are flashing their phones are familiar with this procedure from Android. But it seems not the case, you are not the first one having those difficulties. I will put a disclaimer there.
For the OTA: Yes you are on OTA-2, as the installer always installs the latest stable or rc or devel version from our server Hold tight, tomorrow we launch OTA-3, but there is no popup telling you this, you need to search for updates manually
@flohack said in Installing on Nexus 5:
Hold tight, tomorrow we launch OTA-3, but there is no popup telling you this, you need to search for updates manually
How does one search/find updates?
Do the updates automatically install themselves on the phone, or do we need to use ubports-installer, MDT or other external methods?
libremax last edited by
You only have to check "Updates available" in "System Settings" on your Nexus 5
Flohack last edited by
Yes you need to visit system settings and then the update icon from time to time. We will enable push notifications eventually again when a new OTA is out. This worked at Canonical times but then ceased, no one knows why...
Okay. I will check for an update after I get my phone up and running with a carrier.
revoltevidente last edited by
Hi! I only could install UT by CPT. The snap package hasn't been found on Ubuntu... And it doesn't work by magic-tools .. My installation (or re-installation) is 2 days old
I would like to also ask for a little help.
I am completely new to android flashing. I just got second-hand nexus 5 32GB and wanted to try ubuntu touch. I was able to make first steps and ubports-installer proceeded at first - then it was wainting for device to enter recovery mode. It actually always stops there. I can get to ubports recovery but there are too many options.
Reboot system now
Reboot to bootloader
View recovery logs
In ubuntu actions are following steps:
-replace ubuntu android system
-install ubuntu zip
-install ubuntu preinstalled
-wipe data/factory reset
in android actions are following options:
-wipe data/factory reset
-wipe cache partition
I have 5 recovery logs
Does the logs signal any possible problem?
I have a few question about my situation
- Am I on a right track? can I safely proceed with installation and how?
- Can I safely roll back to android at this state? How could it be done?
- Is it now late to back up data for possible future recovery? I was a little too quick - I thought that gui installation would be straight forward so I was proceeding with not that much care.
Sorry for long message I wanted to specify as much as I could on the first time. Please help me - I really would not like to screw the phone.
Thank you in advance for your help
I just want to add - the phone itself always shows only the google logo with a lock at the bottom just as tupp reported previously.
When you see that recovery screen, DON'T DO ANYTHING! -- it is installing Ubports!
I know it is very confusing to see that "recovery" screen appear during an installation, but you are golden. Just let it do it's thing.
By the way, if your phone is not getting past the Google logo/lock, connect your phone to your computer, and in a terminal try "fastboot oem unlock". If the fastboot screen appears on the phone, start the ubports-installer.
Sorry that I forgot to be explicit in my post above that I did nothing when the recovery screen appeared and then the os installed. I have added that "detail" now, thanks to you!
Thank you so much. I am happily writing this message,from Ubuntu touch. The process was fast and automatic from that point. Everything seems to work. I had only one problem with browser the at first it was not accepting ssl certificates. Then I found out that time was not synchronized from wifi maybe it is synchronized only from operator by default. But I first booted without sim card. Because of wrong time browser considered certificate dates as invalid so the problem was easily fixed.
Thanks again for great support.
By the way can I and should I OEM lock the phone now?
I don't think that one can "re-lock" their phone to a particular carrier. Furthermore, there probably is no need to do so, as carriers generally use a phone's IMEI or ESN number to accept or reject a phone. From what I can tell, carriers don't to discern whether a phone is locked or unlocked.
Enjoy your Ubuntu Touch phone!
UniSuperBox last edited by UniSuperBox
Also, if you do
oem lockat this point, the device will be wiped. All Ubuntu Touch data, including the OS itself, is in the
/datapartition. This is not the case for devices that shipped with Ubuntu Touch from BQ and Meizu.
Thank you for that information. I am happy that I did not try it before I saw your post. By the way does it mean that android binaries are still there on another partition? I just wonder if it booted to android if I locked it.
UniSuperBox last edited by
@andirs26 It wouldn't boot to Android because our boot.img that got flashed to your phone does some very specific things while booting Ubuntu Touch. However, it's likely that an Android system is still on
/systemif you haven't wiped it.
Then it is probably there - I only used ubports-flasher in the end. Maybe I am getting a little off topic here - but why are there so many mmcblk0p partitions from mmcblk0p1 to mmcblk0p29? Most of them are pretty small (used lsblk in terminal to get the list)..Also there seems to be separate 4M disk called mmcblk0rpmb--
Hello, I am trying to do exactly the same thing: installing Ubuntu Touch on a Nexus 5 32GB. But I think the Installer really got stuck. It says "Installing. Installing Ubuntu Touch on your device", and further down: "Waiting for device to enter recovery mode... Flashing recovery and boot images". On the phone I see the recovery screen (with the options mentioned by Andirs26). I did nothing but now I have been waiting for over 30 minutes and nothing has happened so far...
What could I do?
@beegee Hi not sure if you install from windows or Linux but you should probably give admen rights to the tools you use purports-installer or fastboot). Remember to oem unlock the phone - see what tupp posted to thins thread. If the phone is unlocked you should see lock pictured under Google logo at boot. If the above is solved then IIRC you should get the phone to fast boot screen and run ubports-installer with admen rights. Choose the correct device if it is not auto selected
@beegee...and click to start the process. The installer should start the recovery mode and do everything automatically.