Android wear 1.3 update - LG Watch Urbane

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

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

[ROM][Backup]Stock LCA43

[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!!!!

Can't update to 6.0.1

Hello everyone
I received the 6.0.1 update but I can't download it. It keeps on saying retry download.
I tried to restart and nothing happened.
It may just be a server overload. And I believe that once it's tried it reschedules you while it moves on to other devices, so just keep an eye open for the next one and try again.
If you don't want to wait, you can always sideload the OTA using ADB (you don't have to, but you have an option - assuming your phone is stock)
dahawthorne said:
It may just be a server overload. And I believe that once it's tried it reschedules you while it moves on to other devices, so just keep an eye open for the next one and try again.
Click to expand...
Click to collapse
jj14 said:
If you don't want to wait, you can always sideload the OTA using ADB (you don't have to, but you have an option - assuming your phone is stock)
Click to expand...
Click to collapse
Thanks everyone
I downloaded it 4 times today. Crashed every time I tried to install it.
Larzzzz82 said:
I downloaded it 4 times today. Crashed every time I tried to install it.
Click to expand...
Click to collapse
I think because of the costume recovery.
I can't install it too
OTA (or sideloading the OTA) will work only if you are stock. If you have custom recovery, OTA will fail to install
xhamadeex said:
I think because of the costume recovery.
I can't install it too
Click to expand...
Click to collapse
I was completely stock. No twrp.
That was then... Flashed 6.0.1, twrp and the boot image and apk that @doitright is working on, and I got Root sans the triangle pop ups.

Can't update to WW1908 from WW1907

On PKQ1.19041.001.WW_Phone-16.0622.1907.33-0
Copied this file ( UL-ASUS_I001_1-ASUS-16.0631.1908.12-1.1.3-user.zip ) from ASUS update server to my ASUS phone to the root folder (internal storage) it sees the file and I get a message saying that my phone can be updated. But when I click ok to upgrade, it fails.
Anyone try this and successful? Any ideas what the heck I am missing here?!
TY
Maybe corrupted download? Try downloading again.
I had a corrupted download and ended up bricking my phone. Had to flash the Raw 1906 then incrementally update to 1908
stealthj said:
Maybe corrupted download? Try downloading again.
I had a corrupted download and ended up bricking my phone. Had to flash the Raw 1906 then incrementally update to 1908
Click to expand...
Click to collapse
Let me download it again. Hope it works. If this does work, I will feel a lot better about updating my awesome phone in the future. Coming from Samsung on AT&T hopefully ASUS keeps the updates fairly regular.
Nope, still not working. Oh well, guess I can wait for the raw version.
But if anyone has any ideas on what I am missing, please chime in.
jkeener88 said:
On PKQ1.19041.001.WW_Phone-16.0622.1907.33-0
Copied this file ( UL-ASUS_I001_1-ASUS-16.0631.1908.12-1.1.3-user.zip ) from ASUS update server to my ASUS phone to the root folder (internal storage) it sees the file and I get a message saying that my phone can be updated. But when I click ok to upgrade, it fails.
Anyone try this and successful? Any ideas what the heck I am missing here?!
TY
Click to expand...
Click to collapse
If you haven't changed the fingerprint to WW yet, the OTA file will be recognized and fail. Change fingerprint and you should be good
xxBrun0xx said:
If you haven't changed the fingerprint to WW yet, the OTA file will be recognized and fail. Change fingerprint and you should be good
Click to expand...
Click to collapse
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
jkeener88 said:
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
Click to expand...
Click to collapse
It's not a physical fingerprint, it's how the phone identifies itself. Follow this guide: https://forum.xda-developers.com/ro...w-rom-changing-cn-fingerprint-t3969765/page12
jkeener88 said:
I never set a fingerprint. so if I set one now, and then try the update it might work? I guess I will try that and see what happens.
Click to expand...
Click to collapse
you probably got a Chinese 8gb version with flashed WW firmware, which means no OTA anymore. You gotta flash manually after unlocking the bootloader, rooting and so on.
skromnia said:
you probably got a Chinese 8gb version with flashed WW firmware, which means no OTA anymore. You gotta flash manually after unlocking the bootloader, rooting and so on.
Click to expand...
Click to collapse
Thanks, ya learning a lot on this phone. Just got figure it all out without bricking my ROG!
xxBrun0xx said:
It's not a physical fingerprint, it's how the phone identifies itself. Follow this guide: https://forum.xda-developers.com/ro...w-rom-changing-cn-fingerprint-t3969765/page12
Click to expand...
Click to collapse
Thank you so much for pointing me in the right decision, and also although I don't see that many Subaru vehicles in Houston, I plan on getting one this year or maybe next year. Thanks again, up to 1908 now. :good:
Chinese 8gb Tencent q
I'm on 1906 ww. I understand this phone needs a manual flash each time, do I need to flash with every update using raw files and will this also wipe the phone so every update means a wipe?
Can I root, install twrp and simply update the firmware no issue or is it bs?
How do I actually manually update to this? When I hold down on the options button and choose "more options", it still only says Auto-Download System Update
Do I need to flash through fastboot?
Edit: Nevermind, I restarted my phone and it gave me a pop up saying it sees the update
viper98 said:
How do I actually manually update to this? When I hold down on the options button and choose "more options", it still only says Auto-Download System Update
Do I need to flash through fastboot?
Edit: Nevermind, I restarted my phone and it gave me a pop up saying it sees the update
Click to expand...
Click to collapse
i just update to to latest one
u need twrp
put twrp and magisk and the update on root of ur device
flash twrp it will crash first time the next restart will work without any problem
flash and select the latest ota update that u downloaded from asus it take some time
then flash twrp again then flash magisk after all done reboot
work for me no problem

Question System Update Issue (Fixed)

Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Update: I attempted the system update again and left it overnight. This morning it's still stuck on the same installing screen.
Can someone share the Android Version screen of an unlocked Pixel 7. I think I might be updated and the update is just a bug?
Update: I determined I had an OTA update failure. So I just adb sideloaded the OTA file and it's fixed now.
KillerDroid96 said:
Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Click to expand...
Click to collapse
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.
ern88 said:
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.
Click to expand...
Click to collapse
It's set to mobile data and that should only impact the downloading not installing. 4 hours now and still stuck. I'm considering rebooting at this point.
I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.
Giovanni9518 said:
I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.
Click to expand...
Click to collapse
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.
KillerDroid96 said:
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.
Click to expand...
Click to collapse
My Google play system also states that too.
Well I give up. I restarted and I'm just not going to update for the time being.
ern88 said:
My Google play system also states that too.
Click to expand...
Click to collapse
I think I'm actually fully updated and its just a bug?
@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.
KillerDroid96 said:
@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.
Click to expand...
Click to collapse
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.
ern88 said:
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.
Click to expand...
Click to collapse
Thanks! I determined I had an OTA
update failure. So I just adb sideloaded the OTA file and it's fixed now.
So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.
gorilla p said:
So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.
Click to expand...
Click to collapse
They've covered this in the two big threads regarding unlocking / rooting in the 7 Pro-forum.

Categories

Resources