[ROM][Backup]Stock LCA43 - Samsung Gear Live

[Update]
Created new backup of the latest firmware. Hopefully there won't be any problem with updating to next OTA this time. I re-flashed my own watch using this backup, so I guess we'll see.
This is the backup of the latest, at the time of writing, stock firmware.
[MEC23G] OTA update from Google.
https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
Don't really need to flash to my backup anymore since the MEC23G update comes as a full firmware, not incremental. However, if you are missing recovery or have an old recovery from gear live restore tool v2. You might need to flash recovery backup as, at least on my watch, USB is not functioning in sideload mode.
[MEC23G]Backup.
[Boot+System+Recovery]
https://dl.dropboxusercontent.com/u/36544414/Samsung Gear Live Stock/MEC23G/MEC23G.rar
[Recovery]
https://dl.dropboxusercontent.com/u/36544414/Samsung Gear Live Stock/MEC23G/recovery_MEC23G.rar
OLD backups
LCA43
[Boot+System+Recovery]
https://dl.dropboxusercontent.com/u/36544414/Samsung Gear Live Stock/LCA43.rar
[Boot Partition only]
https://dl.dropboxusercontent.com/u/36544414/Samsung Gear Live Stock/LCA43/boot_LCA43.img
[Recovery Partition only]
https://dl.dropboxusercontent.com/u/36544414/Samsung Gear Live Stock/LCA43/recovery_LCA43.img
[LDZ22J]
Link: https://dl.dropboxusercontent.com/u/36544414/Samsung Gear Live Stock/LDZ22J.zip

Have you updated to the newest LCA43? I cannot OTA your install because of libgnults_shared.so not matching.

Same problem here when I try to update to LCA43, error with "libgnustl_shared.so", has unexpected package contain something like that with Status 7...
Try to remove the patch_check from the update file but the update fail with file signature...
Any help ?

Yea, I do remember that I had some sort of problem during OTA update. I think I re-flashed back to one of the older firmware from Samsung Gear Live Restore Tool V2. And then OTAed it up to the latest.
I am not sure what corrupted the file, all I did was a full DD dump from TWRP.
TWRP used to let you flash ota updates with incorrect signatures but then it stopped working after one of the major updates. So, the only thing you can do is find the libgnustl_shared.so that has the correct checksum.
You can try to adb push a backup of a file. I only have the one from the newest firmware. I believe it simply ignores apply patch part if your file is already matching the SHA-1 checksum of the target file.
apply_patch("/system/priv-app/ClockworkHomeGoogle/lib/arm/libgnustl_shared.so",
"-", cd15c4ed848df9463eab5f9caed61005f3886f69, 714416,
c57e82c7cd7b5eedd9a37084a0641b25f2c28a85, package_extract_file("patch/system/priv-app/ClockworkHomeGoogle/lib/arm/libgnustl_shared.so.p"));
set_progress(0.664444);
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/36544414/Samsung Gear Live Stock/libgnustl_shared.so
The file needs to be placed in /system/priv-app/ClockworkHomeGoogle/lib/arm/libgnustl_shared.so.
So when you boot into TWRP, just connect via adb and then do adb push to directory above.
adb push libgnustl_shared.so /system/priv-app/ClockworkHomeGoogle/lib/arm/libgnustl_shared.so.

Still gives the same error, I don't know what's going on and I cannot physically get the OTA to work from V2, just crashes gapps and gets stuck in a loop.
aligatro2010 said:
Yea, I do remember that I had some sort of problem during OTA update. I think I re-flashed back to one of the older firmware from Samsung Gear Live Restore Tool V2. And then OTAed it up to the latest.
I am not sure what corrupted the file, all I did was a full DD dump from TWRP.
TWRP used to let you flash ota updates with incorrect signatures but then it stopped working after one of the major updates. So, the only thing you can do is find the libgnustl_shared.so that has the correct checksum.
You can try to adb push a backup of a file. I only have the one from the newest firmware. I believe it simply ignores apply patch part if your file is already matching the SHA-1 checksum of the target file.
https://dl.dropboxusercontent.com/u/36544414/Samsung Gear Live Stock/libgnustl_shared.so
The file needs to be placed in /system/priv-app/ClockworkHomeGoogle/lib/arm/libgnustl_shared.so.
So when you boot into TWRP, just connect via adb and then do adb push to directory above.
adb push libgnustl_shared.so /system/priv-app/ClockworkHomeGoogle/lib/arm/libgnustl_shared.so.
Click to expand...
Click to collapse

