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

August 15 devel channel update renders your device unable

Scheduled Pinned Locked Moved Support
32 Posts 8 Posters 6.0k Views 2 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.
    • S Offline
      shapley
      last edited by 15 Aug 2018, 11:16

      Happened for me too...rolled back to 16.04r/c

      1 Reply Last reply Reply Quote 0
      • A Offline
        advocatux @domubpkm
        last edited by advocatux 15 Aug 2018, 11:18

        @domubpkm can you change your post title to something like "August, 15 devel channel update renders your device unable" because this issue is happening in all devices. Sorry if I'm asking you too many things today ๐Ÿ™‚

        Now, if you need a working device again, I think one of the best routes is to go to the 16.04 RC channel.

        You need to have ยซdeveloper modeยป still on in your device. Connect using an usb cable and adb to your device ( adb shell), and once you are in , run sudo system-image-cli -vvvv --switch 16.04/rc

        Then wait for a while (you'll know when it's done because the CLI will return to the system prompt, and your device will reboot) and you should have a working device again.

        Edit to add that this process doesn't delete any of your data

        D 1 Reply Last reply 15 Aug 2018, 11:30 Reply Quote 0
        • L Offline
          Lakotaubp @domubpkm
          last edited by 15 Aug 2018, 11:22

          @domubpkm Yes roll back to RC seems to very the advice. Only just picking this up lots more on Telegram supergroup.
          I updated my OPO this morning to 248 and didn't see this welcome message so is it 249 thats the problem

          1 Reply Last reply Reply Quote 0
          • A Offline
            advocatux
            last edited by 15 Aug 2018, 11:30

            @domubpkm thank you for changing the title, and thank you for your patience ๐Ÿ™‚

            1 Reply Last reply Reply Quote 0
            • D Offline
              domubpkm @advocatux
              last edited by 15 Aug 2018, 11:30

              @advocatux Done, change the title of the post. For solving the problem, i must wait at least tomorow to get my ubuntu computer back ! I have only a windows 10 netbook with me....
              Thanks very much !

              A 2 Replies Last reply 15 Aug 2018, 11:30 Reply Quote 0
              • A Offline
                advocatux @domubpkm
                last edited by 15 Aug 2018, 11:30

                @domubpkm lol we posted at the same time

                1 Reply Last reply Reply Quote 0
                • A Offline
                  advocatux @domubpkm
                  last edited by 15 Aug 2018, 11:33

                  @domubpkm I don't know about windows netbooks but maybe you can install adb in it?

                  D 2 Replies Last reply 15 Aug 2018, 11:49 Reply Quote 0
                  • D Offline
                    domubpkm @advocatux
                    last edited by 15 Aug 2018, 11:49

                    @advocatux It's can wait.. It's not fully vital. It's not my main phone. My main phone has Vidid 15.04 r3 for the moment.. Because it's a real lack for me (and others maybe) not to have a fully operational dekko : I'm conscious of the big efforts of the developpers on dekko.

                    A 1 Reply Last reply 15 Aug 2018, 11:52 Reply Quote 0
                    • A Offline
                      advocatux @domubpkm
                      last edited by 15 Aug 2018, 11:52

                      @domubpkm I'm reading the fresh bug report now (https://github.com/ubports/ubuntu-touch/issues/821). Maybe you can try that workaround that works in FP2 at least, before doing anything else

                      K D 2 Replies Last reply 15 Aug 2018, 12:35 Reply Quote 0
                      • K Offline
                        killerbee @advocatux
                        last edited by 15 Aug 2018, 12:35

                        @advocatux Workaround doesnt work for my BQ10 FHD, but fallback to rc channel does

                        A 1 Reply Last reply 15 Aug 2018, 12:40 Reply Quote 0
                        • A Offline
                          advocatux @killerbee
                          last edited by advocatux 15 Aug 2018, 12:40

                          @killerbee yeah, it seems the workaround doesn't work for Pro 5, Arale, and Frieza (those are the devices reported for now).

                          1 Reply Last reply Reply Quote 1
                          • D Offline
                            domubpkm @advocatux
                            last edited by 15 Aug 2018, 13:13

                            @advocatux I hit the phone against the wall, nothing happen for me ! ๐Ÿ™‚

                            A 1 Reply Last reply 15 Aug 2018, 14:36 Reply Quote 0
                            • A Offline
                              advocatux @domubpkm
                              last edited by 15 Aug 2018, 14:36

                              @domubpkm lol

                              M 1 Reply Last reply 15 Aug 2018, 15:40 Reply Quote 0
                              • M Offline
                                Marathon2422 @advocatux
                                last edited by 15 Aug 2018, 15:40

                                @advocatux
                                I think someone is trying to convince you Devs that you need that "edge" LOL

                                A 1 Reply Last reply 15 Aug 2018, 15:55 Reply Quote 0
                                • A Offline
                                  advocatux @Marathon2422
                                  last edited by 15 Aug 2018, 15:55

                                  @marathon2422 good point XD (but I'm just a user)

                                  1 Reply Last reply Reply Quote 0
                                  • D Offline
                                    domubpkm @advocatux
                                    last edited by 15 Aug 2018, 17:12

                                    @advocatux I don't now if i said something unrealistic or infeasible : i don't think there is a command prompt, something similar as TERMINAL in UBPORTS RECOVERY. Isn't it ? If the system freeze, don't you think it would be a good idea to be able to lauch commands lines so as to unfreeze a phone without another computer ? Or to have a mechanism to change the channel (in this case devel to rc ?). If it is stupid idea, sorry....

                                    A 1 Reply Last reply 15 Aug 2018, 18:05 Reply Quote 0
                                    • A Offline
                                      advocatux @domubpkm
                                      last edited by advocatux 15 Aug 2018, 18:05

                                      @domubpkm no, there isn't.

                                      It's not an stupid idea at all but I don't have the technical knowledge about how recovery works in detail, maybe someone with that sort of expertise will reply later.

                                      Off the top of my head, the first problem I see is the (possible) lack of space, but on the other hand I've seen custom android recoveries with much more tools than stock android recoveries, so...

                                      Edit: thinking a bit more about it, the main problem is how to have a keyboard on-screen for input. It would has to be a list of pre-formatted commands or something like that

                                      1 Reply Last reply Reply Quote 0
                                      • L Offline
                                        Lakotaubp
                                        last edited by 15 Aug 2018, 19:01

                                        Just to clarify etc on getting round this issue.
                                        1 Stay on RC or don't update your dev device with todays update, or revert to RC in system settings.
                                        2 Wait till next dev update is released with issue fixed.
                                        3 Update to that and all should be ok.
                                        Is this correct

                                        A 1 Reply Last reply 15 Aug 2018, 19:09 Reply Quote 0
                                        • A Offline
                                          advocatux @Lakotaubp
                                          last edited by advocatux 15 Aug 2018, 19:09

                                          @lakotaubp going to RC is the fastest and easier way to have a running device again, and keep it on the save side.

                                          If whoever is hit by this issue want to run a lower devel version, that's feasible too but I think the RC way is more user friendly for now.

                                          Edit: I forgot to say yes, that's correct ๐Ÿ™‚

                                          1 Reply Last reply Reply Quote 0
                                          • A Offline
                                            advocatux
                                            last edited by advocatux 15 Aug 2018, 21:02

                                            Some people has asked me in private how to stay in the devel channel, so I think it's better if I post the command here ๐Ÿ™‚

                                            ubuntu-device-flash --server=http://system-image.ubports.com touch --device=codename --channel=ubports-touch/16.04/devel --revision=version_number

                                            • Change codename for the proper one for your device. See here https://devices.ubuntu-touch.io/ the codenames list
                                            • version_number means a version number that is not affected by this issue. See the latest good one (that's the previous version to the one affected) for your device here http://system-image.ubports.com/ubports-touch/16.04/devel/

                                            Edit: the issue has been fixed now (https://github.com/ubports/ubuntu-touch/issues/821#issuecomment-413356669) so you can use the latest version_number.

                                            1 Reply Last reply Reply Quote 0
                                            11 out of 32
                                            • First post
                                              11/32
                                              Last post