Ok, so updated to the latest Oreo build, September, and flash via fastboot. Phone is on the latest version of the OS but the update notification is showing and asking me to download/install the update. I tried disabling the update services and that did not work. The notification will not go away.
Ideas on this one?
I would also want to know, did the same thing as OP, but with rooting and superSU/Magisk.
Reflashed the update and still the same. Thought maybe it was a bad flash. So now I flashed one more time to be on 100 stock and downloading the OTA via the OS notification. Hopefully it installs ok and hopefully the notification will go away after. Then I will just root it after.
Found out hte problem......
So I flashed the latest factory image available for the 6p. Which is OPR6.170623.017. Then I did not root/apply a diff recovery. I booted in to the OS and let the phone update OTA. Checked version number and it was OPR6.170623.019. So the latest factory image for the N6p is not yet available.
There are two versions of September version.
017 and 019
The factory image is 017 and you have to run the OTA to get the 019.
wizardwiz said:
There are two versions of September version.
017 and 017
The factory image is 017 and you have to run the OTA to get the 019.
Click to expand...
Click to collapse
I assume you mean "There are two versions of September version, 017 and 019" ?
I was just about to ask about this. Did a full factory flash and then let the OTA do it's thing. Bit strange why there is an OTA and no factory image, I usually always do a clean install.
Related
Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?
Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?
Hub00 said:
Hi,
I have an ALE-21 on B574, with bootloader unlocked, no root.
I received notification for a new update to B584. So I flashed stock recovery (was on TWRP) and launched the OTA update.
It went all the way to 100% download, but failed to install.
Is there a catch, did I forget something ?
Click to expand...
Click to collapse
Try it once again... I've never received OTA updates from b560 onwards.. You could flash your way through
crashpoum99 said:
Hmm... Did you have root at any point? What was the failure message that you got? Also, was your B574 rom modified or plain stock?
Click to expand...
Click to collapse
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
You can try local update......And preferably Force update but it will delete all your data so backup your data And Force update........ Btw leave B584 because B588 is avaiable
Hub00 said:
I had root to enable the pseudo-gyroscope and then unrooted (with some pain) to play Pokemon go.
The B574 is stock, I got it through OTA last time (september if I remember correctly).
I tried changing the source of the stock recovery, but it did'nt work either. The failure message comes after reboot : it's a EMUI notification "last update failed".
Click to expand...
Click to collapse
I would try force updating using the Power+Vol.Up+Vol.Down method. Go for B588 if you want, as it's newer with the latest security patch. If the error comes after the reboot, it's most likely that force updating will fix this. Remember, force updating will delete your files!
What actually worked is downloading 'full package' in the update menu (the file was 1.56Go instead of 260 Mo). It updated overnight even with twrp. Of course, I lost gyroscope in the process...
So I'm know with B584. I will try to force update to B588 as soon as it is downloaded.
Ok, i'm know on B588 and I have gyroscope back again. Thanks for your help.
However, despite the changelog, i didn't notice any improvement with the whatsapp notifications.
Any idea why ?
Trying to update the 4.5.1 and it seemed to have gone fine until it automatically reboots into TWRP recovery. Upon rebooting into system, it states the update failed. With TWRP having all those jumbled folder names right now (has this been fixed yet?) it's hard to see if the update downloaded somewhere to internal storage, and further if it could be flashed even if I found it. Is updating with an OTA like this possible? I know on basically all other phone it is not. Has anyone gotten the update to work while being unlocked, rooted, with TWRP? Thanks.
xgerryx said:
Trying to update the 4.5.1 and it seemed to have gone fine until it automatically reboots into TWRP recovery. Upon rebooting into system, it states the update failed. With TWRP having all those jumbled folder names right now (has this been fixed yet?) it's hard to see if the update downloaded somewhere to internal storage, and further if it could be flashed even if I found it. Is updating with an OTA like this possible? I know on basically all other phone it is not. Has anyone gotten the update to work while being unlocked, rooted, with TWRP? Thanks.
Click to expand...
Click to collapse
Generally you need to reflash the previous Full ROM with TWRP and then flash the OTA on top for it to work as the system must be unmodified. Alternatively, you can just flash the latest Full ROM. Currently those are not available, but that's generally how it works.
If u have installed twrp before updating the stock rom, I guess we have to wait for full rom of latest update 4.5.1 which can be flashed via twrp.
P.s. FLASHING the dwnloaded update via twrp will gives u error.. So have to wait for full rom. ?
Hi guys
Currently, i have a nexus 6p, 7.1.2, rooted and bootloader unlocked.
Got the android O ota updates on my phone. however, wanted to know is it safe to upgrade now using flashfire?
1st, any problems when using flashfire to do the updates
2nd, any problems on android O itself?
3rd, do i still have root after the udpate?
Thanks.
mousefai0922 said:
Hi guys
Currently, i have a nexus 6p, 7.1.2, rooted and bootloader unlocked.
Got the android O ota updates on my phone. however, wanted to know is it safe to upgrade now using flashfire?
1st, any problems when using flashfire to do the updates
2nd, any problems on android O itself?
3rd, do i still have root after the udpate?
Thanks.
Click to expand...
Click to collapse
There is a thread on this ongoing at literally this moment. My experience is that FF with the OTA does not work. Others have reported that it does. So YMMV. The fastboot method worked for me. FF with full factory images may work, but since radio is still recommended to be flashed via fastboot you might as well do everything via fastboot.
mousefai0922 said:
Hi guys
Currently, i have a nexus 6p, 7.1.2, rooted and bootloader unlocked.
Got the android O ota updates on my phone. however, wanted to know is it safe to upgrade now using flashfire?
1st, any problems when using flashfire to do the updates
2nd, any problems on android O itself?
3rd, do i still have root after the udpate?
Thanks.
Click to expand...
Click to collapse
I was trying FF this morning, lastest update 0.71, rooted with Magisk , TWRP and it failed.
Got stuck on a black screen for more than five minutes until I forcefully rebooted the device.
waiting for the factory images I guess.
wizardwiz said:
I was trying FF this morning, lastest update 0.71, rooted with Magisk , TWRP and it failed.
Got stuck on a black screen for more than five minutes until I forcefully rebooted the device.
waiting for the factory images I guess.
Click to expand...
Click to collapse
it seem like the android O have bugs and problem itself, and with now the failing flashfire problems... i think i should wait
GroovyGeek said:
There is a thread on this ongoing at literally this moment. My experience is that FF with the OTA does not work. Others have reported that it does. So YMMV. The fastboot method worked for me. FF with full factory images may work, but since radio is still recommended to be flashed via fastboot you might as well do everything via fastboot.
Click to expand...
Click to collapse
it seem like the android O have bugs and problem itself, and with now the failing flashfire problems... i think i should wait
I just used FF ver. 0.72 on 2 rooted, twrp'd, supersu'd Nexus 6P's and flashed the full factory Sept. 2017 OPR6 image that was published this morning. FF worked like a champ. Just don't update the bootloader and radio with FF.
I am still on 6.0.1 (Build MTC20L), upgraded using FF. If i want to move to 8.0.0 (OPR6.170623.017, Sep 2017), what builds do I need to stop at along the way? I was guessing at the very least 7.1.1 (NUF26N, Mar 2017, Verizon Only), but want to be sure.
states_enemy said:
I am still on 6.0.1 (Build MTC20L), upgraded using FF. If i want to move to 8.0.0 (OPR6.170623.017, Sep 2017), what builds do I need to stop at along the way? I was guessing at the very least 7.1.1 (NUF26N, Mar 2017, Verizon Only), but want to be sure.
Click to expand...
Click to collapse
No, just use the latest full Google 8.0 image with FF. Untick the bootloader and modem partitions. Your phone will boot up with 8.0, then update the bootloader and modem (radio) separately. Best to flash with fastboot, but there are TWRP flashable zips around here.
v12xke said:
No, just use the latest full Google 8.0 image with FF. Untick the bootloader and modem partitions. Your phone will boot up with 8.0, then update the bootloader and modem (radio) separately. Best to flash with fastboot, but there are TWRP flashable zips around here.
Click to expand...
Click to collapse
I'll be using FF, however I don't recall ever updating the bootloader or modem in the past. I don't need to do that, do I?
states_enemy said:
I'll be using FF, however I don't recall ever updating the bootloader or modem in the past. I don't need to do that, do I?
Click to expand...
Click to collapse
You know what they say about not fixing it if it's not broken, but.... While bootloader and modem are independent of the android version itself, you should generally try to keep them up to date. Not sure how a bootloader would be improved, but there are constant tweaks to the radio going on. If you don't have a current, working version of ADB/fastboot on your PC this would be a good time to get it set up and working properly ( ie. when you are NOT having a problem). There is virtually no way you can screw up flashing these, and they take less than a second or two each. You can find the *.img files in the root of any full Google image. As a primer, open up the flash-all.bat file there and read the script. Change the file extension from *.bat to *.txt and open with Notepad. There you will find the fastboot commands for flashing these two. Best of luck.
I see over a dozen different versions here but I'm not sure which one to download:
https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I've already tried two different ones but I receive no cell signal when it boots.
Any ideas?
Thanks!
I actually found the answer on my own: none of them. Wrestling with the G5 this morning made me lose my mind. I ended up with the Pixel ROM.
Does anyone have a copy of the XT1687 stock rom (carrier unlocked ... I bought mine at Costco)? I could really use it.
My phone is totally messed up. My /system is empty except for 'bin'....
Thank you for any help!
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
did going back to stock and accepting the OTA work for you??!
roydhritiman said:
did going back to stock and accepting the OTA work for you??!
Click to expand...
Click to collapse
I ended up with some kind of error with the OEM partition, but in the end all of the details on my settings screen show that I'm on the latest security patch, kernel, etc.
dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
dunderball said:
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
dlong said:
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
Patches, a full ROM is rarely sent as an OTA. You'll know it's a full ROM if the size of the OTA is greater than 1GB. Anything less than say 300-400MB is patches to the system
dlong said:
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
I went from version 83 to successful OTA 92 (November patch), then to 93 January patch (but ended up with a failure message after booting up for whatever reason). I'm on retus, baseband M8953_37.46.07.47R POTTER_NA_CUST, build number NPNS25.137-93-4.
As far as I see, I don't see any full stock firmware out for NPNS25.137-93-4 which is unfortunate. I have a feeling my update to Oreo will fail if it ever comes out. I'm not even sure why my OTA fails, as I do my best to avoid modifying any partitions and mostly use systemless modules through Magisk. Whatever though.
No joy. So apparently, since I'm on NPN25.137-92 (POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), I wasn't able to downgrade to (POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
I did re-flash everything and the results seems to be the same (unable to 'see' new updates). I am on November 2017 patch but when I check for upgrades, it states the system is up to date.
I hope that because my phone is 'unlocked from store (Costco - USA)' that RETAIL is the correct firmware. Anyone know for sure?
Also... I guess I wiped recovery when I installed TWRP. Is there an OEM recovery.img available for Moto 5G Plus?
Edit: So the whole reason, I originally rooted my phone was so that I can enable Hot Spot by adding net.tethering.noprovisioning=true to /system/build.prop (now I wonder if root is even required to do that?)
I cannot update my new-from-Amazon TB-X304f from Android 7.1.1 to Android 8.1. The logs say that the update signature doesn't match the UID on the tablet, and the update fails. I've tried from both the system update on the tablet (wiped cache and factory reset just to be sure), and the Lenovo Smart Assistant. Neither work.
Any advice?
The build number I have is: tb-x304f_s000053_180927_row/
The version I'm trying to update to is: tb-x304f_s0001014_181113_row/
Hello, I have a TB-X704F, rooted with Supersu, TWRP and Xposed Framework. For several weeks the tablet wants to install an OTA update. Since the device is rooted, it reboots and then lands at TWRP. The whole thing keeps repeating itself, I am constantly asked to install the update right now or later. In the developer options the automatic system updates are deactivated, nevertheless the tablet wants to update constantly.
When I select full Unroot in Supersu, the tablet stops booting and stops at the Lenovo logo.
What can I do to install the OTA or other update or disable the update prompts?
Thank you!
64erbaz said:
Hello, I have a TB-X704F, rooted with Supersu, TWRP and Xposed Framework. For several weeks the tablet wants to install an OTA update. Since the device is rooted, it reboots and then lands at TWRP. The whole thing keeps repeating itself, I am constantly asked to install the update right now or later. In the developer options the automatic system updates are deactivated, nevertheless the tablet wants to update constantly.
When I select full Unroot in Supersu, the tablet stops booting and stops at the Lenovo logo.
What can I do to install the OTA or other update or disable the update prompts?
Thank you!
Click to expand...
Click to collapse
You need to flash back to factory default and let the OTA install over that.
It's not worth it in my opinion. Im waiting for a new TWRP to be available.
swieder711 said:
You need to flash back to factory default and let the OTA install over that.
It's not worth it in my opinion. Im waiting for a new TWRP to be available.
Click to expand...
Click to collapse
I'm having this same issue. How do I flash back to factory default?
baydude said:
I'm having this same issue. How do I flash back to factory default?
Click to expand...
Click to collapse
Covered many times in this thread. Get in edl mode and flash stock with MiFlash
Orangebanannax said:
I cannot update my new-from-Amazon TB-X304f from Android 7.1.1 to Android 8.1. The logs say that the update signature doesn't match the UID on the tablet, and the update fails. I've tried from both the system update on the tablet (wiped cache and factory reset just to be sure), and the Lenovo Smart Assistant. Neither work.
Any advice?
The build number I have is: tb-x304f_s000053_180927_row/
The version I'm trying to update to is: tb-x304f_s0001014_181113_row/
Click to expand...
Click to collapse
I'm having the same problem, any luck? I've been attempting to flash back to an earlier rom to see if that fixes the problem, but I haven't been able to find a stock rom that actually works yet.
Orangebanannax said:
I cannot update my new-from-Amazon TB-X304f from Android 7.1.1 to Android 8.1. The logs say that the update signature doesn't match the UID on the tablet, and the update fails. I've tried from both the system update on the tablet (wiped cache and factory reset just to be sure), and the Lenovo Smart Assistant. Neither work.
Any advice?
The build number I have is: tb-x304f_s000053_180927_row/
The version I'm trying to update to is: tb-x304f_s0001014_181113_row/
Click to expand...
Click to collapse
Weird fix that seems to have worked. make a backup of the system using twrp following this https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407, then grab the boot.emmc.win and reflash it using fastboot. I'm currently installing the 8.1 update as I type this.