xorl said:
Still gives the same error, I don't know what's going on and I cannot physically get the OTA to work from V2, just crashes gapps and gets stuck in a loop.
Click to expand...
Click to collapse
Did you keep the recovery partition or flashed the one that comes with V2?

I threw on the V2 openrecovery, pushed the file. Now that I repeated the step, it's saying their is no OTA available.
aligatro2010 said:
Did you keep the recovery partition or flashed the one that comes with V2?
Click to expand...
Click to collapse

xorl said:
I threw on the V2 openrecovery, pushed the file. Now that I repeated the step, it's saying their is no OTA available.
Click to expand...
Click to collapse
Tried it one more time, threw the file on there, via twrp. Restored the V2 recovery, attempted to sideload the OTA, gets to 60% fails with the same error message '"/system/priv-app/ClockworkHomeGoogle/lib/arm/libgnustl_shared.so" has unexpected contents.'
---------- Post added at 04:10 PM ---------- Previous post was at 03:39 PM ----------
~ # ls -al /system/priv-app/ClockworkHomeGoogle/lib/arm/libgnustl_shared.so
-rw-r--r-- root root 714416 2015-10-09 20:46 libgnustl_shared.so

Try this one. This file is from LDZ22J, not LCA43 like the last time; which is what you guys need. I took it straight out of MWX49K -> LDZ22J OTA. Usually they only have patches in those updates unless they are adding new files which is probably the case here.
https://dl.dropboxusercontent.com/u/36544414/Samsung Gear Live Stock/LDZ22J/libgnustl_shared.so
cd15c4ed848df9463eab5f9caed61005f3886f69 libgnustl_shared.so
If all goes well, I'll try to replace this file in dd dump and re-upload.

Hey man your backup help me save my watch and update it to 5.1.1,but then I was just wondering if you could do the same with the new LCA43 update,because I've tried to sideloaded and take the ota but have failed on both ways!!!!!

Jairsantana said:
Hey man your backup help me save my watch and update it to 5.1.1,but then I was just wondering if you could do the same with the new LCA43 update,because I've tried to sideloaded and take the ota but have failed on both ways!!!!!
Click to expand...
Click to collapse
I created new backup of the latest firmware. Hopefully there won't be any problem with updating to next OTA this time. I re-flashed my own watch using this backup, so I guess we'll see.

aligatro2010 said:
I created new backup of the latest firmware. Hopefully there won't be any problem with updating to next OTA this time. I re-flashed my own watch using this backup, so I guess we'll see.
Click to expand...
Click to collapse
Thanks a lot for your efforts and this update!!!!

Related

[Q] OTA 5.1 Update file location?

So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip

Android wear 1.3 update

