Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Successful UBports installation and contacts import on Nexus 5

    Support
    3
    3
    1561
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      JoeBeach last edited by

      I just successfully installed UBports onto a used Nexus 5 and imported my contacts via a vcf file from my old phone (Galaxy S2 running cyanogenmod). In case others are doing something like this, here is what I did.

      I bought a used Nexus 5 (16 GB) from Cellular Exchange for $169. It is best to make sure the phone operates with its current ROM before buying it.

      I performed the installation using by laptop running Ubuntu 16.04 LTS.
      I installed Magic Device Tool from github:
      git clone https://github.com/MariusQuabeck/magic-device-tool.git

      From the phone being turned off, I booted to the bootloader (also called fastboot mode) by holding down the Volume Up and Volume Down (press firmly on the center of the volume control bar on the left side of the phone) and then pressing and holding the power button until the bootloader screen appeared. Then I plugged the phone into the computer using its charging/usb cable.

      The messages on the bootloader screen said the phone was locked, so from the Magic Device Tool Directory, I ran launcher.sh and selected the menu items to unlock the bootloader. This made a screen come up on the phone asking for confirmation to unlock it. I selected Yes. The phone then went back to the bootloader screen and showed its status as unlocked. The Magic Device Tool script exited with messages saying it completed successfully.

      I decided to turn off the phone and reboot into the bootloader to make sure the unlocking stayed between boots. It did.

      With the phone in bootloader mode and plugged into the computer, I ran launcher.sh again. This time I selected the menu items for Nexus 5 Ubuntu installation from the legacy channel (the only channel available right now). After selecting the last menu item (telling the script the phone was connected in fastboot/bootloader mode), I got the following in the terminal:


      Detecting device

      039d1dc8437d7fe6 fastboot
      Device detected !

      Flashing legacy channel

      Creating filesystem with parameters:
      Size: 734003200
      Block size: 4096
      Blocks per group: 32768
      Inodes per group: 7472
      Inode size: 256
      Journal blocks: 2800
      Label:
      Blocks: 179200
      Block groups: 6
      Reserved block group size: 47
      Created filesystem with 11/44832 inodes and 5813/179200 blocks
      erasing 'cache'...
      OKAY [ 0.524s]
      sending 'cache' (13348 KB)...
      OKAY [ 0.630s]
      writing 'cache'...
      OKAY [ 1.064s]
      finished. total time: 2.218s
      Creating filesystem with parameters:
      Size: 13725835264
      Block size: 4096
      Blocks per group: 32768
      Inodes per group: 8144
      Inode size: 256
      Journal blocks: 32768
      Label:
      Blocks: 3351034
      Block groups: 103
      Reserved block group size: 823
      Created filesystem with 11/838832 inodes and 93654/3351034 blocks
      erasing 'userdata'...
      OKAY [ 6.249s]
      sending 'userdata' (137318 KB)...
      OKAY [ 4.510s]
      writing 'userdata'...
      OKAY [ 9.115s]
      finished. total time: 19.874s
      rebooting into bootloader...
      OKAY [ 0.134s]
      finished. total time: 0.184s

      2017/07/08 19:26:30 Device is |hammerhead|
      2017/07/08 19:26:31 Flashing version 42 from ubports-touch/legacy channel and server http://system-image.ubports.com to device hammerhead
      2017/07/08 19:26:52 Start pushing /home/joe/.cache/ubuntuimages/ubports-touch/15.04/stable/hammerhead/version-1.tar.xz to device
      2017/07/08 19:26:52 Start pushing /home/joe/.cache/ubuntuimages/pool/ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz to device
      2017/07/08 19:26:52 Start pushing /home/joe/.cache/ubuntuimages/gpg/image-master.tar.xz to device
      2017/07/08 19:26:52 Start pushing /home/joe/.cache/ubuntuimages/pool/device-728a726a0e9a9983dc3b3b5279ab12759b3e15d33a657dd4b9253b3aa27858c1.tar.xz to device
      2017/07/08 19:26:52 Start pushing /home/joe/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
      2017/07/08 19:26:52 Start pushing /home/joe/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
      2017/07/08 19:26:52 error pushing: failed to copy '/home/joe/.cache/ubuntuimages/ubports-touch/15.04/stable/hammerhead/version-1.tar.xz' to '/cache/recovery/': Is a directory

      Move to your device to finish the setup.

      Cleaning up..

      Exiting script. Bye Bye


      During this, phone rebooted to bootloader, then rebooted again and showed a ubports logo, then eventually moved from that to four animated circles. If you look in the terminal messages above, there was a problem pushing some files to the phone. The four animated dots were, unfortunately, the Android splash screen because the Android system had not been fully erased from the phone. I shut down the phone, let it sit for a few minutes, then rebooted it into the bootloader and ran the launcher.sh script again. I selected the menu items to install the legacy channel on a Nexus 5 again. The terminal messages were:


      Detecting device

      039d1dc8437d7fe6 fastboot
      Device detected !

      Flashing legacy channel

      Creating filesystem with parameters:
      Size: 734003200
      Block size: 4096
      Blocks per group: 32768
      Inodes per group: 7472
      Inode size: 256
      Journal blocks: 2800
      Label:
      Blocks: 179200
      Block groups: 6
      Reserved block group size: 47
      Created filesystem with 11/44832 inodes and 5813/179200 blocks
      erasing 'cache'...
      OKAY [ 0.634s]
      sending 'cache' (13348 KB)...
      OKAY [ 0.630s]
      writing 'cache'...
      OKAY [ 1.096s]
      finished. total time: 2.360s
      Creating filesystem with parameters:
      Size: 13725835264
      Block size: 4096
      Blocks per group: 32768
      Inodes per group: 8144
      Inode size: 256
      Journal blocks: 32768
      Label:
      Blocks: 3351034
      Block groups: 103
      Reserved block group size: 823
      Created filesystem with 11/838832 inodes and 93654/3351034 blocks
      erasing 'userdata'...
      OKAY [ 7.467s]
      sending 'userdata' (137318 KB)...
      OKAY [ 4.511s]
      writing 'userdata'...
      OKAY [ 9.133s]
      finished. total time: 21.111s
      rebooting into bootloader...
      OKAY [ 0.136s]
      finished. total time: 0.186s

      2017/07/08 19:41:15 Device is |hammerhead|
      2017/07/08 19:41:15 Flashing version 42 from ubports-touch/legacy channel and server http://system-image.ubports.com to device hammerhead
      2017/07/08 19:41:36 Start pushing /home/joe/.cache/ubuntuimages/pool/ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz to device
      2017/07/08 19:41:36 Start pushing /home/joe/.cache/ubuntuimages/pool/device-728a726a0e9a9983dc3b3b5279ab12759b3e15d33a657dd4b9253b3aa27858c1.tar.xz to device
      2017/07/08 19:41:36 Start pushing /home/joe/.cache/ubuntuimages/ubports-touch/15.04/stable/hammerhead/version-1.tar.xz to device
      2017/07/08 19:41:36 Start pushing /home/joe/.cache/ubuntuimages/gpg/image-master.tar.xz to device
      2017/07/08 19:41:36 Start pushing /home/joe/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
      2017/07/08 19:41:36 Start pushing /home/joe/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
      2017/07/08 19:41:36 Done pushing /home/joe/.cache/ubuntuimages/ubports-touch/15.04/stable/hammerhead/version-1.tar.xz to device
      2017/07/08 19:41:36 Done pushing /home/joe/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
      2017/07/08 19:41:36 Done pushing /home/joe/.cache/ubuntuimages/gpg/image-master.tar.xz to device
      2017/07/08 19:41:36 Done pushing /home/joe/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
      2017/07/08 19:41:46 Done pushing /home/joe/.cache/ubuntuimages/pool/device-728a726a0e9a9983dc3b3b5279ab12759b3e15d33a657dd4b9253b3aa27858c1.tar.xz to device
      2017/07/08 19:42:10 Done pushing /home/joe/.cache/ubuntuimages/pool/ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz to device
      2017/07/08 19:42:10 Created ubuntu_command: /home/joe/.cache/ubuntuimages/ubuntu_commands910527468
      2017/07/08 19:42:10 Rebooting into recovery to flash

      Move to your device to finish the setup.

      Cleaning up..

      Exiting script. Bye Bye


      Note that the terminal messages this time showed the files being pushed without errors. While the terminal output was happening, the phone rebooted to bootloader once, then rebooted to UBports recovery, then rebooted to a ubports splash screen (white background, orange text, gray phone drawings). After 3 minutes the screen went dark, then a Google logo with an unlocked padlock icon appeared. About a minute after that a different UBports screen appeared with Ubuntu-like color scheme and a droid-like icon. Then it started prompting me for language and time zone and such to finish the setup.

      After I finished the setup, I wanted to import my contacts from my old phone (Galaxy S2 running cyanogenmod). I had exported my contacts to a .vcf file and copied that to the Documents folder on the UBports Nexus 5. I went to the Contacts app on UBports importe the vcf file, but it didn't have any options to do that. On a lark, I decided to use the File Browser app and navigated to the Documents folder to make sure the vcf file was there. It was. When I selected it, I was shown a prompt asking what app to use to open the file. One of the options was the Contacts app, so I chose that. It made me very happen when that caused the Contacts App to import the vcf file. It took a minute or two for it to finish the import, but now all of my old contacts are on my new UBports phone.

      I'm excited to be using UBports, I'll be making a donation today.

      1 Reply Last reply Reply Quote 5
      • U
        UniSuperBox last edited by

        Good to hear you were finally able to get it working! Also incredibly interesting that you were able to find that little import function... I will investigate further

        1 Reply Last reply Reply Quote 0
        • A
          andybleaden last edited by

          Interesting how many apps actually have a smart function like that and thanks for sharing

          1 Reply Last reply Reply Quote 0
          • First post
            Last post