Related
Downloaded the New OTA, I get this error
assert failed: apply_patch_check("/system/build.prop", "5c3f9a4d69509d2c8b88850d2a333ae7df255a", "c566a4739016d30834e2ae57784e81c7dbdd6ce9")
E:Error in /cache/Blur_Version.45.2.7.MB855.Sprint.en.US.zip
(status 7)
update: Problem not resolved, found a workaround See post #2
DID a hard reset though Android Recovery, and then tried to download the NEW OTA, and during installation got the same error. I am currently on 4.2.7 build 154_6
Right Now trying to RSD 4.3.6, will update
Update: Flashing Build 4.3.6 through RSD failed, I get the screen filled with noise
Update: Flashing 154_5 with RSD Success
system downloaded 4.2.7 OTA, and then Download 4.3.6, all works
BUT it blows i had to do all this.....could Bootstrap recovery be blamed??? i have another photon, that was rooted that same way as this but that one had no bootstrap recovery and the OTA went fine
update: http://www.uploadhere.com/UPPUJTGZNO if people need the 154_5 full SBF
same here, update fails. stock rooted
Download it and as soon as it starts to install, press Volume up AND down, it will tell you whats going on, i had to go all the way back to 154_5 to get it going, hard reset did not work
Do you have bootstrap installed and if so, ever restored a backup?
no bootstrap, just rooted
well try pressing volume up and down and lets see what the error is, sometimes it can be resolved.
assert failed: apply_patch_check("/system/appaccountandsyncsettings.apk", "96a3dd49051c5b6cf5e31fd080d2f1398157f02c", "485f9b3476f156630d72fcc1564737f2029a40")
E:Error in /cache/Blur_Version.45.2.7.MB855.Sprint.en.US.zip
(status 7)
installation aborted
I also am just 1 click rooted, during the update it starts and soon goes into the exclamation mark. I don't know what the bootstrap is; I just one click rooted. I have tried to update twice now with no luck...
Harry_Spade said:
Downloaded the New OTA, I get this error
assert failed: apply_patch_check("/system/build.prop", "5c3f9a4d69509d2c8b88850d2a333ae7df255a", "c566a4739016d30834e2ae57784e81c7dbdd6ce9")
E:Error in /cache/Blur_Version.45.2.7.MB855.Sprint.en.US.zip
(status 7)
update: Problem not resolved, found a workaround See post #2
Click to expand...
Click to collapse
That means that the build.prop has been modified and does not match what the installer is expecting (hash wise). Should be easily fixed by switching in build.prop from the stock sbf.
I forgot to mention that besides having OCR I have the modified webtop dock software to run from an HDMI cable. Would that be my issue in updating? Is there any way to get the original files (it was really dumb but i just went ahead and deleted them and didnt save them elsewhere before)
samcrac said:
I forgot to mention that besides having OCR I have the modified webtop dock software to run from an HDMI cable. Would that be my issue in updating? Is there any way to get the original files (it was really dumb but i just went ahead and deleted them and didnt save them elsewhere before)
Click to expand...
Click to collapse
Download stock sbf of the version you have. Switch in files that fail hash check with adb or root explorer.
After clicking "Download" button process doesn't start visually but if I trying to check update again I get the message "An update is currently being downloaded. You will be notified when the download is complete". Wipe is done. All stock apps are available. Nothing happens, the update is hanging somewhere in the background. What should I do?
Joutes said:
After clicking "Download" button process doesn't start visually but if I trying to check update again I get the message "An update is currently being downloaded. You will be notified when the download is complete". Wipe is done. All stock apps are available. Nothing happens, the update is hanging somewhere in the background. What should I do?
Click to expand...
Click to collapse
same here....
---------- Post added at 10:59 AM ---------- Previous post was at 10:55 AM ----------
update... mine is downloading now. There is a progress bar in notifications now. I guess just wait it out and maybe it will "unstick" for you
hold your horses and wait for the download to finish.
MultiDev said:
That means that the build.prop has been modified and does not match what the installer is expecting (hash wise). Should be easily fixed by switching in build.prop from the stock sbf.
Click to expand...
Click to collapse
I tried that, I did modify my build.prop and I had backed up my original one, I also did a hard reset and still got the same error, untill i had to RSD flash 154_5. Question though, How do you extract a build.prop file from a sbf, what do you use to do it?
Nullinvoid said:
hold your horses and wait for the download to finish.
Click to expand...
Click to collapse
I have waited now for 17 hours , Nothing Happens ,
But its sucking my battery , I have to keep the 3G data on all the time ,
how to cancel it , There's nothing I can do about it , it just really annoys me in the notification bar .,
Saran from india
sarandepp said:
I have waited now for 17 hours , Nothing Happens ,
But its sucking my battery , I have to keep the 3G data on all the time ,
how to cancel it , There's nothing I can do about it , it just really annoys me in the notification bar .,
Saran from india
Click to expand...
Click to collapse
reboot and see if it helps, or connect to wifi
I also am not able to update to the new OTA.
I receive the following error message:
assert failed: apply_patch_check("/system/app/SprintOMADMConnMoPlugin.apk", "looongstring1", "loongstring2")
I deleted the .apk file to stop Sprint searching for network at the beginning. I guess that is the reason why its not letting me update. Is there anywhere I can find this file from? Does Sprint/Motorola provide it? Am I screwed?
ROOTING is not the Problem, my other photon had the OCR and updated fine, some of the APKs are getting modified, if nothing goes the last resort might be what i had to do.
Anyone can please provide the methods to extract specific files from sbf, that might help, the SBF would have to be from the current file system as your phone.
I agree. Even in my case, I have deleted an apk which is causing this. Need to find a way to get the apk back or else the previous update is going to be my last
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Ste_J said:
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Click to expand...
Click to collapse
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Floralina123 said:
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Click to expand...
Click to collapse
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Ste_J said:
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Click to expand...
Click to collapse
Hi Ste_j, thanks for the reply. I unrooted it already, or so I thought using nabilabs but it looks like twrp was removed and gapps remains - which I'm happy about seeing as I can't update it using ota update with google playstore- that could have been a disaster.
Here is my question I posted -
I Apologise for my ignorance in android in general.
I have rooted a Nabi 2 successfully installing Gapps etc using Nabilab, which was a pleasure to use. Now that the new OTA update is available which includes the Googleplaystore I would like to unroot and get the OTA updates. I thought I had unrooted it - using Nabilabs (twrp would not work, can't remember why but I think the touchscreen part wouldn't work for me). I returned to stock using (option 1. -1.9.37. Android can boot.) recovery using Nabilabs. I think I did a factory reset after that -sorry but it was weeks ago. Anyway, I suspected something wasn't right when I still had Gapps. I don't have TWRP on it now.
When I do the OTA update I get the dead android on reboot. Nabi is working fine apart from that. I read a lot of pages on this website but it ended up confusing me more than helping me unfortunately as I'm not android savvy.
I just need someone to tell me exactly what to do to properly unroot the Nabi so that it is truly back to original so I can use the OTA updates. I have no need to root the nabi again as the google play store is now officially available. And I've got a UK Nabi 2.
Ste_j,
I assumed I had a Uk nabi because I'm in Ireland. I don't know how to check this as it doesn't say uk here but the
model no is NABI2-NV7A-IE
Android version 4.0.4
Kernel version 3.1.10-00298-ge08b99f
[email protected] #2
SMP PREEMPT Tue Feb 26 17:21:35 HKT 2013
Build no IMM76L
Product version: 2.0-release-keys
I don't want to unroot any further unless I can get the latest ota update that gives me the google play store. I would rather leave it as it is now(gapps still on it) until you get yours working successfully I will gladly follow your lead from start to finish then. I just hope someone in the know replies with the solution. I too had been reading the nabi forum but cannot post there.
Tnx
Sounds like one of my recent 1am going on for 2 adventures in nabi land!
Hopefully there will be a UK stock 2.2 being uploaded tonight and if I get it working then I will let you know.
Ste_J said:
Sounds like one of my recent 1am going on for 2 adventures in nabi land!
Hopefully there will be a UK stock 2.2 being uploaded tonight and if I get it working then I will let you know.
Click to expand...
Click to collapse
Did you ever sort this one out mate? If I can atleast get my hands on the 2.2 OTA update zip file then atleast I can force it to upgrade from recovery mode.
metalheadkicks said:
Did you ever sort this one out mate? If I can atleast get my hands on the 2.2 OTA update zip file then atleast I can force it to upgrade from recovery mode.
Click to expand...
Click to collapse
Not yet. Waiting on 2.2 to be uploaded on the other thread. Hopefully the guy will get chance to upload over the weekend
So all 3 of you have UK Nabi's that can't get to 2.2 and are stuck somewhere at 2.0 or 2.1? Is that correct?
In theory restoring either of these(2.0 stock or 2.1 stock) http://forum.xda-developers.com/showpost.php?p=50158865&postcount=67
should then allow you to take the OTA. The US version did it as a 2 part update and the first wiped the system partition and installed a base ROM which got everyone on the same page and the did the second update to 2.3(2.2 for you guys if I understand correctly). Maybe the UK version doesn't do it like that.
Where is everyone failing at? TWRP usually fails for a "assert error in some file" If the backups are truly stock then this should work fine. Sometimes people who make backups mess up and TWRP set the file recovery-from-boot.p to recovery-from-boot.bak then the update can find that file and errors. Any other files will cause the same issue. Some other issues are the addon partition, the OTA's do edit stuff on the addon partition, if you have skipped around OTA's this can cause a mismatch too.
A stock 2.2 ROM would be great but anyone on 2.1 would still be stuck with ICS bootloader which won't boot 2.2UK. You would also want an addon partion backup to restore too.
Oops I get it.. You guys don't know where you are failing at because the stock recovery(dead android) doesn't give you any info. TWRP 2.6.3 can install OTA updates. Put TWRP backon. Use it to install the OTA it will have a log that will say why it's failing.
aicjofs said:
So all 3 of you have UK Nabi's that can't get to 2.2 and are stuck somewhere at 2.0 or 2.1? Is that correct?
In theory restoring either of these(2.0 stock or 2.1 stock) http://forum.xda-developers.com/showpost.php?p=50158865&postcount=67
should then allow you to take the OTA. The US version did it as a 2 part update and the first wiped the system partition and installed a base ROM which got everyone on the same page and the did the second update to 2.3(2.2 for you guys if I understand correctly). Maybe the UK version doesn't do it like that.
Where is everyone failing at? TWRP usually fails for a "assert error in some file" If the backups are truly stock then this should work fine. Sometimes people who make backups mess up and TWRP set the file recovery-from-boot.p to recovery-from-boot.bak then the update can find that file and errors. Any other files will cause the same issue. Some other issues are the addon partition, the OTA's do edit stuff on the addon partition, if you have skipped around OTA's this can cause a mismatch too.
A stock 2.2 ROM would be great but anyone on 2.1 would still be stuck with ICS bootloader which won't boot 2.2UK. You would also want an addon partion backup to restore too.
Oops I get it.. You guys don't know where you are failing at because the stock recovery(dead android) doesn't give you any info. TWRP 2.6.3 can install OTA updates. Put TWRP backon. Use it to install the OTA it will have a log that will say why it's failing.
Click to expand...
Click to collapse
Thank you. I have restored 2.0 from that post
Am I correct in thinking that the OTA will be stored in internal memory and that TWRP should be able to locate the file? Is there anyway of repairing the addon partition if that is corrupt?
Ste_J said:
Thank you. I have restored 2.0 from that post
Am I correct in thinking that the OTA will be stored in internal memory and that TWRP should be able to locate the file? Is there anyway of repairing the addon partition if that is corrupt?
Click to expand...
Click to collapse
Yes the ota is stored in internal memory. On data/media(internal). Its in a folder called ota or something intuitive like that. A forum search will find it, I'm drawing a blank. Do the ota download but when it says to update, back out of settings at that point and you will have the OTA zip.
Its kind of hard to repair addon. If there was a backup of addon from an early software version you could let the otas update it properly. I didn't really think to add that ability to twrp until late in the game though. The other option is to have someone that has successfully progressed through the otas make a backup and share. Then we could cook something up where you just use a 2.2 ROM and restore, update the bootloader and restore a 2.2 add-on. The last option is a custom OTA, similar to what I did with the US Nabi, and even that hasn't went perfectly. I'm not sure if its my update or people doing it a little different then the instructions but there have been a few failures with it. Although we figure it out eventually, just like we will with the UK Nabi.
aicjofs said:
Yes the ota is stored in internal memory. On data/media(internal). Its in a folder called ota or something intuitive like that. A forum search will find it, I'm drawing a blank. Do the ota download but when it says to update, back out of settings at that point and you will have the OTA zip.
Its kind of hard to repair addon. If there was a backup of addon from an early software version you could let the otas update it properly. I didn't really think to add that ability to twrp until late in the game though. The other option is to have someone that has successfully progressed through the otas make a backup and share. Then we could cook something up where you just use a 2.2 ROM and restore, update the bootloader and restore a 2.2 add-on. The last option is a custom OTA, similar to what I did with the US Nabi, and even that hasn't went perfectly. I'm not sure if its my update or people doing it a little different then the instructions but there have been a few failures with it. Although we figure it out eventually, just like we will with the UK Nabi.
Click to expand...
Click to collapse
TWRP installed and OTA attempted. log file attached . still not sure what is going wrong but hopefully somebody who is used to reading the logs will point me in the right direction
Ste_J said:
TWRP installed and OTA attempted. log file attached . still not sure what is going wrong but hopefully somebody who is used to reading the logs will point me in the right direction
Click to expand...
Click to collapse
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
aicjofs said:
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
Click to expand...
Click to collapse
That was going from 2.1 to 2.2
And yes i appear to be cross threading at the moment. Grabbed the 2.2 update and just spent the last hour trying to get past the stuck nabi screen. Got back to 2.1 eventually. Fastboot and Nabilab with just enough time to fire over previous TWRP and get back to the restore
Any ideas on how to update the boot loader?
Moving back to the other thread http://forum.xda-developers.com/showthread.php?t=2041224&page=9
aicjofs said:
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
Click to expand...
Click to collapse
I get this issue also. I had rooted and added Google services - happy enough but no ability to move Apps to SD and I wanted to see if the Kernel update added this option. Anyway, I restored my backup - but the updates didn't apply cleanly. I swapped the boot loader back and things still weren't right and I didn't know then how to troubleshoot it. I was tired/had a wailing 3 year old wanting his tablet and I elected to wipe and reinstall from scratch using NabiLabFull. Initialised well enough through initial setup - completed setup and changed the recovery back to stock and it boot looped... Ugh. Reapplied stock image through twrp and changed to recovery back immediately - setup the Nabi from scratch and update 2.1 applied successfully. Update 2.2 fails however using stock everything with the error message:
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
Verifying current system. . ,
assert failed: apply_patch_check("/system/vendor/app/fuhu_nabiMD_uk.apk", "c4cd5edbc3f980c806a4fb8dd1d182f5c81b35f3", " eea145bf7f4a7b314ef15a3f3b0b9e8a9bc6efe7")
E:Error in /cache/nabi2-update.zip
(Status 7)
Installation aborted
So. The presence of two, what appear to be, md5 hash values makes me think the app in the system partition is not what it should be. Absent a file manager and root access I haven't delved deeper but I can only think the stock image I loaded isn't close enough to the UK stock image such that the UK specific apps correctly update in the 2.1 update (NabiMD is no longer installed after applying the 2.1 patch - dead link launcher icon on Parent home screen). My problem is I forgot to copy the pre-rooted backup before wiping - so I might have lost it. Anyway. Need to go shopping now and I'll dig more later. Long story short - I'm not sure a stock root path via NabiLab is viable for UK Nabi 2s.
Uk nabi update - leaving nabi as is until it's solved
I'm sorry this is not helpful but I just wanted to say that until the uk nabi is restored successfully and can update normally using ota, I'm leaving mine as it is. Basically, it works fine and my 4 yr old gets endless fun out of it. In saying that, I will restore it to normal someday when it can be done. I await one of you smart nabi gurus to come up with the answer.
MattP79 said:
I get this issue also. I had rooted and added Google services - happy enough but no ability to move Apps to SD and I wanted to see if the Kernel update added this option. Anyway, I restored my backup - but the updates didn't apply cleanly. I swapped the boot loader back and things still weren't right and I didn't know then how to troubleshoot it. I was tired/had a wailing 3 year old wanting his tablet and I elected to wipe and reinstall from scratch using NabiLabFull. Initialised well enough through initial setup - completed setup and changed the recovery back to stock and it boot looped... Ugh. Reapplied stock image through twrp and changed to recovery back immediately - setup the Nabi from scratch and update 2.1 applied successfully. Update 2.2 fails however using stock everything with the error message:
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
Verifying current system. . ,
assert failed: apply_patch_check("/system/vendor/app/fuhu_nabiMD_uk.apk", "c4cd5edbc3f980c806a4fb8dd1d182f5c81b35f3", " eea145bf7f4a7b314ef15a3f3b0b9e8a9bc6efe7")
E:Error in /cache/nabi2-update.zip
(Status 7)
Installation aborted
So. The presence of two, what appear to be, md5 hash values makes me think the app in the system partition is not what it should be. Absent a file manager and root access I haven't delved deeper but I can only think the stock image I loaded isn't close enough to the UK stock image such that the UK specific apps correctly update in the 2.1 update (NabiMD is no longer installed after applying the 2.1 patch - dead link launcher icon on Parent home screen). My problem is I forgot to copy the pre-rooted backup before wiping - so I might have lost it. Anyway. Need to go shopping now and I'll dig more later. Long story short - I'm not sure a stock root path via NabiLab is viable for UK Nabi 2s.
Click to expand...
Click to collapse
Floralina123 said:
I'm sorry this is not helpful but I just wanted to say that until the uk nabi is restored successfully and can update normally using ota, I'm leaving mine as it is. Basically, it works fine and my 4 yr old gets endless fun out of it. In saying that, I will restore it to normal someday when it can be done. I await one of you smart nabi gurus to come up with the answer.
Click to expand...
Click to collapse
Have you tried this? http://forum.xda-developers.com/showpost.php?p=50431606&postcount=98
It has to be done manually but should get a UK Nabi to complete stock version 2.2.
In case you need to know for some reason in the future that is a SHA1 hash not md5.
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.
YOU CAN FIND THE FULL G930AUCU8CSA3 FIRMWARE HERE:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871
G930AUCU4CRE4 to G930AUCS4CRG5:
Download link: https://drive.google.com/file/d/1MoJ0be2exLMoji2ZURR6tbEiHCqWSszG/view
G930AUCS4CRG5 to G930AUCU4CRI2:
Download link: https://drive.google.com/file/d/1Fdrcy4m49Qtl-__dUE0Etuqmyn8UhYbe/view
G930AUCU4CRI2 to G930AUCS8CRJ2
Download link: https://drive.google.com/file/d/1bhVx5Rt_CTXmG5YQrY5azS10RO3lWj1r/view
G930AUCS8CRJ2 to G930AUCS8CRK1
Download link: https://drive.google.com/file/d/1lepPXVZIiZM4i_VMOUOvDvVHvGY4ifwv/view
G930AUCS8CRK1 to G930AUCS8CRL1
Download link: https://drive.google.com/file/d/1CUJOVWnDsk3LL378vxLO0vp8y3AdQjmr/view
If i helped you don't forget to hit thanks button
G930aucu4cri2
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Juliowwwe said:
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Click to expand...
Click to collapse
Link is UP
thank you very much
thank you very much
New October update is UP
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
lahlah said:
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
Click to expand...
Click to collapse
1.) Turn off the phone. Hold down Volume Up + Home + Power until you see a little Android guy. It will say Applying System Update or something like that possibly, and just let it do it's thing until a menu comes up.
2.) Select "Apply update from ADB". You can scroll using the volume buttons and select using the power button.
3.) Make sure you have ADB and the proper drivers installed on your PC:
http://dl.adbdriver.com/upload/adbdriver.zip
4.)Put the firmware in the ADB folder. You can rename it to anything easy to remember like "FIRMWARE".
5.) In the ADB folder, hold SHIFT + right mouse click and choose "Open command window here". Then type the command "adb sideload FIRMWARE" (where FIRMWARE is how you named your file).
6.) Wait patiently.
7.) The phone will reboot and will hang at AT&T logo. This can take another 10 minutes, just wait until it's done
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
samhnky said:
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
Click to expand...
Click to collapse
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
stek-kravari said:
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
Click to expand...
Click to collapse
Awesome! Thank you, thank you!
I actually really like Oreo, just trying to get Oreo and WiFi calling working on my phone (My Office at work fights all day for 1 bar of cell signal), I had hoped that WiFi calling worked in the SM-G930U variant since everyone talked about it running so much better, but alas, it still doesn't support WiFi Calling (Stupid me for thinking it might have had support added recently).
Thank you again
(My Wife is sure to get upset with me once again working on my phone again today... whoops)
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
bnn0 said:
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
Click to expand...
Click to collapse
You mean about G930AUCS8CRJ2 sideload with adb? Im just pulling the update from AT&T servers and uploading it here. I don't know how to make sideload zip. And for the rooting part I don't know if its possible now because the bootloader binary was updated to 8, try to search here on xda and see if you can find root methods for this firmware
new update, check first post
----
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Maury Yarik said:
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Click to expand...
Click to collapse
First you need to install this:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871 (G930AUCS8CRJ2)
Then you need to go from G930AUCS8CRJ2 to G930AUCS8CRK1, G930AUCS8CRK1 to G930AUCS8CRL1 and you will have the latest update.
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Josh13400 said:
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Click to expand...
Click to collapse
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
stek-kravari said:
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
Click to expand...
Click to collapse
I was thinking something like that was possible. I have baseband version G930AUCU4CRB5 Android 8.0.0 on the AT&T Gal S7 as mentioned, I never saw any updates from this version to go up to a newer version or get into regular updates from OTA. 2 issues I would like to also fixed, that came with the manual update to 8.0 oreo on my phone was the HR heart rate sensor on the back by your flash(red LED) always goes off.. And have tried to go to Samsung health and do some settings to turn it off, but seems to show back up eventually. Also, the issue of not having a working LED indicator, works fine when the phone is POWERED off. and charges. But in OS, it won't work, screen off or on bc of the update. If anyone knows how those issues could be fixed and if there is a possible newer update from my baseband mentioned below. And thanks for the response.
HI, Help needed
Hi,
I wanted to check if it is possible to flash the latest Oreo firmware you have here for downloading dirrectly to my samsung s7 that is currently running on 7.0? Current BaseBand is G930AUCU4BQK2
Basically what happened was that i lost all my contacts on my phone, I ended up download Dr.Phone to my laptop, which i used to try and recover my numbers. What i didnt know was that dr.phone rooted my device which has caused me nothing but headaches.
I now want to flash my phone and get updated to oreo and have my phone working normally again. Since dr.phone did whatever it did to my phone I lost use of my finger print scanner, had to disable samsung health as it kept trying to open on its own, my phone is lagging and freezing constantly..
I just want my phone to be normal again and unrooted and updated.
Lastly my phone is an AT&T device, that i bought second hand in Dubai, if i flash stock firmware is it going to carrier lock my device to AT&T again?
Any advice and help with this matter would be greatly appreciated.
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/