Can someone upload android wear 1.3 update.zip or the updater-script?
thank you!!
EDIT: link in second page.
not seeing the update yet on the watch.
My watch received the update, but i can't install and after edit the updater-script the watch enter in a bootloop
Anybody else receive the update?
MysteriousSparrow said:
Anybody else receive the update?
Click to expand...
Click to collapse
you will need to do a factory reset before the updatee comes tru
potaturrias said:
My watch received the update, but i can't install and after edit the updater-script the watch enter in a bootloop
Click to expand...
Click to collapse
could you post the update zip, something probably isn't flashed proparly
suljo94 said:
could you post the update zip, something probably isn't flashed proparly
Click to expand...
Click to collapse
https://mega.nz/#!EFcGxLDB!jDbphrownOlCP5Idk4Ko8L1HZegJpYHa4LZCqrTjTKg
There is something wrong with /system/bin/app_process32
Backup before install!!!!
No update either from my side.
deedii said:
No update either from my side.
Click to expand...
Click to collapse
can someone upload system/bin/app_process32??
thank you in advance.
potaturrias said:
can someone upload system/bin/app_process32??
thank you in advance.
Click to expand...
Click to collapse
If you installed SU, it could be possible that your /system/bin/app_process32 and /system/bin/install-recovery.sh have been replaced, the originals should still be on your system as /system/bin/app_process32_original and /system/bin/install-recovery_original.sh, just move them back and the update should work.
cloudrainstar said:
If you installed SU, it could be possible that your /system/bin/app_process32 and /system/bin/install-recovery.sh have been replaced, the originals should still be on your system as /system/bin/app_process32_original and /system/bin/install-recovery_original.sh, just move them back and the update should work.
Click to expand...
Click to collapse
Thank you!! i can install the zip but the watch is not updated...
Edit: I installed stock recovery but i get zip signature error. Still need an unmodified update.zip
Found:
https://android.googleapis.com/packages/ota/lge_bass_bass/8831116af47f7842164aa7ed8efde2984b355e84.signed-bass-LCA44B-from-LDZ22D.8831116a.zip
OK, I'm a little confused. I got the Android Wear 1.3 update to my phone yesterday. However when I check the version number on the watch it says Android wear 1.1.1 I just did a factory reset on the watch and checked and I still have the same 1.1.1 version. Does it take some time to transfer over to the watch?
For what its worth, I can't get the new style interactive watch faces to work. This is understandable since the watch is not using the newest version.
ozaghloul said:
OK, I'm a little confused. I got the Android Wear 1.3 update to my phone yesterday. However when I check the version number on the watch it says Android wear 1.1.1 I just did a factory reset on the watch and checked and I still have the same 1.1.1 version. Does it take some time to transfer over to the watch?
For what its worth, I can't get the new style interactive watch faces to work. This is understandable since the watch is not using the newest version.
Click to expand...
Click to collapse
flashing the file, my watch have 1.3.0.2166028
Why should I need to flash anything? I already got the update form the play store to my phone. Why isn't my phone updating my watch?
ozaghloul said:
Why should I need to flash anything? I already got the update form the play store to my phone. Why isn't my phone updating my watch?
Click to expand...
Click to collapse
The update that you installed is for android wear app, not for the watch.
Deleted for stupidity.
I got my update OTA yesterday - seems to have survived the ordeal.
Argh
I was up until 3 am trying to get my Urbane back to an unrooted, unmodified state (with the exception of OEM unlock). Using the mv command, I replaced the 2 modified files in /system/bin with their originals, and no matter what I do, the 1.3 update won't take. It starts to sideload, but then craps out during the installation, with a message that flashes by briefly that basically states that an error took place. I have checked and rechecked the firmware package (even redownloading it multiple times), but the same thing happens. I believe my device is not truly unrooted, and that there are system files from SuperSU that are preventing this from installing successfully.
Is there a foolproof way to return this watch to stock, wiping out root, and allowing the 1.3 update to take? I am at a loss here. I have tried the TWRP backup/restore as well, and the same thing happens.
Thanks in advance.
If anyone can take a TWRP backup AFTER updating to 1.3 and post it, I am sure it would help me and many others. Thanks in advance.
Could you produce a step by step of the file name change? (mv command)
Thanks in advance

Anyone know what's in the Verizon Update pushed on 4/12? OTA XT1096

