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
Related
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well
gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
shelooga said:
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well
Click to expand...
Click to collapse
sheloga is correct. You'd have to revert back to full stock or wait for someone to make a flashable zip.
Can't you just flash the stock recovery and take the OTA? Or do you have to fully unroot and reflash the factory image?
I would like to pay close attention time to this thread because that is one is the main questions that I have. I hear so many different solutions towards this. I usually wait for a flashable zip but I would want to see someone either wrote a write up or make a video. Subscribed.
My understanding (from looking at the lollipop OTA updater-script) is it checks EVERY file for changes, including other partitions. You must be 100% stock with nothing extra in system (SuperSU apk or busybox etc).
gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.
BLUF: wait until OTA is made available in a recovery flash method. 90% of the time the OTA updates are patching security holes and other less important features.
Having been with a handful of different android devices in the past several years, I've always gone the route of flashing from recovery vs. OTA.
The LG G3 for example had an OTA just recently that broke rooting. It was fixed by a Dev, but that's the only update found in OTA.
Sent from my Nexus 6 using XDA Free mobile app
Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
simms22 said:
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.
Click to expand...
Click to collapse
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
no thoughts.
i just flash aosp hours after it appears there. or just wait for @rascarlo to add it to his rom, then i flash
HyperM3 said:
Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
After Android 5.0, you can't sideload the OTA file if you have made any changes to the system partition. You need to be completely stock to take OTA. You can just download the new factory images and extract the various img files from it and just flash those manually in ADB, thereby overwriting your modified system partition with the new factory system image (you can skip overwriting the userdata if you want to preserve your data). No need to revert back to stock (old image) and then take OTA - unnecessary step.
HyperM3 said:
Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?
gwojo22 said:
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?
Click to expand...
Click to collapse
From google
https://developers.google.com/android/nexus/images
hlxanthus said:
From google
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately
waqar.qu said:
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately
Click to expand...
Click to collapse
You need to install ADB and fastboot. After that, you can use the 'fastboot' command directly from Terminal. I've found that the easiest way to update Lollipop on my Nexus 6 is to:
Download image from Google
Decompress the archive, AND the second archive which was contained within the first one. Note: The recovery, boot, and system images are in the second archive.
Open Terminal, change directory to the extracted folder, and run these commands (they skip overwriting the userdata partition):
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
fastboot reboot-bootloader (VERY IMPORTANT TO DO THIS STEP)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
You need to restore root at this point; you can use these instructions if you're unfamiliar with the procedure.
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
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.
Hi guys, I am only a very junior user who randomly flash his phone but most of the time I want my phone to be stable for work. I have had the situation since the recent OTA available, suffered a lot, would like to seek any help or advice.
I have a L09C635B361, Japan version. I updated to Android 7 via OTA, then unlocked / rooted under the instructions in this forum, forgot which exact thread though. Never thought of flashing any customized rom so I haven't realized the update problem until the recent OTA update (from B361 to B382) released. I got the push, downloaded B382 OTA package, restart to TWRP, then the flash was failed in TWRP screen. Restart again, the system notified there was a recent update failure. Then I installed Firmware Finder, downloaded the 3 update zip files, restart back to TWRP, still failed installing. Please refer to the failure screenshot for detailed reson. I have no idea what it said and how I should do differently.
No other way to go, I backed up my system, then wiped my phone, reset to factory mode, but brand new system was very strange: only voice input, no keyboard, missing several key functions such as camera. So I have to restore to my previous system, everything worked well except I can't open "clock".
Right now I am looking at system notification of B382 all the time, but I can't figure out how to get it updated, I don't mind if there's a way enables me go back to stock rom, but it's really hard to find the stock firmware for C635......
Thanks, appreciate your help in advance.
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
xMrTROLLIPOPx said:
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
Click to expand...
Click to collapse
Thanks bro. I will try the entire process when I have a backup phone.
One more thing is when I first tried to wipe phone, failed for several times. Plus the TWRP flashing error, I have suspect that there's something wrong with my partition information or format error. Can anyone help me to eliminate the possibility by the screenshot please?
On the other hand, I found 3 zip files on Firmware for same version update. Which one should I flash? If I need to flash all of the 3, is there a sequence?
The screenshot for the 3 zip files.
oushouseki said:
The screenshot for the 3 zip files.
Click to expand...
Click to collapse
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
lostunsunghero said:
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
Click to expand...
Click to collapse
Well, it ended up with paying 20USD to some "pro"s on taobao.com to unbrick my P9...sigh...am I too old to do this :crying:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Maybe Oxygen Updater has full download link?
BeachNYC said:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Click to expand...
Click to collapse
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
kouzelnik3 said:
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
Click to expand...
Click to collapse
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
BeachNYC said:
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
Click to expand...
Click to collapse
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
kouzelnik3 said:
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
Click to expand...
Click to collapse
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
BeachNYC said:
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
Click to expand...
Click to collapse
You can try complete uninstall of the magisk by clicking on that button in the app, but better have a backup of your data if anything goes wrong.
Or you can just download the full Ota zip using oxygen updater and use that local update apk if it goes through. Also use that local update apk for android 13 as there is for A12 and for A13. It might solve the issue too.
Did you flash stock recovery to both slots the last time?
g96818 said:
Did you flash stock recovery to both slots the last time?
Click to expand...
Click to collapse
No. Should I?
BeachNYC said:
No. Should I?
Click to expand...
Click to collapse
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
g96818 said:
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
Click to expand...
Click to collapse
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
BeachNYC said:
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
Click to expand...
Click to collapse
idk. safest way is probably change regions or wait for a full rom. I have c.30 ota download links in my update post, but idk if you want to chance it.