I am downloading the 722 MB update over OTA right now. Check for software updates in system settings.
root
delphimon said:
I am downloading the 722 MB update over OTA right now. Check for software updates in system settings.
Click to expand...
Click to collapse
did you have your phone rooted? I can´t get the update, I get "There is no updates available for your device at the moment".
jla2024 said:
did you have your phone rooted? I can´t get the update, I get "There is no updates available for your device at the moment".
Click to expand...
Click to collapse
No, the phone has never been rooted. Running stock MF3 with no changes. Checked for update and it was there (still downloading).
delphimon said:
No, the phone has never been rooted. Running stock MF3 with no changes. Checked for update and it was there (still downloading).
Click to expand...
Click to collapse
My phone is rooted and it showed up!!!
Finished installing. 4.3 I537UCUBML2 confirmed
how i can install this rom on mi s4 active carrier Telcel
someone who can upload some zip to flash or créate .tar file
ok so i got the update to download then went to intall and it came up that the update was interrupted could that be because of having rooted my phone?
htcman724 said:
ok so i got the update to download then went to intall and it came up that the update was interrupted could that be because of having rooted my phone?
Click to expand...
Click to collapse
Can somebody pull the update file off their phone for the rest of the community? You have to do this before you install update. Basically what the phone does is download the update to a temporary directory on your phone and then installs the update. Once updated the phone then deletes the update file.
Your phone will download the update file.
It will ask you to install the update, DON'T press Cancel and DON'T press Update, instead hit the home button (don't worry it will ask you again later).
Open your root file manager, go up to the root directory and go to /cache/fota/ and copy the zip file from your phone to your computer. This zip file is the update file.
Upload the file and post the link for the community
Wallow in all the "Thanks" you will receive
IMPORTANT: You must grab the update file before your phone updates or the file will be deleted.
EDIT: Information about copying the update file can be found in this post by @thatbigmoose
htcman724 said:
ok so i got the update to download then went to intall and it came up that the update was interrupted could that be because of having rooted my phone?
Click to expand...
Click to collapse
Had the same problem. Do I have to return to stock and un-root to install the update?
Devo7v said:
Can somebody pull the update file off their phone for the rest of the community? You have to do this before you install update. Basically what the phone does is download the update to a temporary directory on your phone and then installs the update. Once updated the phone then deletes the update file.
Your phone will download the update file.
It will ask you to install the update, DON'T press Cancel and DON'T press Update, instead hit the home button (don't worry it will ask you again later).
Open your root file manager, go up to the root directory and go to /cache/fota/ and copy the zip file from your phone to your computer. This zip file is the update file.
Upload the file and post the link for the community
Wallow in all the "Thanks" you will receive
IMPORTANT: You must grab the update file before your phone updates or the file will be deleted.
EDIT: Information about copying the update file can be found in this post by @thatbigmoose
Click to expand...
Click to collapse
im redownloading it now as soon as its done i'll upload it
treystegall said:
Had the same problem. Do I have to return to stock and un-root to install the update?
Click to expand...
Click to collapse
I had the same problem, as well. Went through download, then restarted. Seemed to restart overly quickly, then saw that I was still on 4.2.2. Is there a log file somewhere that I can look at?
I will try and pull it off my wife's phone tonight!
Has anybody on MI2 been notified of an update? I'm guessing not since MI2 was a pre-release so it would be interesting to see if someone has.
Devo7v said:
Has anybody on MI2 been notified of an update? I'm guessing not since MI2 was a pre-release so it would be interesting to see if someone has.
Click to expand...
Click to collapse
I am on the MI2 leak rooted no OTA notification . Says up to date
I'm guessing I won't see OTA if I am on Tmo's network??
We are not left behind!
I can confirm, from Indiana, that the 4.3 update has come to the S4Active OTA.
Just gave it a try and I got the update downloading even though I'm on Tmo's network! Yes!! Wasn't working before cause I remember I removed KnoxAgent.apk and wssyncmldm.apk but I put those back and it's all good
Devo7v said:
Can somebody pull the update file off their phone for the rest of the community? You have to do this before you install update. Basically what the phone does is download the update to a temporary directory on your phone and then installs the update. Once updated the phone then deletes the update file.
Your phone will download the update file.
It will ask you to install the update, DON'T press Cancel and DON'T press Update, instead hit the home button (don't worry it will ask you again later).
Open your root file manager, go up to the root directory and go to /cache/fota/ and copy the zip file from your phone to your computer. This zip file is the update file.
Upload the file and post the link for the community
Wallow in all the "Thanks" you will receive
IMPORTANT: You must grab the update file before your phone updates or the file will be deleted.
EDIT: Information about copying the update file can be found in this post by @thatbigmoose
Click to expand...
Click to collapse
ok so i went there and there was no zip file. tryed to reinstall it and it failed again. has anyone gotten it to install?
htcman724 said:
ok so i went there and there was no zip file. tryed to reinstall it and it failed again. has anyone gotten it to install?
Click to expand...
Click to collapse
I looked for the file as well and there was no zip located in cache\fota
---------- Post added at 10:25 PM ---------- Previous post was at 10:17 PM ----------
moppegaard said:
I looked for the file as well and there was no zip located in cache\fota
Click to expand...
Click to collapse
nevermind, I'm not rooted so I can't access the file
I'll have it uploaded within the hour to Dropbox unless someone beats me to it. I'm at 50% right now.
Upload took a little longer than I thought. Also file is .cfg and not a .zip from the OTA. But it will still run on phone through update. I'll post link and screenshots as soon as the file uploads.
Related
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
[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!!!!
Android newbie trying to do a 6.20.651.3 update on a HTC One M8 Sprint variant. I’ve tried the direct download method, I get to 1.06gb, download successful, verified, unzipping update then reboots and flashes up some errors and goes into TWRP recovery.
I have also had a few goes at it from Windows running RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.EXE that fails as well with an error 155: unknown error: cannot update Android phone, please get the correct ROM update utility and try again or just hangs there on 0% for 30 mins.
Device has s-off and is rooted - at least Root Checker app says it is but it can also report not properly installed. I've just tried the direct download method once more having used the Root Check app to confirm that it is rooted but with same result.
Can anyone give me a few pointers in terms of what I have to do to get this to work. Help much appreciated.
You won't be able to take the OTA update with TWRP installed. As for running the latest RUU, you have to have the latest firmware installed first. You'll also need the latest version of TWRP if you want to flash a MM ROM. Check OMJ's RUU thread in Android Development for more info.
An alternative to taking the OTA or running the RUU would be to update your firmware & TWRP recovery, then flash a stock rooted MM ROM.
Thanks for your response. It has given me some understanding of the different types of update. I checked my TWRP and it is 2.8.7.0, which is the latest, and tried a firmware update using the firmware update utility from here
http://forum.xda-developers.com/showthread.php?t=2729173
and downloaded one of the non-Harman extracted firmware versions, renamed to rom.zip, put it in required folder and ran ARUWizard.exe and it is stuck on updating (0/1) sending, has been for 15 mins so I can assume that this will not work.
Any ideas? There are four variants: full, full signed, with / without recovery, boot. Am I running the wrong firmware?
Download the modified MM firmware (no boot or recovery) and place it on your external SD card and rename the file 0P6BIMG.zip (make sure the file doesn't have an extra .zip extension on the end). Reboot to the boot loader and update your firmware when prompted. As for TWRP, there is a newer version available. Check the last couple of pages of the TWRP thread in Original Development. It's version 2.8.9.0.
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
mp
check your mp
Cliff2016 said:
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
Click to expand...
Click to collapse
Cliff2016 said:
A few more hours of life gone, and still no joy with this update I'm afraid.
Back to where I was yesterday using the firmware update utility I notice today that the firmware zip I used couldn't be opened, not a valid zip. So that is why that failed. Also if I go with updating the firmware from an external SD card, again EVERY zip I download from whatever server I use.
To be honest, I'm not exactly sure from this page
http://forum.xda-developers.com/showthread.php?t=2729173
which zip I need to download.
Would you be good enough to just give me one method to update the firmware and a link to a zip that will open. Also, am I right in thinking that if I get the firmware updated then I should be able to do either an OTA update or a RUU installer under Windows.
To be honest, I'd be glad to drop you £20 via Paypal if you could help me get to a working v6 phone.
Click to expand...
Click to collapse
Download the file linked below. Once you've done that, click the link in my signature for the M8 hboot guide. Scroll down to the section on firmware updates (it's in the very first post) and follow my instructions in my guide to update your firmware.
https://www.androidfilehost.com/?fid=24391638059059964
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
[Solved] So i was gonna download the december update but mid-download my wifi decided to suck. When the connection came back the download just resumed. It's finished now but I'm scared to install the update. Is there a way to delete the update file and redownload it? I'm not rooted and I don't want to flash the update. Please help!
KasraMC said:
So i was gonna download the december update but mid-download my wifi decided to suck. When the connection came back the download just resumed. It's finished now but I'm scared to install the update. Is there a way to delete the update file and redownload it? I'm not rooted and I don't want to flash the update. Please help!
Click to expand...
Click to collapse
just go to download location using file browser and delete the files you downloaded as normal
I don't remember but the name is something like ht team or ht something on root of internal sd
KevMetal said:
just go to download location using file browser and delete the files you downloaded as normal
I don't remember but the name is something like ht team or ht something on root of internal sd
Click to expand...
Click to collapse
I didn't download a flashable file i downloaded the normal way from settings. It's fine the emui updater checks for the integrity of the file and im on the latest update with no problems so far.