• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Installing Ubuntu on Nexus 7 2013 deb (LTE)

Scheduled Pinned Locked Moved Porting
nexus 7 2013
32 Posts 7 Posters 21.5k Views 4 Watching
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.
    • Z Offline
      zubozrout
      last edited by zubozrout 9 Apr 2016, 07:37

      Unfortunately and apparently -each update you'll have to reflash boot.img- (Update: Ok, this is not true - had to do this just once, but normally it works just fine with system updates) so that it installs properly until an update is made to the images. If you then boot the recovery it may start installing the update automatically as it did for me - or you can update manually by the "ubuntu-device-flash --server http://system-image.ubports.com touch --channel ubuntu-touch/rc-proposed" command.

      1 Reply Last reply Reply Quote 0
      • 5 months later
      • D Offline
        doniks
        last edited by 26 Aug 2016, 23:08

        Can you explain what's the story behind that boot.img and recovery.img?

        I'd love to install it on my Nexus 7, but the idea of flashing binary files from some random google drive isn't very appealing to me. Would you mind telling where you got them from or how you made them?

        1 Reply Last reply Reply Quote 0
        • Z Offline
          zubozrout
          last edited by 27 Aug 2016, 06:49

          Hi,
          I created the boot.img and recovery.img using this guide https://developer.ubuntu.com/en/phone/devices/porting-new-device/ and as N7 is a Google device supported by AOSB I did not have to do any specific changes and all worked quite well out of the box. However, I believe the fact this site's repository doesn't work out of-the-box is the fact mariogrip doesn't have the N7 LTE and therefore has no way of extracting the device specific drivers from it as explained on the "Enabling a new device" section on developer.ubuntu.com.

          So you can either believe me that the files I created are ok (I only followed that guide) or create them on your own. Unfortunately because I got no response from mariogrip (after our initial chat) even thought I was trying to help him with the device support, I got rid of my N7 and can no longer help with this any further, but it would be awesome to see someone else contacting him and asking to finish what he started - the N7 LTE's full support is most probably only a step away.

          Good luck...

          1 Reply Last reply Reply Quote 0
          • Z Offline
            zubozrout
            last edited by 27 Aug 2016, 06:53

            However, the device status has changed radically from not-being-listed to being featured as almost working: https://devices.ubports.com/#/deb ... doesn't it work without any modifications yet?

            1 Reply Last reply Reply Quote 0
            • D Offline
              doniks
              last edited by 27 Aug 2016, 11:52

              Yeah, it's listed as almost working, but I think neither the boot.img nor the recovery.img are working right now. I was talking to mariogrip a couple of weeks ago about the unbootable recovery.img and we went through a couple of rounds of me trying to boot them, showing him the error or any observations, him changing things and rebuilding and sending me a new file. In the end ideas and time ran out and we gave up. It looks to me as if the recovery is still in that same state.

              Cool, so you were able to compile them for your self. I had been dabbling with this on and off, but never managed to produce anything that worked. Would you mind me asking some more specific questions after I have dug up my build attempts and reminded myself where I got stuck?

              1 Reply Last reply Reply Quote 0
              • D Offline
                doniks
                last edited by 27 Aug 2016, 12:33

                Ok, I think I know where I got stuck.

                I followed the steps from https://developer.ubuntu.com/en/phone/devices/porting-new-device/ , choosing aosp_deb-userdebug in lunch, that did actually build something and I find recovery.img and boot.img in phablet/out/target/product/deb.

                I can
                fastboot boot recovery.img
                and it seems to work, but no such luck with boot.img
                fastboot boot boot.img appears to be stuck on the bootloader screen of the N7, while
                fastboot flash boot boot.img appear to be stuck on the Google logo boot screen after rebooting.

                At no step during all of this did I knowingly do anything like extracting device specific drivers.

                1 Reply Last reply Reply Quote 0
                • Z Offline
                  zubozrout
                  last edited by 27 Aug 2016, 13:15

                  "At no step during all of this did I knowingly do anything like extracting device specific drivers." that was it for me ... I did that https://developer.ubuntu.com/en/phone/devices/porting-new-device#anchor3 before I built the revocery.img and boot.img.

                  D 1 Reply Last reply 29 Aug 2016, 16:52 Reply Quote 0
                  • Z Offline
                    zubozrout
                    last edited by zubozrout 27 Aug 2016, 13:27

                    Or to be more specific, this is the exact thing I did (first step only): https://wiki.cyanogenmod.org/w/Doc:_porting_intro#Add_the_blobs_to_the_vendor.2F_directory (that Ubuntu site is not much explanatory there, sorry)

                    And then ideally you should end up with something like this in the device tree: http://pastebin.ubuntu.com/23097537/

                    1 Reply Last reply Reply Quote 0
                    • M Offline
                      marxjohnson @zubozrout
                      last edited by 29 Aug 2016, 12:28

                      I attempted to follow these instructions, but after I see the message "Rebooting into recovery to flash" in the terminal, the tablet gets stuck on the "This phone needs restoring from a PC..." screen.

                      D 1 Reply Last reply 29 Aug 2016, 16:21 Reply Quote 0
                      • D Offline
                        doniks @marxjohnson
                        last edited by 29 Aug 2016, 16:21

                        @marxjohnson said in Installing Ubuntu on Nexus 7 2013 deb (LTE):

                        I attempted to follow these instructions, but after I see the message "Rebooting into recovery to flash" in the terminal, the tablet gets stuck on the "This phone needs restoring from a PC..." screen.

                        I had that originally as well, but now I did use the boot.img and recovery.img zubozrout provided in the google drive link and then it worked. Did you use those?

                        M 1 Reply Last reply 29 Aug 2016, 19:35 Reply Quote 0
                        • D Offline
                          doniks @zubozrout
                          last edited by 29 Aug 2016, 16:52

                          @zubozrout said in Installing Ubuntu on Nexus 7 2013 deb (LTE):

                          I did that https://developer.ubuntu.com/en/phone/devices/porting-new-device#anchor3 before I built the revocery.img and boot.img.

                          Ah yes, I followed the link in "Retrieving the proprietary blobs from Android" and extracted the three archives and now my boot.img seems to work.

                          .... now, how do we get this into the ubports repository?!

                          1 Reply Last reply Reply Quote 0
                          • M Offline
                            marxjohnson @doniks
                            last edited by 29 Aug 2016, 19:35

                            @doniks Yes, I followed the instructions just as shown; ran the --bootstrap command, flashed the boot.img and recovery.img, booted into recovery and ran the second flash command.

                            1 Reply Last reply Reply Quote 0
                            • D Offline
                              doniks
                              last edited by 29 Aug 2016, 20:00

                              Mhm, strange. Not sure what that could be. You are sure you have a deb and not a flo?

                              M 1 Reply Last reply 10 Sept 2016, 12:46 Reply Quote 0
                              • 12 days later
                              • M Offline
                                marxjohnson @doniks
                                last edited by 10 Sept 2016, 12:46

                                @doniks Definitely:

                                mark@coachz:~/Downloads/deb_images$ ubuntu-device-flash ubuntu-device-flash --server
                                http://system-image.ubports.com touch --channel ubuntu-touch/rc-proposed --bootstrap
                                2016/09/10 13:33:52 Expecting the device to be in the bootloader... waiting
                                2016/09/10 13:33:52 Device is |deb|
                                
                                1 Reply Last reply Reply Quote 0
                                • D Offline
                                  doniks
                                  last edited by 10 Sept 2016, 12:56

                                  lets take a step back, maybe we can figure it out.

                                  can you install the recovery and then boot into it? what do you see?

                                  M 1 Reply Last reply 19 Sept 2016, 11:22 Reply Quote 0
                                  • D Offline
                                    doniks
                                    last edited by 13 Sept 2016, 18:49

                                    @zubozrout said in Installing Ubuntu on Nexus 7 2013 deb (LTE):

                                    What doesn't work:

                                    • bluetooth
                                    • for some reason camera, but this one should work - may be fixed with server update

                                    It sounds like you are less optimistic about bluetooth than about the camera. Do you know why bluetooth is not working or can you share anything that might help getting it to work?

                                    Z 1 Reply Last reply 13 Sept 2016, 19:27 Reply Quote 0
                                    • Z Offline
                                      zubozrout @doniks
                                      last edited by zubozrout 13 Sept 2016, 19:27

                                      @doniks unfortunately I don't know much on this subject. The reason why I made this statement was the fact I was using Ubuntu on my Nexus 7 deb for a long time, originally with Vojtěch Boček's http://system-image.tasemnice.eu/ server that had unfortunately started to be problematic by the end of 2015 and completely stopped working in February this year. Bluetooth never worked with his builds on Nexus 7 deb while camera did work quite well. However, if you flash flo's image on deb I think that Bluetooth works so perhaps this info may be usable.

                                      D 1 Reply Last reply 13 Sept 2016, 19:44 Reply Quote 0
                                      • D Offline
                                        doniks @zubozrout
                                        last edited by 13 Sept 2016, 19:44

                                        @zubozrout I just tried booting the boot.img for flo from the ubuntu server, but that doesnt make a difference. Maybe installing the complete flo image would make a difference, but I dont feel like setting everything up again. One of these days Ill try.

                                        Z 1 Reply Last reply 14 Sept 2016, 07:27 Reply Quote 0
                                        • Z Offline
                                          zubozrout @doniks
                                          last edited by 14 Sept 2016, 07:27

                                          @doniks Yup, that is what I meant ... the complete official flo image. You can try installing it without the --bootstrap option and if you are lucky you won't lose any data. But I am not sure if that will suffice. It is possible that if and when mariogrip compiles the whole system with the drivers we compiled our recovery and boot images the camera and Bluetooth will miraculously start working - though I know nothing about that process so take it just as a very wild guess.

                                          D 1 Reply Last reply 24 Sept 2016, 16:53 Reply Quote 0
                                          • M Offline
                                            marxjohnson @doniks
                                            last edited by marxjohnson 19 Sept 2016, 11:22

                                            @doniks I finally got it working! I had to use the -w flag when doing the fastboot commands.

                                            The full steps I used for the successful flash:

                                            ubuntu-device-flash touch --channel=ubuntu-touch/stable/ubuntu --device=flo --bootstrap
                                            # Reboot into bootloader
                                            fastboot flash -w boot boot.img
                                            fastboot flash -w recovery recovery.img
                                            # Boot into recovery
                                            ubuntu-device-flash --server http://system-image.ubports.com touch --channel ubuntu-touch/rc-proposed
                                            
                                            D 2 Replies Last reply 24 Sept 2016, 16:38 Reply Quote 0
                                            11 out of 32
                                            • First post
                                              11/32
                                              Last post