Home Page Forums After Sales Services Alldocube X – OTA Update problems

Viewing 10 posts - 1 through 10 (of 15 total)
Alldocube X – OTA Update problems
|
2019-03-26 00:19:28
Member
Starter
#1F
Replies: 14 | Views 4623 | Favorites: 0 | Subscriptions: 4

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
2019-03-27 11:40:06
#2F

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
2019-03-27 11:54:38
#3F

Quote #2F by @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"…

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 ?

版主
2019-03-28 13:21:49
#4F

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

Member
Starter
2019-03-29 01:26:53
#5F

Quote #4F by @win2tabless:

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

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
2019-03-29 10:52:14
#6F

Quote #4F by @win2tabless:

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

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

版主
2019-03-29 16:28:00
#7F

Quote #6F by @David Nessl:

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

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

Member
2019-03-29 17:11:27
#8F

Quote #6F by @David Nessl:

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

“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)

版主
2019-03-29 17:24:15
#9F

Quote #6F by @David Nessl:

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

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
2019-03-29 21:45:18
#10F

Quote #7F by @win2tabless:

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

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.

Viewing 10 posts - 1 through 10 (of 15 total)
Post a new Topic
SUBSCRIBE NOW