I'm wondering if it's worth it. Version 23.201.2.en.us
I'm not sure, but here it is:
https://dl.dropboxusercontent.com/u/12873062/Blur_Version.23.201.2.victara_verizon.verizon.en.US.zip
Is there a way to flash this onto a rooted phone? I unlocked my XT1096 a couple of months ago and installed Teamwin then flashed SuperSU.
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
dunderball said:
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
Click to expand...
Click to collapse
To take the ota you have to reflash the full 5.1 firmware for verizon.
You can't have root nor a modified sytem for OTAs to work. So you need back all those apps you removed and get rid of root.
Sent from my XT1095 using Tapatalk
jonnythan said:
I'm not sure, but here it is:
https://dl.dropboxusercontent.com/u/12873062/Blur_Version.23.201.2.victara_verizon.verizon.en.US.zip
Is there a way to flash this onto a rooted phone? I unlocked my XT1096 a couple of months ago and installed Teamwin then flashed SuperSU.
Click to expand...
Click to collapse
dunderball said:
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
Click to expand...
Click to collapse
I've put together a debloated TWRP flashable version. It's here: http://forum.xda-developers.com/showpost.php?p=66354183&postcount=1057
Please review the first post in that thread as the ROM is partially debloated and has SuperSU and Xposed pre-installed. GApps have been removed and you need to install your own. It is possible with the files posted to have a full stock install but you'll need the instructions from that thread to accomplish that.
mikeoswego said:
I've put together a debloated TWRP flashable version. It's here: http://forum.xda-developers.com/showpost.php?p=66354183&postcount=1057
Click to expand...
Click to collapse
Which of these files would I want to flash, if I'm running stock firmware (rooted with SuperSU flashed)? The update from Verizon is ~20 MB, but you have a 30MB modem firmware and 398K bootloader.
jonnythan said:
Which of these files would I want to flash, if I'm running stock firmware (rooted with SuperSU flashed)? The update from Verizon is ~20 MB, but you have a 30MB modem firmware and 398K bootloader.
Click to expand...
Click to collapse
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
mikeoswego said:
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
Click to expand...
Click to collapse
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
---------- Post added at 04:09 PM ---------- Previous post was at 03:58 PM ----------
dunderball said:
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
Click to expand...
Click to collapse
It turns out that when I flash the two .zip files, my Moto X still thinks there is a system update available. Is there something else I'm supposed to flash?
mikeoswego said:
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
Click to expand...
Click to collapse
Thanks.. it doesn't seem like I can install just the update. I'd need to flash the whole ROM. Correct?
dunderball said:
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
---------- Post added at 04:09 PM ---------- Previous post was at 03:58 PM ----------
It turns out that when I flash the two .zip files, my Moto X still thinks there is a system update available. Is there something else I'm supposed to flash?
Click to expand...
Click to collapse
jonnythan said:
Thanks.. it doesn't seem like I can install just the update. I'd need to flash the whole ROM. Correct?
Click to expand...
Click to collapse
The two smaller zips are the bootloader and modem firmware, the rom and kernel are in the xt1096-5.1-23.32-25-5-2_1.zip file. You could extract the boot.img file from the zip and flash it with fastboot. If you want the full ROM and want to flash SuperSU yourself and remove whatever bloat yourself, then use xt1096-full-stock-23.32-25-5-2.img.7z file; you can flash the image file within that archive with current versions of fastboot. (Or, using 7zip, you could delete the system.img file from xt1096-5.1-23.32-25-5-2_1.zip then rename the .img file in xt1096-full-stock-23.32-25-5-2.img.7z to system.img and place it in xt1096-5.1-23.32-25-5-2_1.zip. Then you would TWRP flash that, it would update your kernel (boot.img) and install the system partition just as if you took the OTA on the stock system.) Like AGISCI said above, the only way to use the OTA directly is on an unmodified stock system.
Forgive me, I'm not really following you. I don't know what's in the OTA exactly. Is there anything in your post that I can flash that will update my system to the latest version without wiping everything and starting from scratch?
jonnythan said:
Forgive me, I'm not really following you. I don't know what's in the OTA exactly. Is there anything in your post that I can flash that will update my system to the latest version without wiping everything and starting from scratch?
Click to expand...
Click to collapse
You must flash the full firmware like was mentioned earlier. It is impossible to do the update with a modified system.
Sent from my XT1095 using Tapatalk
I'm wondering if there is a way to not take the update. I keep getting a nag message about installing the update and I keep pushing reminder out to a new time.
A little background. I have a XT1096 (Verizon version) and unlocked the bootloader and rooted. I also nuked a bunch of bloatware so there is no way that a OTA update will install. I'm not sure that I really want to go back to stock and start over.
I flashed the system .img file and it just updated my system without wiping anything. Seems to be working fine, but I had to reflash SuperSU.
desertcat said:
I'm wondering if there is a way to not take the update. I keep getting a nag message about installing the update and I keep pushing reminder out to a new time.
A little background. I have a XT1096 (Verizon version) and unlocked the bootloader and rooted. I also nuked a bunch of bloatware so there is no way that a OTA update will install. I'm not sure that I really want to go back to stock and start over.
Click to expand...
Click to collapse
I found a way to not take the update. Use your favorite applications manager for root to freeze MotorolaOTA and the update won't be downloaded and you won't get messages about installing the update.
desertcat said:
I found a way to not take the update. Use your favorite applications manager for root to freeze MotorolaOTA and the update won't be downloaded and you won't get messages about installing the update.
Click to expand...
Click to collapse
THANK YOU!!! After being stuck on vacation for a week with this !#@[email protected]#$ update bugging me to install it every couple of minutes this fix stopped the problem.

