Alldocube Global

David Nessl

https://www.alldocube.com/en/forums/users/dnessl/

Replies created

Topic	Forum	Replies/Views	Last activity
Alldocube X – OTA Update problems	Technical Discussion	14 8395	chrrit 2019-03-30 3:23
Yes, that new OTA package installed completely. Thanks! (Settings -> About Tablet now reports Build U1005_v1.1_20190313)
Alldocube X – OTA Update problems	Technical Discussion	14 8395	chrrit 2019-03-30 3:23
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.)
Alldocube X – OTA Update problems	Technical Discussion	14 8395	chrrit 2019-03-30 3:23
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”)
Alldocube X – OTA Update problems	Technical Discussion	14 8395	chrrit 2019-03-30 3:23
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.
Alldocube X – OTA Update problems	Technical Discussion	14 8395	chrrit 2019-03-30 3:23
It appears that the package’s signature keys don’t match my tablet’s. See attached photo of the recovery.log
Alldocube X – OTA Update problems	Technical Discussion	14 8395	chrrit 2019-03-30 3:23
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.

Viewing 6 posts - 1 through 6 (of 6 total)