I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
This also what happened to me.
szophiya said:
I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
JazzieBoi said:
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
Click to expand...
Click to collapse
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
arda99 said:
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
Click to expand...
Click to collapse
Wow I had no idea metro did that. I knew metro doesn't like unlocked bootloader's and are strict. I will never buy one in my life .
szophiya said:
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Click to expand...
Click to collapse
You could try flashing the stock boot.img via fastboot to see if it finishes installing. https://forum.xda-developers.com/attachments/boot-11-0-1-be88cf-img-zip.5399231/
You'll need to reboot to fastboot and then run: fastboot flash boot_a boot-11-0-1-be88cf-img and then fastboot boot_b (img filename). Try rebooting and performing the update then.
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Misclicked and did a double post, sorry.
szophiya said:
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Click to expand...
Click to collapse
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
JazzieBoi said:
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
Click to expand...
Click to collapse
The MSM you provided is for BE86AA and BE89BA, not for BE88CF which is what they need.
As far as I know, no MSM exists for BE88CF: https://forum.xda-developers.com/t/...8cf-11-0-2-be88cf-rooting-impossible.4367271/
Related
Hello Everyone,
I badly need help on my Huawei Honor U8860 phone. I have recently updated it from 2.3.6 to 4.03 over WIFI and the update went smoothly. So now here is what my phone have:
Kernel Version: 3.0.8-perf-00059-g3a757a2 [email protected] #1
Build Number: U8860IV100R001C00B923SP01
I have not rooted the phone at this time. It was working fine until 2 days ago when I started getting messages on the screen like:
"Unfortunately, 2D Home has stopped"
"Unfortunately, Google Play has stopped"
"Unfortunately, Contacts has stopped"
"Unfortunately, Settings has stopped"
"Unfortunately, Google Play Music has stopped"
"Unfortunately, Browser has stopped"
And so on, and so forth. It seems that all apps and processes have stopped when I try to use them so I literally can't use the phone. I went through several threads here just trying to restore my phone back to a
working state. I tried to do the following in order but without success:
1.) Factory data reset / erase everything - the phone boots to the recovery menu then it formats the /Data, /Cache and /HWUserData then it reboots. After reboot, the phone is back to where it was before the factory data reset with everything in it including downloaded apps.
2.) Manually uninstalled all downloaded apps. Removed screen lock (just to see if phone behavior changes). Then rebooted the phone but after reboot, all the apps are still installed and the screen lock is back as well.
3.) I tried to Force Update with the following official ROMs: B886, B919 and B923 but I always get the message "Update failed" during the update process.
4.) I downloaded the file "recovery-u8860-en.img" so I can replace the "recovery.img" file . Rebooted the phone w/ the pink screen and connected it to my PC but there is no USB mass storage device mounted.
5.) Finally, I tried to root the phone. I enabled USB debugging. I installed the ADB drivers then I downloaded the U8860 root tools and rootexplorer.apk. When I ran the "root-me.cmd", it tried to copy some files to the phone but it failed. The error was "read-only file system".
So it seems that the problem is because of the "read-only filesystem". I does not permit/allow any changes made to the phone. Can you help me restore my phone?
Please.. Can somebody help me on this?
Thanks, clint2rose
clint2rose said:
Please.. Can somebody help me on this?
Thanks, clint2rose
Click to expand...
Click to collapse
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
clint2rose said:
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
Click to expand...
Click to collapse
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
kaefert said:
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
Click to expand...
Click to collapse
thanks for the reply. it did not work. I even formatted the internal SD. Re-run the firmware update but it failed. when i boot the phone, all the contents of the internal SD remains intact. any other suggestion?
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
kaefert said:
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
Click to expand...
Click to collapse
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
clint2rose said:
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
Click to expand...
Click to collapse
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
kaefert said:
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
Click to expand...
Click to collapse
Thank you once more for your time. Most of the thread I read regarding these patches often used the phrase" you have to flash the current version of your ROM using the patch"...
And yes I created dload folder, place the UPDATE.APP and put it on the sdcard. I turned off the phone and removed the battery. Then I pressed vol+ vol- and power on/off button. The firmware update went to about 70% installing before displaying update failed.
I guess I will have to bring my phone to a repair center. My only problem is that there is no Huawei service center at my place (I reside here in Saudi Arabia). I got the phone as a free device on a broadband package and the warranty is already expired. I'm a little worried to take the phone to the small mobile repair shops as they might screw up the phone even more. Huawei is not a popular device here unlike iPhone, HTC and Samsung Galaxy.
As I understood that your device is rooted, you should get some custom ROM and try to install it.
okty2k said:
As I understood that your device is rooted, you should get some custom ROM and try to install it.
Click to expand...
Click to collapse
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
clint2rose said:
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
Click to expand...
Click to collapse
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
kaefert said:
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
Click to expand...
Click to collapse
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
U8860 not responding
clint2rose said:
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
Click to expand...
Click to collapse
Have you find the solution yet? I have the same problem. Somehow my phone system is "locked". I can't install or uninstall app. Some google apps keep showing not responding. Everything changes i made, keep showing up after the phone rebooted.
This was happen a few days after I upgrade to ICS B932SP01 and rooted my phone (to remove original chinese apps).
Luckily i have friend in huawei indonesia. He gave my u8860 to the technical support. But the result was no good.
They try everything, even install my phone with the original GB and always failed.
The last suggestion is change the phone machine, which is as same as buy a new phone.
I really appreciate is someone can help me here...
Thanks
NOTE: This patch is only for upgrading from 12B to 23A. If you're currently on 10B or 11C, you'll need to upgrade to 12B before applying this patch. If wanted, I can upload those two patches as well.
Though there's already a thread about update 23A on the VS985, I figured an actual release of the OTA would warrant its own thread.
This is a release of the Verizon LG G3 5.0 OTA (VS98523A). The OTA package is unmodified (and probably couldn't be modified, at least easily, due to signing in the OTA package format). It was downloaded directly from Verizon's OTA servers. The OTA patch is only for version 12B; if you want to apply this upgrade and are running a version prior to 12B, you'll have to get to version 12B before applying the 23A patch.
You can download the package at http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/LG_VS985_12B-23A.dlpkgfile.
UPDATE: I've uploaded all three OTA update packages (10B to 11C, 11C to 12B, and 12B to 23A) to http://downloads.codefi.re/illegalargument/LG_VS985/.
The package is in an odd format and it is rather difficult to extract files from it, as many of the updates are provided in diff patches. However, there is a relatively simple way to apply this OTA using VerizonHiddenMenu. Root access is required to run the VerizonHiddenMenu activity.
Download the OTA package from the link above.
Copy the package to your device as either /storage/sdcard0/SoftwareUpdate/23A.up or /storage/external_SD/SoftwareUpdate/23A.up (technically, the filename can vary as long as it ends in the .up extension and is one of those two locations).
Run the following command:
Code:
adb shell su -c "am start -n com.lge.VerizonHiddenMenu/.fota.DmcTestFotaMenu"
This will start the diagnostic FOTA menu from the Verizon Hidden Menu.
From here, click on the "Select Package" option, and then choose "23A.up" from the list.
Once you've selected the update package, choose the "Do update" option from the menu. This should apply the update and if all goes well, you'll wake up with 23A when it's all done.
That's all there is to it. Have fun!
Annnnnd here we go! Lol
Nice work!
We need a Guinea pig that is willing to stay on stock/unrooted/locked 5.0 in order to test downgrade ability via kdz/tot.... Not it!
So if anyone is up for initiating this ota via terminal, can you please do some additional work by testing out downgrading? I have a 12b kdz file link in my thread that you can flash back to in order to push the lp update again (if downgrading works).
*edit*, command requires root, so full roll back to 10b will be required. Stock unrooted 12b is SOL unless you roll back for this method.
Thanks .....
Thank you!
I was going to mention I might become a guinea pig, but I'm not quite that brave yet. Maybe I will be in the morning when I've had proper sleep, and depending on what I've got got on at work.
I just planned on testing keeping root with SuperSU's keep root option, but otherwise completely stock besides the hidden menu requirement.
Sent from my VK810 4G
Thank you! Finally!
Do you have to be on stock KitKat for this to work?
I, too, am very anxious to see what the "guinea pig's" result of a potential downgrade is....that ominous "security software version" seen in that screenshot that has been circulating has me a tad worried though tbh. Thankfully I've gotten all the g3's I need for right now and have rooted/unlocked then all....but there's one more I'd like to get in about ~10 months (don't ask, long story) and would like to be able to root/unlock it, so really hoping for the best here!
---------- Post added at 05:04 AM ---------- Previous post was at 05:03 AM ----------
luke24 said:
Thank you! Finally!
Do you have to be on stock KitKat for this to work?
Click to expand...
Click to collapse
You would need to be on stock KitKat w/ stock recovery, yes.
luke24 said:
Thank you! Finally!
Do you have to be on stock KitKat for this to work?
Click to expand...
Click to collapse
Yes completely stock. No modifications. A reminder that this will break any exploits we have so far for rooting, you've been warned. Please tread cautiously. [emoji106]
Sent from my VS985 4G using Tapatalk
skiman10 said:
Yes completely stock. No modifications. A reminder that this will break any exploits we have so far for rooting, you've been warned. Please tread cautiously. [emoji106]
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Yea I kinda thought so..
This is exciting, but I think I'm gonna wait too...
Someone correct me if I'm wrong - but as far as anyone knows, literally anything could happen if one upgraded to his 23A update and then attempted to kdz back to 12B (or 10B_01, for that matter) - up to an including anything ranging from the downgrade simply erroring in flash tool and not working and you being OK but totally "stuck" on stock LP for the foreseeable future.....to a potential hard brick of your device, right?? It's the latter possibility that definitely would scare the ****ahky mushrooms out of me LOL
IllegalArgument said:
Though there's already a thread about update 23A on the VS985, I figured an actual release of the OTA would warrant its own thread.
This is a release of the Verizon LG G3 5.0 OTA (VS98523A). The OTA package is unmodified (and probably couldn't be modified, at least easily, due to signing in the OTA package format). It was downloaded directly from Verizon's OTA servers.
You can download the package at http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/LG_VS985_12B-23A.dlpkgfile.
The package is in an odd format and it is rather difficult to extract files from it, as many of the updates are provided in diff patches. However, there is a relatively simple way to apply this OTA using VerizonHiddenMenu. Root access is required to run the VerizonHiddenMenu activity.
Download the OTA package from the link above.
Copy the package to your device as either /storage/sdcard0/SoftwareUpdate/23A.up or /storage/external_SD/SoftwareUpdate/23A.up (technically, the filename can vary as long as it ends in the .up extension and is one of those two locations).
Run the following command:
Code:
adb shell su -c "am start -n com.lge.VerizonHiddenMenu/.fota.DmcTestFotaMenu"
This will start the diagnostic FOTA menu from the Verizon Hidden Menu.
From here, click on the "Select Package" option, and then choose "23A.up" from the list.
Once you've selected the update package, choose the "Do update" option from the menu. This should apply the update and if all goes well, you'll wake up with 23A when it's all done.
That's all there is to it. Have fun!
Click to expand...
Click to collapse
@IllegalArgument, thank you for the dlpkgfile patch. I'll use it to build a rooted 23A ROM.
hsbadr said:
@IllegalArgument, thank you for the dlpkgfile patch. I'll use it to build a rooted 23A ROM.
Click to expand...
Click to collapse
That would be awesome!!! Thanks!
ohlin5 said:
I, too, am very anxious to see what the "guinea pig's" result of a potential downgrade is....that ominous "security software version" seen in that screenshot that has been circulating has me a tad worried though tbh.
You would need to be on stock KitKat w/ stock recovery, yes.
Click to expand...
Click to collapse
Some info on that security software message
commoncriteriaportal.org/files/epfiles/st_vid10593-vr.pdf
niap-ccevs.org/st/Compliant.cfm?pid=10593
gsmarena.com/at_ts_lg_g3_is_receiving_the_android_50_lollipop_update_too-news-11143.php
TLDR: Basically, just its just a certification that all US varients have passed. Shows up in ATT version too, and ATT has confirmed rollback
mattd7591 said:
Some info on that security software message
commoncriteriaportal.org/files/epfiles/st_vid10593-vr.pdf
niap-ccevs.org/st/Compliant.cfm?pid=10593
gsmarena.com/at_ts_lg_g3_is_receiving_the_android_50_lollipop_update_too-news-11143.php
TLDR: Basically, just its just a certification that all US varients have passed. Shows up in ATT version too, and ATT has confirmed rollback
Click to expand...
Click to collapse
Interesting....well I still won't hold my breath given the things I've seen VZW do in the past, but thanks for the info, good find!
hot wings and beer explanation of wht this means...?????????????
great work
annoyingduck said:
Nice work!
We need a Guinea pig that is willing to stay on stock/unrooted/locked 5.0 in order to test downgrade ability via kdz/tot.... Not it!
So if anyone is up for initiating this ota via terminal, can you please do some additional work by testing out downgrading? I have a 12b kdz file link in my thread that you can flash back to in order to push the lp update again (if downgrading works).
Click to expand...
Click to collapse
I'd be willing to try it out and test the ability to downgrade but I won't be near a pc until 10 hours from now.
Error
IllegalArgument said:
Though there's already a thread about update 23A on the VS985, I figured an actual release of the OTA would warrant its own thread.
This is a release of the Verizon LG G3 5.0 OTA (VS98523A). The OTA package is unmodified (and probably couldn't be modified, at least easily, due to signing in the OTA package format). It was downloaded directly from Verizon's OTA servers.
You can download the package at http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/LG_VS985_12B-23A.dlpkgfile.
The package is in an odd format and it is rather difficult to extract files from it, as many of the updates are provided in diff patches. However, there is a relatively simple way to apply this OTA using VerizonHiddenMenu. Root access is required to run the VerizonHiddenMenu activity.
Download the OTA package from the link above.
Copy the package to your device as either /storage/sdcard0/SoftwareUpdate/23A.up or /storage/external_SD/SoftwareUpdate/23A.up (technically, the filename can vary as long as it ends in the .up extension and is one of those two locations).
Run the following command:
Code:
adb shell su -c "am start -n com.lge.VerizonHiddenMenu/.fota.DmcTestFotaMenu"
This will start the diagnostic FOTA menu from the Verizon Hidden Menu.
From here, click on the "Select Package" option, and then choose "23A.up" from the list.
Once you've selected the update package, choose the "Do update" option from the menu. This should apply the update and if all goes well, you'll wake up with 23A when it's all done.
That's all there is to it. Have fun!
Click to expand...
Click to collapse
Quick question on this...
I did all of the above, am on software 10B rooted with StumpRoot, put the file in /storage/sdcard0/SoftwareUpdate/23A.up, but after selecting the file at "Select Package" it hangs for a few seconds, gives me a toast notification that reads "Download = 23A.up", but when I press Do Update it reads, "RESULT_NOT_EXECUTED". Screenshots of the progress included. Any reason I'm getting this message? I tried renaming the file to 23A.up on the device first, then on the PC, and both times moved the file to the directory in sdcard0 (which didn't exist, I created the "SoftwareUpdate" folder). I'd be very grateful if someone could help me out.
First pic is selecting the file, second is it hanging and then returning to the FOTA Test Menu, and the last is obviously the error. I really would appreciate some help on this. Thanks in advance.
KlausWillSeeYouNow said:
Quick question on this...
I did all of the above, am on software 10B rooted with StumpRoot, put the file in /storage/sdcard0/SoftwareUpdate/23A.up, but after selecting the file at "Select Package" it hangs for a few seconds, gives me a toast notification that reads "Download = 23A.up", but when I press Do Update it reads, "RESULT_NOT_EXECUTED". Screenshots of the progress included. Any reason I'm getting this message? I tried renaming the file to 23A.up on the device first, then on the PC, and both times moved the file to the directory in sdcard0 (which didn't exist, I created the "SoftwareUpdate" folder). I'd be very grateful if someone could help me out.
First pic is selecting the file, second is it hanging and then returning to the FOTA Test Menu, and the last is obviously the error. I really would appreciate some help on this. Thanks in advance.
Click to expand...
Click to collapse
Additional info: each time the device restarts after trying all of that (manual restart of me turning it off and on), it goes to the blue Software Update screen and gives "err: 0x1111004". Once again, help is greatly appreciated. Thanks in advance.
KlausWillSeeYouNow said:
Additional info: each time the device restarts after trying all of that (manual restart of me turning it off and on), it goes to the blue Software Update screen and gives "err: 0x1111004". Once again, help is greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
If I remember right, "err: 0x1111004" means that something in the system filesystem has been modified, so when the FOTA program goes to verify the status of all of the files it wants to update, it finds a mismatch between what it expects and what is actually there. Since many of the files are updated with diffs, it can't patch the file if it has been changed from what it was expecting to find. I had trouble with this when I modified my HotspotProvision.apk to enable tethering.
And now reading what you said again, I'm pretty sure the problem is simpler than that. The patch provided is only from 12B to 23A. If you're currently on 10B, you'll have to upgrade up to 12B first before applying the 23A patch. I'll edit the main post to clarify that, sorry for not doing so earlier. I did just check and didn't see any direct patches from 10B available, unfortunately. If you need the OTA patches for 10B to 11C and then 11C to 12B, I can get those for you as files that you can then just apply manually.
I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.
The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.
I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1
I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.
I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.
Is there anything else I can try ??
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.
What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.
Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
y2whisper said:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Click to expand...
Click to collapse
From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens
Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
kurtis.austin2 said:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Click to expand...
Click to collapse
the.teejster said:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
Click to expand...
Click to collapse
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
adstro said:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
Click to expand...
Click to collapse
the.teejster said:
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
Click to expand...
Click to collapse
Have you seen any evidence of this unicorn? Just curious...
Reported on the official Google+ page :
https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T
But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
cam30era said:
Have you seen any evidence of this unicorn? Just curious...
Click to expand...
Click to collapse
FWIW.
I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.
I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous
When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.
All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).
Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)
My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have
47e96f7e7daa360947b456eca9dc5a8e45573b30
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
How do I do this? Need adb from a computer?
kurtis.austin2 said:
How do I do this? Need adb from a computer?
Click to expand...
Click to collapse
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
cam30era said:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Thank you ? very kind of you
kurtis.austin2 said:
Thank you ? very kind of you
Click to expand...
Click to collapse
Welcome
Please read the OP.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
I unlocked the bootloader and installed TWRP, but have not rooted. I have the OTA install of Android 11. I keep getting this message on my phone. At least once a day!
"Package verification failed - the update package being downloaded is not compatible with the current software version on the device"
Please, someone help me to disable this message. It is driving me nuts. Also I don't know if it is wasting bandwidth downloading an update that it isn't able to install.
Did you change firmware regions?
No, I don't even know how to do that, and I doubt such a thing could be done accidentally by unlocking the bootloader and installing TWRP.
Ok, I see now there is an option in Settings called "System Updates", within which one can disable automatic downloading of new updates. I disabled it so we'll see if I stop seeing the annoying message. Though I'm almost certain that this will work. Yes I know I'm a moron for not having found this obvious setting sooner. Oh well, I hope this post will help other folks out there.
Is there any solution to this. I get the notification daily despite disabling the Settings/System Updates?
boltjuice said:
Is there any solution to this. I get the notification daily despite disabling the Settings/System Updates?
Click to expand...
Click to collapse
I ultimately had to root the device and then install the De-Bloater app. Nothing but rooting ever worked.
danahata said:
I unlocked the bootloader and installed TWRP, but have not rooted. I have the OTA install of Android 11. I keep getting this message on my phone. At least once a day!
"Package verification failed - the update package being downloaded is not compatible with the current software version on the device"
Please, someone help me to disable this message. It is driving me nuts. Also I don't know if it is wasting bandwidth downloading an update that it isn't able to install.
Click to expand...
Click to collapse
Its suppose to fail, if its a signature verification, just make sure you have the exact files needed, see if your device is 64arm or 64 etc I had the same problem before fully educating myself with the whole process, let me know if this helps. Do a factory reset fully, redo every step and apply the ota package then apply any other packages like gapps etc but if you're doing a gapps install do it immediately after the lineage ota. With all this being said I hope you've already booted into the lineage recovery' failure to do so will result as an unsuccessful attempt
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.