Home Forums After Sales Services Alldocube X – OTA Update problems

This topic contains 14 replies, has 4 voices, and was last updated by  chrrit 3 weeks, 5 days ago.

  • Author
    Posts
  • Member
    @chrrit
    chrrit(Starter)

    Hi,

    the OTA update of doesn’t work: it shows in the Wireless updates a new version, it is downloading, “install now” and reboot also ok, but it seems that it is not installing, because after reboot is finished same SW version and wireless update is again available…

    Anyone got an idea please?

     

  • Member
    @dnessl
    David Nessl

    Me too.  New update it tries to install is U1005_v1.1_20190313_20190313-1057

    If you watch the update, you will momentarily see “Installing system update” and progress bar, then an image of the Android “droid” laying on its side and the word “error” for a few seconds before it reboots automatically.  Which means the OTA/wireless update didn’t get applied.

    FYI, my Settings –> About Tablet says I have a Model U1005 running vendor-supplied Android 8.1.0 with Build number U1005_V1.0_20190116.  I haven’t loaded/flashed any mods — I’m running completely vanilla as delivered by the manufacturer.

    • Member
      @oliwek
      oliwek

      Hi. I have the same issue on my european Alldocube X (U1005E). Download OTA 20190313, unpack, reboot in recovery then fails with an ‘error’ message shown on recovery screen. Then reboot in its previous non updated state.

      I secured the Android boot on my device with a scheme I have to draw on a 3×3 grid (at each reboot). Maybe this is related ?

  • Member
    @win2tabless
    win2tabless

    all you guys can post pic show recovery.log in recovery mode(recpvery.log can show the detail about error )

    • Member
      @chrrit
      chrrit(Starter)

      i have no idea how to get this log file. if you could explain this to a medium experienced techie, i will try…

      just to add, the same happens if you download the update file and start a local update….

    • Member
      @dnessl
      David Nessl

      Android tablets/phones have a 2nd bootable image, called the recovery image, separate from the “system” image that you normally run.  The recovery image can be used to (a) recover (duh) if your system image becomes broken and unable to boot, and (b) to do updates to the system image because it can cause problems for a system image to try to update itself while it’s running.

      One normally can boot into the recovery image in either of two ways:

      Method 1: Power-off the tablet, then simultaneously hold down the power key and one of the other keys (volume-up or volume-down).  I couldn’t get either key combo to work by experimenting, tho this method is somewhat timing dependent.  It would help if Alldocube let us know the key-combo needed for for the Alldocube-X.

      Method 2: While running the normal Android system, connect it to a PC via USB cable, then use the “adb” command on the PC to boot the tablet into recovery mode.  (“adb reboot recovery”)  This is what I had to use.  (To use this method, you have to install Google’s “platform tools” on your PC.  Then on your tablet you have to enable the secret developer mode and then enable USB debugging. Web search for the info.)

    • Member
      @dnessl
      David Nessl

      It appears that the package’s signature keys don’t match my tablet’s.  See attached photo of the recovery.log

    • Member
      @win2tabless
      win2tabless

      so,the pic is your recovery.log.and your tablet android os build number is U1005_V1.0_20190116?

    • Member
      @dnessl
      David Nessl

      Yes, that photo is of the recovery.log (while booted into recovery) after a failed wireless update attempt.

      And yes, my Settings –> About Tablet says I am currently running Android 8.1.0 with Build number U1005_V1.0_20190116.

      Here’s another photo of the log that shows the full error message line (including the keys it is expecting to find).

      Is there some way to grab the text version of the recovery logs?  If this recovery was TWRP, I’d just boot into TWRP recovery and pull the files via adb.

    • Member
      @win2tabless
      win2tabless

      please try ota update again, a new ota package has been upload to ota server

    • Member
      @dnessl
      David Nessl

      Yes, that new OTA package installed completely.  Thanks!

      (Settings -> About Tablet now reports Build U1005_v1.1_20190313)

    • Member
      @oliwek
      oliwek

      “script aborted : E3001 : package expects build fingerprint” so this is related to what I wrote above (secured android boot with PIN/fingerprint/3×3 grid) ? (I mean secured boot of the OS, not just log in in your personal session)

    • Member
      @dnessl
      David Nessl

      Nope, none of this is related to your system PIN or lock-screen pattern.  The “keys” that the error message talks about are digital signatures associated with the update images — they ensure that (1) the downloaded update image is uncorrupted and unaltered, and (2) they are “official”, i.e. created by the Alldocube company’s developers.   (For more info see the Wikipedia article on “Digital Signature”)

    • Member
      @win2tabless
      win2tabless

      one more question ,is your android update from build number 20181227 to 20190116,and then update to 20190313?

      If this is the case, probably know what caused the upgrade error (1227-0116 OTA package problem).
      TF packages of 20190116 or  20190108(for u1005e) will be released next week, flash 20190116  or 20190108(for u1005e) TF packages ,and last upgrade firmware to 20190313 version.that may be final sulution.

       

  • Member
    @chrrit
    chrrit(Starter)

    Hi,

    I had contact with the support and they have uploaded a new OTA package and it works now!

    Great support!

     

     

You must be logged in to reply to this topic.