Apparently there is a new update out there.
http://www.androidpolice.com/2015/0...2-update-starts-rolling-google-fit-fixes-tow/
Apoplectic1 said:
Apparently there is a new update out there.
http://www.androidpolice.com/2015/0...2-update-starts-rolling-google-fit-fixes-tow/
Click to expand...
Click to collapse
Yeah I don't want to update. I wish there was a way on Gomer 2.3 I could dismiss it permanently.
alansupra94 said:
Yeah I don't want to update. I wish there was a way on Gomer 2.3 I could dismiss it permanently.
Click to expand...
Click to collapse
I do, but that's because I've been having a lot of bugs lately, from apps force closing upon opening to the watch just plain not wanting to show any notifications.
Unfortunately, since I'm rooted any attempt at updating will abort.
Oh I mean I have the update downloaded and it keeps saying "system update" and I just want it to go away but I don't see a way to remove it.
alansupra94 said:
Oh I mean I have the update downloaded and it keeps saying "system update" and I just want it to go away but I don't see a way to remove it.
Click to expand...
Click to collapse
If you know the path to the OTA file you could delete it from your system through adb and the notification should go away.
I have no idea what that path is though. I've got a post on Q&A asking for where it might be, I'll let you know when I find out.
Apoplectic1 said:
If you know the path to the OTA file you could delete it from your system through adb and the notification should go away.
I have no idea what that path is though. I've got a post on Q&A asking for where it might be, I'll let you know when I find out.
Click to expand...
Click to collapse
Once the OTA is downloaded and Android prompts to install it should be stored in '/cache'.
Actually i tried installing even though im rooted and my installation was aborted. How can i make it appear again? (I will try go back to stock for a moment from Gohma and after update, flash Gohma again). In "system updates" it's now showing "up to date" but of course it wasnt updated
Lasiu said:
Actually i tried installing even though im rooted and my installation was aborted. How can i make it appear again? (I will try go back to stock for a moment from Gohma and after update, flash Gohma again). In "system updates" it's now showing "up to date" but of course it wasnt updated
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58963155&postcount=175
You can adb push it to /cache/, but it will only fail again if you have rooted it.
There are a few guys playing around with the update to see if they can get it to flash, and some trying to see if they can make a bash file to take your watch back to stock in order to take the OTA.
Lasiu said:
Actually i tried installing even though im rooted and my installation was aborted. How can i make it appear again? (I will try go back to stock for a moment from Gohma and after update, flash Gohma again). In "system updates" it's now showing "up to date" but of course it wasnt updated
Click to expand...
Click to collapse
At this point even going back to "stock" will NOT work as the "stock" image has been pre-rooted which breaks the OTA update files. We are all currently waiting for the amazing XDA developers for updated roms / OTA fix capabilities. Until released, even if you have reverted back to "stock" and locked the bootloader etc. if you get the notification it will FAIL to install.
Moguledyouth said:
At this point even going back to "stock" will NOT work as the "stock" image has been pre-rooted which breaks the OTA update files. We are all currently waiting for the amazing XDA developers for updated roms / OTA fix capabilities. Until released, even if you have reverted back to "stock" and locked the bootloader etc. if you get the notification it will FAIL to install.
Click to expand...
Click to collapse
What I meant by going back to stock was by flashing a completely stock image to the watch, not the return to stock option in the LG G Watch Toolkit.
I think I read that Tomsgt is working on a tool that will completely reimage the watch in order to take the OTA.
Here it is: http://forum.xda-developers.com/showpost.php?p=58967268&postcount=257
Apoplectic1 said:
http://forum.xda-developers.com/showpost.php?p=58963155&postcount=175
You can adb push it to /cache/, but it will only fail again if you have rooted it.
There are a few guys playing around with the update to see if they can get it to flash, and some trying to see if they can make a bash file to take your watch back to stock in order to take the OTA.
Click to expand...
Click to collapse
I wanted to go back to stock and install it and then flash Gohma again but i see, that its pointless I have to wait... Actually im REALLY hyped for these improvements. The only thing i hated about 5.0 release were crashes and bugs
Lasiu said:
I wanted to go back to stock and install it and then flash Gohma again but i see, that its pointless I have to wait... Actually im REALLY hyped for these improvements. The only thing i hated about 5.0 release were crashes and bugs
Click to expand...
Click to collapse
You and me both brother.
Apoplectic1 said:
You and me both brother.
Click to expand...
Click to collapse
It seems i wasnt alone with that Most annoying thing was "android wear is not responding. Do you want to close it?" Hell yeah i want to close system, maybe even delete it, huh google? xD
Lasiu said:
It seems i wasnt alone with that Most annoying thing was "android wear is not responding. Do you want to close it?" Hell yeah i want to close system, maybe even delete it, huh google? xD
Click to expand...
Click to collapse
I never had that, mainly just having to try two or three times to open settings because it would always force close a split second after opening, every now and then it's go full retard and tell me that I had to open the Maps app on my phone to use Navigation (REALLY annoying if you're driving), and it would randomly stop getting notifications for no reason until I rebooted it.
Apoplectic1 said:
I never had that, mainly just having to try two or three times to open settings because it would always force close a split second after opening, every now and then it's go full retard and tell me that I had to open the Maps app on my phone to use Navigation (REALLY annoying if you're driving), and it would randomly stop getting notifications for no reason until I rebooted it.
Click to expand...
Click to collapse
It seems that you even experienced worse bugs than I did I hope that this update will fix everything!
Wife's moto 360 updated yesterday but my LG still no update
Got the update but not sure if I want to revert to stock to install it. Anyone varify what it fixes?
Just by the way, considerating that i have no problem with reseting my watch data. What should i do to take this update? Go back to stock? Relock bootloader? Then take ota, and then unlock bootloader and flash gohma again? Or there is no point in this cuz gohma is not 5.0.2 compatible? (though somewhere on rootwiki dev stated that it should work anyway, but also there was statement that ota shouldnt fail, so now im not sure if i can believe in this part xd)
---------- Post added at 12:40 PM ---------- Previous post was at 11:51 AM ----------
Is it possible to flash this ota through TWRP?
Lasiu said:
Just by the way, considerating that i have no problem with reseting my watch data. What should i do to take this update? Go back to stock? Relock bootloader? Then take ota, and then unlock bootloader and flash gohma again? Or there is no point in this cuz gohma is not 5.0.2 compatible? (though somewhere on rootwiki dev stated that it should work anyway, but also there was statement that ota shouldnt fail, so now im not sure if i can believe in this part xd)
---------- Post added at 12:40 PM ---------- Previous post was at 11:51 AM ----------
Is it possible to flash this ota through TWRP?
Click to expand...
Click to collapse
I was trying to figure this out as well. I'd even be OK if I could disable the notification for the update. I'm on an unlocked bootloader and Arter97's kernel, no custom ROM. Seems as though this device is suffering from a lack of devs or or a lack or interest or probably both.
altivoid said:
I was trying to figure this out as well. I'd even be OK if I could disable the notification for the update. I'm on an unlocked bootloader and Arter97's kernel, no custom ROM. Seems as though this device is suffering from a lack of devs or or a lack or interest or probably both.
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/moto-360/development/rom-gohma-2-3-1-11-2015-t2999582/page15
Or this:
"It took me a while to figure out how to edit build.prop to stop the OTA notifications, so I thought I would tell you what worked for me.
adb kill-server
adb start-server
adb pull /system/build.prop build.prop
I then edited the build.prop file and did 2 global replacements:
5.0.1 --> 5.0.2
LWX48P --> LWX49L
a diff between the old a new version gave:
# diff build.prop build.prop.ORG
4c4
< ro.build.id=LWX49L
---
> ro.build.id=LWX48P
10c10
< ro.build.version.release=5.0.2
---
> ro.build.version.release=5.0.1
35,36c35,36
< ro.build.description=platina-user 5.0.2 LWX49L 1627902 release-keys
< ro.build.fingerprint=lge/platina/dory:5.0.2/LWX49L/1627902:user/release-keys
---
> ro.build.description=platina-user 5.0.1 LWX48P 1627902 release-keys
> ro.build.fingerprint=lge/platina/dory:5.0.1/LWX48P/1627902:user/release-keys
Finally, I moved the new files to the watch:
adb push build.prop /sdcard/build.prop
adb push build.prop.ORG /sdcard/build.prop.ORG
adb shell
su
mount -o rw,remount /system
cp /sdcard/build.prop* /system/
exit
exit
adb reboot
This seems to be working for me."
Second one is by haltriumph from rootzwiki (Y) Didnt try them. Decided to go to 5.0.2 and just run script for longer vibrations But it might help you.
Related
I rooted and installed StarBurst 11.13.11 v1.9.8r
Since then I've been unable to run the Android update. It starts to install then i get an icon of the little android guy and a exclamation mark. Then it's dead until I restart.
Any idea what's wrong?
You're in the wrong forums, since I presume you mean this: http://forum.xda-developers.com/showthread.php?t=1276320 (this is the I9100 forums).
Anyway, I don't know why you'd be surprised that you can't use OTA update if you're on a custom ROM.
bopritchard said:
I rooted and installed StarBurst 11.13.11 v1.9.8r
Since then I've been unable to run the Android update. It starts to install then i get an icon of the little android guy and a exclamation mark. Then it's dead until I restart.
Any idea what's wrong?
Click to expand...
Click to collapse
Yeah. What he said about the forum stuff and other stuff.
And in flashing a custom ROM, it should be implied that Android won't update itself anymore.
By flashing a ROM, you're kinda telling the Android system, "It's cool. I've got the whole ROM thing under control. You just go ahead and take some time off".
oh...ok...thanks, i guess i didn't understand that when i did it...
is there a way to stop the automatic android updates?
bopritchard said:
oh...ok...thanks, i guess i didn't understand that when i did it...
is there a way to stop the automatic android updates?
Click to expand...
Click to collapse
No worries. I'm on an ICS build now, so it might be slightly different in Gingerbread, but it's gonna be something like:
Settings -> About phone -> Software update -> uncheck the box labelled something like "update automatically"
bopritchard said:
oh...ok...thanks, i guess i didn't understand that when i did it...
is there a way to stop the automatic android updates?
Click to expand...
Click to collapse
If you have a custom ROM then your OTA automatic updates shouldnt even connect to start with.They should be completely dead and disconnected so Im not sure why it even starts the proccess.If you are rooted then use Titanium Backup to freeze it and that will take care of it.
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
Hey guys, I have an unlocked Nexus 9 and updating to 5.1 OTA isn't possible (as most of you probably already know). I have no idea what I am doing and only unlocked it because RootJunky had some automated program that basically did it for me. Now I'm stuck trying to figure out how to update manually...
My simple question is how do I revert back to a version (locked?) that will allow me to update via OTA and not have to deal with this going forward? Idiot-proof responses are most welcome.
what version of android to you currently have installed? is it 5.0.1 or 5.0.2? also, i'm guessing the reason it's not updating is because you have a custom recovery installed. if you flash the stock recovery again it should be able to update. i could help you out with that but it's a bit of a long process for a beginner haha. you can check by booting into fastboot by pressing and holding power + volume down while it's shut down until the fastboot screen shows, then scroll down to recovery with the volume keys and click on it with the power key. if you have twrp or something installed it'll show a splash screen then give you a gui but if it's the stock recovery it'll be an android mascot laying down with a warning sign above it.
octagonPerfectionist said:
what version of android to you currently have installed? is it 5.0.1 or 5.0.2? also, i'm guessing the reason it's not updating is because you have a custom recovery installed. if you flash the stock recovery again it should be able to update. i could help you out with that but it's a bit of a long process for a beginner haha. you can check by booting into fastboot by pressing and holding power + volume down while it's shut down until the fastboot screen shows, then scroll down to recovery with the volume keys and click on it with the power key. if you have twrp or something installed it'll show a splash screen then give you a gui but if it's the stock recovery it'll be an android mascot laying down with a warning sign above it.
Click to expand...
Click to collapse
It's 5.0.2. I have stock recovery and already tried the option "wipe data/factor reset" which still doesn't allow for me to update OTA.
What should I try next?
livinginavacuum said:
It's 5.0.2. I have stock recovery and already tried the option "wipe data/factor reset" which still doesn't allow for me to update OTA.
What should I try next?
Click to expand...
Click to collapse
well the OTA is currently rolling out in stages so most people won't be getting it quite yet the normal way. if you wanted it sooner, you could try sideloading it. it's a bit of a pain but it works just as well as just waiting for the OTA to show up by itself. lemme just copy & paste something i typed out the other day in another thread:
download this: https://android.googleapis.com/packa...L.5cb0c625.zip
install ADB: https://developer.android.com/sdk/index.html (scroll down and download SDK tools only)
and sideload it by following these instructions: http://www.androidcentral.com/how-ma...r-nexus#slide2
note that these instructions were assuming you are on a mac, instead of doing a ./fastboot or ./adb command just type fastboot or adb, no need for the ./
also, you're sideloading the OTA, not flashing the factory image so don't unlock the bootloader and skip the part that talks about flashing the factory images. also iirc once you see the recovery screen with the error looking message, you should press volume-up first then power to bring up the menu? i remember running into a bit of a snag there when i did this last since it says to do it the other way around. anyway hopefully this will update it. if not, you're probably gonna have to flash the factory images, which would need an unlocked bootloader. SO, in case if you do need to unlock the bootloader (which will wipe the device), be absolutely sure to flip that little switch in developer options that allows OEM unlock, otherwise you might be left with a bricked device.
Click to expand...
Click to collapse
you could also flash the factory image but this way is honestly a bit easier and gives the same result. i've never been able to get the .bat file to actually automate it properly before haha
livinginavacuum said:
Hey guys, I have an unlocked Nexus 9 and updating to 5.1 OTA isn't possible (as most of you probably already know). I have no idea what I am doing and only unlocked it because RootJunky had some automated program that basically did it for me. Now I'm stuck trying to figure out how to update manually...
My simple question is how do I revert back to a version (locked?) that will allow me to update via OTA and not have to deal with this going forward? Idiot-proof responses are most welcome.
Click to expand...
Click to collapse
You don't need to ota to update.
Read the instructions here;
https://developers.google.com/android/nexus/images
octagonPerfectionist said:
well the OTA is currently rolling out in stages so most people won't be getting it quite yet the normal way. if you wanted it sooner, you could try sideloading it. it's a bit of a pain but it works just as well as just waiting for the OTA to show up by itself. lemme just copy & paste something i typed out the other day in another thread:
you could also flash the factory image but this way is honestly a bit easier and gives the same result. i've never been able to get the .bat file to actually automate it properly before haha
Click to expand...
Click to collapse
Your first and third link don't seem to work.
doitright said:
You don't need to ota to update.
Read the instructions here;
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Easier said than done for someone who has no clue. Is there a good youtube video?
livinginavacuum said:
Your first and third link don't seem to work.
Click to expand...
Click to collapse
sorry about that, here's the first link again. the forum must have truncated it because it was too long: https://goo.gl/CkF7J6
here's the third one with a link shortener too, for some reason the forum won't let me post the long version: http://goo.gl/XevxkJ
octagonPerfectionist said:
sorry about that, here's the first link again. the forum must have truncated it because it was too long: https://goo.gl/CkF7J6
here's the third one with a link shortener too, for some reason the forum won't let me post the long version: http://goo.gl/XevxkJ
Click to expand...
Click to collapse
First one doesn't work! LOL. I'm sure it's not you.
livinginavacuum said:
First one doesn't work! LOL. I'm sure it's not you.
Click to expand...
Click to collapse
haha fml apparently google doesn't like links to the ota zip well anyway just google "nexus 9 ota zip" and it's pretty easy to find.
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/