What is the purpose of each of the 3 different update zip files ?

Hi,
Sorry of this is a bit of a newbie question but:
What is the purpose of each of the 3 different update zip files ?
And do I have to apply them all - and in what order ?
In my case, I am about to update to B389, and I have downloaded 3 files for VIE-L29C636B389 (currently on VIE-L29C636B130), and I have an update.zip, an update_full_VIE-L29_hw_spcseas.zip and an update_data_full_public.zip.
I was planning on doing the first two by the dload method (with reboots in between), but the update_data_full_public.zip doesn't appear to have an update.app, so how do I load that ? (I do have TWRP on my phone, so could probably figure it out - eventually).
Cheers,
SZ
same question
I read somewhere that it should be flashed in that exact order. i'm guessing that is the same procedure as with auto OTA updates, except now we have rooted phones, so bye-bye to auto updates. I am currently on VIE-L29CB636B387 and i received an automatic Huawei notification of a new version (VIE-L29CB636B388) about a week ago. I tried to update to that version in System Update-Quick Update, but that didn't work (surprise!). There was no issue though as when I rebooted it just went back to 387. However, I now have a red "New Version" notification in my System Update. Please tell me how your upgrade went if you went ahead and flashed 389. I have the three files already from filefinder, i also have TWRP and/or I could use adb fastboot to install. Thanks in advance.
Hey,
I am not sure I want to proceed on the basis of something that somebody 'read somewhere' ....
Anyhow - I've not run these updates yet, as I wanted to backup my phone first, but TWRP keeps blowing up with an error in the middle of the backup, so I am not going to try anything until I get to the bottom of that.
Will let you know if/when I ever go ahead!
Cheers,
SZ
Hi,
TWRP blowing up during NAND backups? thats not a good thing. Upon the advice of a forum member (xzanium) I flashed TWRP 3.1.1-1 instead of TWRP-3.2.1-0-vienna. No hitches so far, solid backups and no hiccups in flashing SuperSU, also got xposed to work seamlessly and other stuff. I hope you are able to resolve the issue you mentioned and get around to getting VIE-L29CB636B389 on your phone.
Well good luck to you, and post here any progress if you would.
SZ,
I have an idea on what the purpose of each of the 3 different update zip files are for and whether you have to apply them all - and in what order.
Since I could make a NAND backup using TWRP without issues, and there was an OTA update notice for an upgrade to VIE-L29CB636B388 which I couldn't upgrade to while rooted, I decided to unroot in order to upgrade to that. First i did the requisite steps - uninstalled the xposed framework and proceeded with the full unroot with SuperSU. Then I performed the dload method to flash the update.app that I extracted from the update.zip.
It was here where i hit a snag. What followed was, I found out that Huawei needs a verified stock rom, meaning it has to be a fullOTA-MF-PV in order that the bootloader could be relocked. So I tried my luck and downloaded the stock ROM VIE-L29C636B370 and flashed that. Success! From there, and several auto upgrades later I was back to L29C636B370. Reinstalling my Google account also locked back FRP. At this point i am full stock EMUI 5
Now, to answer your question. When I tried to upgrade to VIE-L29C636B388 via system update quick update. I only saw one file - update.zip therefore this must the only one needed for incremental patches. The same holds true with update_data_full_public.zip as I later learned when I decided to use the proxy upgrade method in MT filefinder . It applied a 2nd patch. The third file, namely, update_full_VIE-L29_hw_spcseas.zip was not required for this incremental update. In fact, the update process was cut short and an error message appeared that the file could not be located, even though i copied that to the HwOUC folder. It appears that this was deleted before the fullOTA update could finish during the incremental update process. Clearly, this last zip is not necessary for incremental updates. So this must be the package which delivers the rest of the ROM, or the parts of it that needs to be changed.
So, obviously what "I read somewhere" was legit. I hope that answers your question.
cheers!
mm

