Related
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip
Can someone upload android wear 1.3 update.zip or the updater-script?
thank you!!
EDIT: link in second page.
not seeing the update yet on the watch.
My watch received the update, but i can't install and after edit the updater-script the watch enter in a bootloop
Anybody else receive the update?
MysteriousSparrow said:
Anybody else receive the update?
Click to expand...
Click to collapse
you will need to do a factory reset before the updatee comes tru
potaturrias said:
My watch received the update, but i can't install and after edit the updater-script the watch enter in a bootloop
Click to expand...
Click to collapse
could you post the update zip, something probably isn't flashed proparly
suljo94 said:
could you post the update zip, something probably isn't flashed proparly
Click to expand...
Click to collapse
https://mega.nz/#!EFcGxLDB!jDbphrownOlCP5Idk4Ko8L1HZegJpYHa4LZCqrTjTKg
There is something wrong with /system/bin/app_process32
Backup before install!!!!
No update either from my side.
deedii said:
No update either from my side.
Click to expand...
Click to collapse
can someone upload system/bin/app_process32??
thank you in advance.
potaturrias said:
can someone upload system/bin/app_process32??
thank you in advance.
Click to expand...
Click to collapse
If you installed SU, it could be possible that your /system/bin/app_process32 and /system/bin/install-recovery.sh have been replaced, the originals should still be on your system as /system/bin/app_process32_original and /system/bin/install-recovery_original.sh, just move them back and the update should work.
cloudrainstar said:
If you installed SU, it could be possible that your /system/bin/app_process32 and /system/bin/install-recovery.sh have been replaced, the originals should still be on your system as /system/bin/app_process32_original and /system/bin/install-recovery_original.sh, just move them back and the update should work.
Click to expand...
Click to collapse
Thank you!! i can install the zip but the watch is not updated...
Edit: I installed stock recovery but i get zip signature error. Still need an unmodified update.zip
Found:
https://android.googleapis.com/packages/ota/lge_bass_bass/8831116af47f7842164aa7ed8efde2984b355e84.signed-bass-LCA44B-from-LDZ22D.8831116a.zip
OK, I'm a little confused. I got the Android Wear 1.3 update to my phone yesterday. However when I check the version number on the watch it says Android wear 1.1.1 I just did a factory reset on the watch and checked and I still have the same 1.1.1 version. Does it take some time to transfer over to the watch?
For what its worth, I can't get the new style interactive watch faces to work. This is understandable since the watch is not using the newest version.
ozaghloul said:
OK, I'm a little confused. I got the Android Wear 1.3 update to my phone yesterday. However when I check the version number on the watch it says Android wear 1.1.1 I just did a factory reset on the watch and checked and I still have the same 1.1.1 version. Does it take some time to transfer over to the watch?
For what its worth, I can't get the new style interactive watch faces to work. This is understandable since the watch is not using the newest version.
Click to expand...
Click to collapse
flashing the file, my watch have 1.3.0.2166028
Why should I need to flash anything? I already got the update form the play store to my phone. Why isn't my phone updating my watch?
ozaghloul said:
Why should I need to flash anything? I already got the update form the play store to my phone. Why isn't my phone updating my watch?
Click to expand...
Click to collapse
The update that you installed is for android wear app, not for the watch.
Deleted for stupidity.
I got my update OTA yesterday - seems to have survived the ordeal.
Argh
I was up until 3 am trying to get my Urbane back to an unrooted, unmodified state (with the exception of OEM unlock). Using the mv command, I replaced the 2 modified files in /system/bin with their originals, and no matter what I do, the 1.3 update won't take. It starts to sideload, but then craps out during the installation, with a message that flashes by briefly that basically states that an error took place. I have checked and rechecked the firmware package (even redownloading it multiple times), but the same thing happens. I believe my device is not truly unrooted, and that there are system files from SuperSU that are preventing this from installing successfully.
Is there a foolproof way to return this watch to stock, wiping out root, and allowing the 1.3 update to take? I am at a loss here. I have tried the TWRP backup/restore as well, and the same thing happens.
Thanks in advance.
If anyone can take a TWRP backup AFTER updating to 1.3 and post it, I am sure it would help me and many others. Thanks in advance.
Could you produce a step by step of the file name change? (mv command)
Thanks in advance
Hey folks,
NOTE: SOLVED, update below
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
UPDATE: I worked out a way of re-flashing an official update without funkyhuawei, check out https://forum.xda-developers.com/p10/development/dev-introducing-redlotus-source-huawei-t3601493
Did you try to install another camera app to see if the camera turn on? it's possible that the data folder of camera to be erased.
Lukx said:
Hey folks,
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
Click to expand...
Click to collapse
Have you tried the HiSuite system restore option. I never used it. But if it works like the restore option from Samsung and Sony. You should restart your phone in recovery mode and the original firmware will be flashed?
Hey
thanks for your answers.
The hisuite does not support my model yet (argh).
OpenCamera works fine, whatsapp's camera feature as well....
The Gallery App is still there, by the way.
I'm having the same issue too after an unsuccessful root which required me to factory reset my P10. After factory rest the stock camera app is missing..
Could someone upload their stock camera backup file? It would be much appreciated.
I attached the HwCamera2 folder with apk, lib and oat folder from /system/priv-app.
I'm on VTR-L29C432B123.
Jannomag said:
I attached the HwCamera2 folder with apk, lib and oat folder from /system/priv-app.
I'm on VTR-L29C432B123.
Click to expand...
Click to collapse
Thanks for the file. May I know how do I get it installed?
I navigated through the same directory and found the same files as yours. I tried installing the apk file from both my own and yours but it says it is corrupted.
Thanks, @Jannomag. I have found that most other Huawei-Apps in that priv-app folder are also missing (except I am not entirely sad about many of those). I'll keep digging a bit.
*Update* I just found in my /etc/whitelistedapps.xml points to /vendor/etc/whitelistedapps.xml, which in turn does not exist.
could somebody with a working Camera app please check whether that file /vendor/etc/whitelistedapps.xml exists, and what is written in there?
This is just a straw I am holding on to, not a real trace or hint, though.
Lukx said:
Thanks, @Jannomag. I have found that most other Huawei-Apps in that priv-app folder are also missing (except I am not entirely sad about many of those). I'll keep digging a bit.
*Update* I just found in my /etc/whitelistedapps.xml points to /vendor/etc/whitelistedapps.xml, which in turn does not exist.
could somebody with a working Camera app please check whether that file /vendor/etc/whitelistedapps.xml exists, and what is written in there?
This is just a straw I am holding on to, not a real trace or hint, though.
Click to expand...
Click to collapse
Hy Lukx, i have exactly the same problem. Wanted to root my phone, but I couldnt see the zip file in twrp, so i wiped whole data and did formatting the whole phone. after reboot my camera app was gone, also the themes were disappeared. I tried installing the firmware for my huawei (from a russian site but I dont know if its the right firmware) but it stopped at 5%.
My Phones Build Number is: VTR-L09C432B113
Thanks
stilla98
Funny thing... I am suspecting that some version mismatch of the recovery or boot partition during the Wipe might be the cause, although I do not have any proof of that.
I am currently trying to write a free alternative to funkyhuawei, so we can flash the full firmware easily again. I think i won't be done with that before mid next week, though...
I am using the OpenCamera app in the meantime.
Lukx said:
Funny thing... I am suspecting that some version mismatch of the recovery or boot partition during the Wipe might be the cause, although I do not have any proof of that.
I am currently trying to write a free alternative to funkyhuawei, so we can flash the full firmware easily again. I think i won't be done with that before mid next week, though...
I am using the OpenCamera app in the meantime.
Click to expand...
Click to collapse
So you are telling me, that the funkyhuawei method works? I saw that my Version is supported. Should I try it?
Thanks
stilla98 said:
So you are telling me, that the funkyhuawei method works? I saw that my Version is supported. Should I try it?
Thanks
Click to expand...
Click to collapse
I didn't say that
But as FH reflashes your phone fully, it should do a full recovery. If you feel like investing money into that, why not try? Otherwise, I recommend you wait along with me for another week and see how far I get with my approach, which I promise to release for free...
Lukx said:
I didn't say that
But as FH reflashes your phone fully, it should do a full recovery. If you feel like investing money into that, why not try? Otherwise, I recommend you wait along with me for another week and see how far I get with my approach, which I promise to release for free...
Click to expand...
Click to collapse
Okay , i will wait for it. I will also install the opencamera app.. by the way, do you also have problems with the design? im having only one design and i cannot add more..
stilla98 said:
im having only one design and i cannot add more..
Click to expand...
Click to collapse
I never really use the theme feature, as I have found "my" favorite theme initially and it's now in the Huawei Backup I carry around through reflashes (highly recommended, it stores on SD card). But the "Designs" app seems to show me a couple of designs, yes. I don't want to try downloading them right now, though.
Lukx said:
I never really use the theme feature, as I have found "my" favorite theme initially and it's now in the Huawei Backup I carry around through reflashes (highly recommended, it stores on SD card). But the "Designs" app seems to show me a couple of designs, yes. I don't want to try downloading them right now, though.
Click to expand...
Click to collapse
okay, i hadnt a microsd card since yesterday, i also backed up my phone before wiping and formatting but there are still no themes, i will try installing them on sd card.. thank you for your help
just install via fastboot boot.img recovery.img cust.img system.img
i have same problem but i can fix it
Same problem
Lukx said:
Hey folks,
NOTE: SOLVED, update below
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
UPDATE: I worked out a way of re-flashing an official update without funkyhuawei, check out https://forum.xda-developers.com/p10/development/dev-introducing-redlotus-source-huawei-t3601493
Click to expand...
Click to collapse
I have the same problem with my Huawei p10, don't have the camera apk but I can use with the open camera. did you fix the problem? Thank you
been there done that
Guy all you need is follow step on this link to restock rom and start unlock bootloader again
You can try to restore factory settings.
Hi,
Sorry of this is a bit of a newbie question but:
What is the purpose of each of the 3 different update zip files ?
And do I have to apply them all - and in what order ?
In my case, I am about to update to B389, and I have downloaded 3 files for VIE-L29C636B389 (currently on VIE-L29C636B130), and I have an update.zip, an update_full_VIE-L29_hw_spcseas.zip and an update_data_full_public.zip.
I was planning on doing the first two by the dload method (with reboots in between), but the update_data_full_public.zip doesn't appear to have an update.app, so how do I load that ? (I do have TWRP on my phone, so could probably figure it out - eventually).
Cheers,
SZ
same question
I read somewhere that it should be flashed in that exact order. i'm guessing that is the same procedure as with auto OTA updates, except now we have rooted phones, so bye-bye to auto updates. I am currently on VIE-L29CB636B387 and i received an automatic Huawei notification of a new version (VIE-L29CB636B388) about a week ago. I tried to update to that version in System Update-Quick Update, but that didn't work (surprise!). There was no issue though as when I rebooted it just went back to 387. However, I now have a red "New Version" notification in my System Update. Please tell me how your upgrade went if you went ahead and flashed 389. I have the three files already from filefinder, i also have TWRP and/or I could use adb fastboot to install. Thanks in advance.
Hey,
I am not sure I want to proceed on the basis of something that somebody 'read somewhere' ....
Anyhow - I've not run these updates yet, as I wanted to backup my phone first, but TWRP keeps blowing up with an error in the middle of the backup, so I am not going to try anything until I get to the bottom of that.
Will let you know if/when I ever go ahead!
Cheers,
SZ
Hi,
TWRP blowing up during NAND backups? thats not a good thing. Upon the advice of a forum member (xzanium) I flashed TWRP 3.1.1-1 instead of TWRP-3.2.1-0-vienna. No hitches so far, solid backups and no hiccups in flashing SuperSU, also got xposed to work seamlessly and other stuff. I hope you are able to resolve the issue you mentioned and get around to getting VIE-L29CB636B389 on your phone.
Well good luck to you, and post here any progress if you would.
SZ,
I have an idea on what the purpose of each of the 3 different update zip files are for and whether you have to apply them all - and in what order.
Since I could make a NAND backup using TWRP without issues, and there was an OTA update notice for an upgrade to VIE-L29CB636B388 which I couldn't upgrade to while rooted, I decided to unroot in order to upgrade to that. First i did the requisite steps - uninstalled the xposed framework and proceeded with the full unroot with SuperSU. Then I performed the dload method to flash the update.app that I extracted from the update.zip.
It was here where i hit a snag. What followed was, I found out that Huawei needs a verified stock rom, meaning it has to be a fullOTA-MF-PV in order that the bootloader could be relocked. So I tried my luck and downloaded the stock ROM VIE-L29C636B370 and flashed that. Success! From there, and several auto upgrades later I was back to L29C636B370. Reinstalling my Google account also locked back FRP. At this point i am full stock EMUI 5
Now, to answer your question. When I tried to upgrade to VIE-L29C636B388 via system update quick update. I only saw one file - update.zip therefore this must the only one needed for incremental patches. The same holds true with update_data_full_public.zip as I later learned when I decided to use the proxy upgrade method in MT filefinder . It applied a 2nd patch. The third file, namely, update_full_VIE-L29_hw_spcseas.zip was not required for this incremental update. In fact, the update process was cut short and an error message appeared that the file could not be located, even though i copied that to the HwOUC folder. It appears that this was deleted before the fullOTA update could finish during the incremental update process. Clearly, this last zip is not necessary for incremental updates. So this must be the package which delivers the rest of the ROM, or the parts of it that needs to be changed.
So, obviously what "I read somewhere" was legit. I hope that answers your question.
cheers!
mm
Anyone else having a problem with the OTA update failing to install?
It'll keep trying over and over and a notification of failure occurs.
I have to "FORCE STOP" for the "Motorola Update Service" in order for it to stop trying.
The filesize is 150815511.
Looking at https://mirrors.lolinet.com/firmware/moto/beckham/official/RETUS/ it would seem *1-6 isn't listed, but rather it jumps to *2-3.
I ended up manually doing the "step"s in "flashfile.xml" from "BECKHAM_PPWS29.183_29_1_2_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml.zip" I took from LMSA to Slot-A.
I'm thinking the whole magisk thing was the culprit, but I'm still going to reinstall it.
Again, like last time, at some point Magisk seems to lose it's SU abilities. The thing is, there was NO version change for my device (not magisk) this time, so there was no reason for the "boot" partition to be overwritten.
This time, after rewriting boot, I updated the Manager and Magisk itself.
Next time, I might just copy out the boot partition and diff it with the patch to see if the patch that was written into boot was overwritten.
Hmm, for some reason I wasn't getting the update failure notification, but I'm guessing my system HAD been trying to update, because when I would wake up, my battery would be much lower than usual.
Looking at the logcat, it would appear that an update to PPWS29.183-29-1-9 exists and is trying to be installed.
Back to doing what I did before to make it happen <sigh...>.
vindicatorr said:
Hmm, for some reason I wasn't getting the update failure notification, but I'm guessing my system HAD been trying to update, because when I would wake up, my battery would be much lower than usual.
Looking at the logcat, it would appear that an update to PPWS29.183-29-1-9 exists and is trying to be installed.
Back to doing what I did before to make it happen <sigh...>.
Click to expand...
Click to collapse
What did you have to do before? This update that keeps failing to install seems to have broken my Google Pay.
gullzway said:
What did you have to do before? This update that keeps failing to install seems to have broken my Google Pay.
Click to expand...
Click to collapse
Sadly, what I did before does not make the other boot slot boot.
Essentially, I manually used fastboot to flash the partition images for version *1-6 following the steps in the xml file zipped up.
You can find recovery images from links in other threads dedicated to them or use LMSA (there was no *1-9 version when I last checked) to download it and find the file(s) in the ProgramData folder.
My understanding is that if you see the steps flashing some images specifically to the one dedicated to slot_b, then you want everything else flashed to slot_a (fastboot --set-active=a).
After that, I "think" the incremental upgrade process is supposed to download the diff (~100MB) between the 2 versions, then unpack the payload to slot_b and then set the active slot to "b".
But even when I used twrp to erase ALL partitions listed in the xml, then manually flashed *1-6 to slot a, it should have done a complete copy of slot_a and the upgrade diff to slot_b, but for whatever reason, even though it DOES seem to happen (looking at the logcat output), the boot fails to occur and it tells me something along the lines of trying again or wiping everything. So then I just set the active slot back to "a" (*1-6).
I didn't want to bother wiping out all of my programs and stuff, so I'm just going to wait for the *1-9 recovery and manually flash that.
I saw NO reason for the boot to fail given I wiped everything but userdata (wiped cache as well).
In the meantime I just disabled the motorola update service.
As for Google Pay, I don't know if you got it working before using the "dg.db" method (https://medium.com/@raphnguyen/andr...-work-with-magisk-through-tasker-2468e720b566).
That's what I used to get my card scanned into it.
So, I found the 1-9 version now registers as existing in LMSA.
But again, sadly, for some reason, it still doesn't want to boot that version. I went back to 1-6 for now and posted a reply to a thread on the Lenovo forum regarding this. I'm not sure if their issue is like mine or not.
I really don't want to delete my userdata partition and can't think of why an update would require it.