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

How to manually upgrade from OTA-3 to OTA-4

Scheduled Pinned Locked Moved General
39 Posts 15 Posters 15.6k 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.
    • M Offline
      marc_aurel @mihael
      last edited by 1 Sept 2018, 14:15

      @mihael This requires a setup for ssh, doesn't it?

      It this instruction up to date? I'm not sure because of the path with the directory "phablet". I wouldn't call a FF2 a phablet.

      M 1 Reply Last reply 1 Sept 2018, 16:25 Reply Quote 0
      • M Online
        mihael @marc_aurel
        last edited by 1 Sept 2018, 16:25

        @marc_aurel I don't remember if I did it this way but just connect a usb cable and then adb shell and you are inside the phone from the computer. Or just type that command for the updatr within the phone terminal app - you don't even need a computer, just the phone connected to internet.

        M 1 Reply Last reply 1 Sept 2018, 20:31 Reply Quote 1
        • M Offline
          marc_aurel @mihael
          last edited by 1 Sept 2018, 20:31

          @mihael Thanks, this works now.

          Unfortunately the settings of the new UBports still doesn't offer custom text size. This is a problem for visual impaired people. Has someone an idea, whether whis is on the roadmap?

          Dekko is not working any more. Has someone a recommendation for an email app?

          S 1 Reply Last reply 1 Sept 2018, 21:04 Reply Quote 0
          • S Offline
            Stefano @marc_aurel
            last edited by 1 Sept 2018, 21:04

            @marc_aurel DEKKO beta is here:

            1 Reply Last reply Reply Quote 0
            • F Offline
              flohack @marc_aurel
              last edited by 1 Sept 2018, 21:20

              @marc_aurel BTW the password is the one of your PC, not the phone...

              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

              1 Reply Last reply Reply Quote 0
              • G Offline
                GT
                last edited by 8 Sept 2018, 17:30

                Hi all, short question:

                if I manually upgrade to OTA-4 following the described steps, will I lose my data and apps or will they remain intact on the device after the update? Thanks.

                A S 2 Replies Last reply 8 Sept 2018, 17:42 Reply Quote 0
                • A Offline
                  advocatux @GT
                  last edited by 8 Sept 2018, 17:42

                  @gt you'll keep all your data as long as you don't check the wipe option.

                  Anyhow, if your data is important for you, you should make a backup

                  1 Reply Last reply Reply Quote 0
                  • S Offline
                    Stefano @GT
                    last edited by 8 Sept 2018, 17:55

                    @gt The apps that were not updated to 16.04 might( most likely) not work, data should stays intact.

                    1 Reply Last reply Reply Quote 0
                    • A Offline
                      Aloys
                      last edited by Aloys 9 Sept 2018, 21:34 9 Sept 2018, 21:23

                      Hello,

                      I tried to install 16.04 stable on FP2, with the method described above, but it failed. I did two attempt, both failed.
                      I have currently 15.04rc22 and I did what is described in this post:
                      [HowTo] [FP2] Update baseband & other firmware. Could it be the reason why it fail? or any idea?
                      In fact I see that it seems to be a known or similar bug described in ubports installer issues. But not clear if there is a workaround or not?

                      The installer I used is ubports-installer_0.1.21-beta_amd64.deb (running in Kubuntu 18.04).

                      It starts correctly but then I have these screen:
                      0_1536526896548_Screenshot_20180909_224708.png

                      Then I close the installer. I have to remove the battery to restart the phone and it starts again with the 15.04rc22 (ouf!).
                      I have one change: the screen at the boot is new (Fairphone powered by UBports and no more android).

                      Here is the full log:

                      me@mylaptop:~/Temp$ ubports-installer 
                      Pug interceptor registered successfully
                      debug: Welcome to the party
                      debug: Killing all running adb servers...
                      debug: Using native platform tools!
                      debug: Running platform tool exec cmd adb kill-server
                      debug: 
                      debug: Running platform tool exec cmd adb -P 5038 kill-server
                      debug: 
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug: Successfully downloaded devices list
                      warn: Running latest stable version.
                      debug: 
                      debug: adb shell: getprop ro.product.device
                      debug: Running platform tool exec cmd adb -P 5038 shell getprop ro.product.device
                      debug: 
                      debug: getprop: FP2
                      debug: adb shell: cat /etc/system-image/channel.ini
                      debug: Running platform tool exec cmd adb -P 5038 shell cat /etc/system-image/channel.ini
                      debug: 
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug: 
                      debug: reboot to bootloader
                      debug: Running platform tool exec cmd adb -P 5038 reboot bootloader
                      debug: 
                      debug: reboot to bootloader [DONE] err:null
                      debug: checking password
                      debug: correct password
                      debug: fastboot: wait for device
                      info: Download startCheck
                      info: checked: recovery-FP2.img
                      info: /home/me/.cache/ubports/images/FP2/recovery-FP2.img already exists with the expected checksum, so download will be skipped
                      info: checked: splash-FP2.img
                      info: /home/me/.cache/ubports/images/FP2/splash-FP2.img already exists with the expected checksum, so download will be skipped
                      info: Download complete
                      info: done downloading(once listener)
                      debug: fastboot: flash; [{"url":"http://cdimage.ubports.com/devices/recovery-FP2.img","checksum":"534cc2da2add4a2bd8136b01069ed7dbe432076659fd4780910b6910b916f77b","type":"recovery","path":"/home/me/.cache/ubports/images/FP2"},{"type":"splash","url":"http://cdimage.ubports.com/devices/splash-FP2.img","checksum":"2bf76ec909af34d9896a954cd6c4ed5ad114d6053e59b7a856325b4fcfca43cd","path":"/home/me/.cache/ubports/images/FP2"}]
                      info: Booting into recovery image...
                      error: Devices: Error: Fastboot: Unknown error:  downloading 'boot.img'...
                      OKAY [  0.360s]
                      booting...
                      FAILED (remote: bootimage: incomplete or not signed)
                      finished. total time: 0.361s
                      
                      info: STARTING OVER
                      debug: Welcome to the party
                      debug: Killing all running adb servers...
                      debug: Using native platform tools!
                      debug: Running platform tool exec cmd adb kill-server
                      debug: 
                      debug: Running platform tool exec cmd adb -P 5038 kill-server
                      debug: 
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug: Successfully downloaded devices list
                      warn: Running latest stable version.
                      debug:  message=Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      , stack=Error: Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      
                         at ChildProcess.exithandler (child_process.js:282:12)
                         at emitTwo (events.js:125:13)
                         at ChildProcess.emit (events.js:213:7)
                         at maybeClose (internal/child_process.js:921:16)
                         at Socket.stream.socket.on (internal/child_process.js:348:11)
                         at emitOne (events.js:115:13)
                         at Socket.emit (events.js:210:7)
                         at Pipe._handle.close [as _onclose] (net.js:549:12), killed=false, code=1, signal=null, cmd=adb -P 5038 shell echo 1
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug:  message=Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      , stack=Error: Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      
                         at ChildProcess.exithandler (child_process.js:282:12)
                         at emitTwo (events.js:125:13)
                         at ChildProcess.emit (events.js:213:7)
                         at maybeClose (internal/child_process.js:921:16)
                         at Socket.stream.socket.on (internal/child_process.js:348:11)
                         at emitOne (events.js:115:13)
                         at Socket.emit (events.js:210:7)
                         at Pipe._handle.close [as _onclose] (net.js:549:12), killed=false, code=1, signal=null, cmd=adb -P 5038 shell echo 1
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug:  message=Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      , stack=Error: Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      
                         at ChildProcess.exithandler (child_process.js:282:12)
                         at emitTwo (events.js:125:13)
                         at ChildProcess.emit (events.js:213:7)
                         at maybeClose (internal/child_process.js:921:16)
                         at Socket.stream.socket.on (internal/child_process.js:348:11)
                         at emitOne (events.js:115:13)
                         at Socket.emit (events.js:210:7)
                         at Pipe._handle.close [as _onclose] (net.js:549:12), killed=false, code=1, signal=null, cmd=adb -P 5038 shell echo 1
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug:  message=Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      , stack=Error: Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      
                         at ChildProcess.exithandler (child_process.js:282:12)
                         at emitTwo (events.js:125:13)
                         at ChildProcess.emit (events.js:213:7)
                         at maybeClose (internal/child_process.js:921:16)
                         at Socket.stream.socket.on (internal/child_process.js:348:11)
                         at emitOne (events.js:115:13)
                         at Socket.emit (events.js:210:7)
                         at Pipe._handle.close [as _onclose] (net.js:549:12), killed=false, code=1, signal=null, cmd=adb -P 5038 shell echo 1
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug:  message=Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      , stack=Error: Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      
                         at ChildProcess.exithandler (child_process.js:282:12)
                         at emitTwo (events.js:125:13)
                         at ChildProcess.emit (events.js:213:7)
                         at maybeClose (internal/child_process.js:921:16)
                         at Socket.stream.socket.on (internal/child_process.js:348:11)
                         at emitOne (events.js:115:13)
                         at Socket.emit (events.js:210:7)
                         at Pipe._handle.close [as _onclose] (net.js:549:12), killed=false, code=1, signal=null, cmd=adb -P 5038 shell echo 1
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug:  message=Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      , stack=Error: Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      
                         at ChildProcess.exithandler (child_process.js:282:12)
                         at emitTwo (events.js:125:13)
                         at ChildProcess.emit (events.js:213:7)
                         at maybeClose (internal/child_process.js:921:16)
                         at Socket.stream.socket.on (internal/child_process.js:348:11)
                         at emitOne (events.js:115:13)
                         at Socket.emit (events.js:210:7)
                         at Pipe._handle.close [as _onclose] (net.js:549:12), killed=false, code=1, signal=null, cmd=adb -P 5038 shell echo 1
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug:  message=Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      , stack=Error: Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      
                         at ChildProcess.exithandler (child_process.js:282:12)
                         at emitTwo (events.js:125:13)
                         at ChildProcess.emit (events.js:213:7)
                         at maybeClose (internal/child_process.js:921:16)
                         at Socket.stream.socket.on (internal/child_process.js:348:11)
                         at emitOne (events.js:115:13)
                         at Socket.emit (events.js:210:7)
                         at Pipe._handle.close [as _onclose] (net.js:549:12), killed=false, code=1, signal=null, cmd=adb -P 5038 shell echo 1
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug:  message=Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      , stack=Error: Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      
                         at ChildProcess.exithandler (child_process.js:282:12)
                         at emitTwo (events.js:125:13)
                         at ChildProcess.emit (events.js:213:7)
                         at maybeClose (internal/child_process.js:921:16)
                         at Socket.stream.socket.on (internal/child_process.js:348:11)
                         at emitOne (events.js:115:13)
                         at Socket.emit (events.js:210:7)
                         at Pipe._handle.close [as _onclose] (net.js:549:12), killed=false, code=1, signal=null, cmd=adb -P 5038 shell echo 1
                      debug: adb shell: echo 1
                      debug: Running platform tool exec cmd adb -P 5038 shell echo 1
                      debug:  message=Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      , stack=Error: Command failed: adb -P 5038 shell echo 1
                      error: no devices/emulators found
                      
                         at ChildProcess.exithandler (child_process.js:282:12)
                         at emitTwo (events.js:125:13)
                         at ChildProcess.emit (events.js:213:7)
                         at maybeClose (internal/child_process.js:921:16)
                         at Socket.stream.socket.on (internal/child_process.js:348:11)
                         at emitOne (events.js:115:13)
                         at Socket.emit (events.js:210:7)
                         at Pipe._handle.close [as _onclose] (net.js:549:12), killed=false, code=1, signal=null, cmd=adb -P 5038 shell echo 1
                      debug: Killing all running adb servers...
                      debug: Using native platform tools!
                      debug: Running platform tool exec cmd adb kill-server
                      Good bye!
                      debug: 
                      debug: Running platform tool exec cmd adb -P 5038 kill-server
                      debug: 
                      
                      
                      me@mylaptop:~/Temp$
                      
                      A 1 Reply Last reply 9 Sept 2018, 23:17 Reply Quote 0
                      • A Offline
                        advocatux @Aloys
                        last edited by 9 Sept 2018, 23:17

                        @ublublu @lionelb has reported success finally going from vivid to xenial on a FP2 using UBports Installer version 0.1.12-beta (YMMV).

                        1 Reply Last reply Reply Quote 1
                        39 out of 39
                        • First post
                          39/39
                          Last post