Security Update OPSS27.104-92-2

I am getting a nag screen to update to opss27.104-92-2 but I can't because I have rooted the phone. I noticed a similar question about the last update and there was a way to manually do the update. Does anyone know where to get the files for this security update so that I can do a manual install.
Alternative, does anyone know where the file is stored on the phone once it is downloaded? If I can find the file then I can probably unzip it and do a manual install.
Thanks
atomclock said:
I am getting a nag screen to update to opss27.104-92-2 but I can't because I have rooted the phone. I noticed a similar question about the last update and there was a way to manually do the update. Does anyone know where to get the files for this security update so that I can do a manual install.
Alternative, does anyone know where the file is stored on the phone once it is downloaded? If I can find the file then I can probably unzip it and do a manual install.
Thanks
Click to expand...
Click to collapse
You can't unzip it and try to apply it. It doesn't work that way. You either have to wait until a full firmware package with this update in it is released or reflash a stock system that matches the one you're on. You would need to flash the entire stock firmware. Then you can boot back to the system and take the update normally.
madbat99 said:
You can't unzip it and try to apply it. It doesn't work that way. You either have to wait until a full firmware package with this update in it is released or reflash a stock system that matches the one you're on. You would need to flash the entire stock firmware. Then you can boot back to the system and take the update normally.
Click to expand...
Click to collapse
I guess I will have to wait until some is kind enough to post a manual install version.
Thanks
atomclock said:
I guess I will have to wait until some is kind enough to post a manual install version.
Thanks
Click to expand...
Click to collapse
There won't likely be a way to install an update on rooted stock. You have to fastboot flash the firmware you're currently on (to remove modifications to system, boot.img, etc), then take the update. That IS the manual method. It should be stored in /cache. The /cache that's in the root directory of the phone. Which G6 do you have?
madbat99 said:
There won't likely be a way to install an update on rooted stock. You have to fastboot flash the firmware you're currently on (to remove modifications to system, boot.img, etc), then take the update. That IS the manual method. It should be stored in /cache. The /cache that's in the root directory of the phone. Which G6 do you have?
Click to expand...
Click to collapse
When I talked about doing the update the manual way, I was talking about doing it the way it is described in this thread.
https://forum.xda-developers.com/moto-g6/help/security-update-to-opws27-113-45-4-wont-t3818421
Hopefully, someone will extract the relevant files from the update and give instructions on manually doing the update. I really wouldn't call restoring the device to stalk and taking the automated update and then re-rooting the manual way. I would call that the hard way.
atomclock said:
When I talked about doing the update the manual way, I was talking about doing it the way it is described in this thread.
https://forum.xda-developers.com/moto-g6/help/security-update-to-opws27-113-45-4-wont-t3818421
Hopefully, someone will extract the relevant files from the update and give instructions on manually doing the update. I really wouldn't call restoring the device to stalk and taking the automated update and then re-rooting the manual way. I would call that the hard way.
Click to expand...
Click to collapse
That thread literally says install the stock firmware. You have to wait for the entire firmware for the new build to be released. no one is extracting anything from any update package. They are just using the full firmware package in that thread. You just have to wait for the full firmware to be posted on mirrors.lollinet.com the November patch for my G6 play was just posted there yesterday. that's why I asked which version of the G6 you have I will link you to the full firmware.
Or, You just fastboot flash stock, take the update, fastboot TWRP, use TWRP to flash magisk. No data loss, easy peasy.
the only difference in those two ways is taking the update after you flash stock or flashing stock firmware including the update. Either way you have to root your device again.
You can even flash stock with RSDlite using service file.xml instead of flashfile.xml
the file they are flashing with fastboot in that thread is the stock firmware. Just the newer one.
I was browsing for firmware today, the newest build/security patch is available on the lollinet Moto under Ali fw
GotHeart said:
I was browsing for firmware today, the newest build/security patch is available on the lollinet Moto under Ali fw
Click to expand...
Click to collapse
The question is can i use different software channel for my G6? Example 1925-6 to 1925-7 to gain particular service carrier signal

Categories

Resources