[Problem] stock rom 7.1.1+TWRP 3.1.1+magisk 14.0->how to update OTA NPSS26.118-19-4?
Hello,
I recently got the moto z2 (XT1710-09) on a NPS26-118-19.
unlocked it, installed TWRP 3.1.1 and rooted through magisk 13.1 and magisksu.
I updated magisk to 14.0 when it showed up.
I just got the new OTA update NPSS26.118-19-4 asking to be updated. I don't want to lose my root or have to config again all the /data.
I think I found the update on /cache/Blur_Version.26.51.19.albus.retail.en.US.zip, is it the one?
I found on some sites defining the 'right folder' for motorola OTA downloads in /data/data/com.motorola.ccc.ota/app_download/ but there seems to be nothing in those folders.
I started investigating flashfire, but it does not seem to work properly on this phone, as I asked for a backup and it rebooted to a black screen without any activity for like 5 minutes (not even backlight).
I guess it may be because it is magisksu and not supersu? does it make a difference to it?
I guess I should report the bad behaviour of flashfire to chainfire, but I am not sure about the rest.
has someone already tested all this?
Thank you guys
sik_gerar said:
Hello,
I recently got the moto z2 (XT1710-09) on a NPS26-118-19.
unlocked it, installed TWRP 3.1.1 and rooted through magisk 13.1 and magisksu.
I updated magisk to 14.0 when it showed up.
Click to expand...
Click to collapse
Most likely your system partition has been modified. So you have to revert to "stock" in order to flash the OTA. You will be only able to do that if you have a byte for byte backup of the system image, as far as I know. Most people don't have that. But if you have a backup of the system image (and the other partitions like recovery ...), you could revert to stock, OTA, and root again.
If not, you could also check whether this stock image is compatible with your device XT1710-09.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
This is the only retail stock image available but it is not clear (to me) for which variant.
sik_gerar said:
Hello,
I found on some sites defining the 'right folder' for motorola OTA downloads in /data/data/com.motorola.ccc.ota/app_download/ but there seems to be nothing in those folders.
Click to expand...
Click to collapse
In my case I found the update file in folder /data/data/com.motorola.ccc.ota/app_download/
Update:
Please see also this topic
https://forum.xda-developers.com/z2-play/help/installing-ota-updates-questions-help-t3674133
Related
Hello,
my Pixel XL came from T-Mobile Germany.
I am in TWRP alpha2 and SR4-SuperSU-v2.78-SR4.
My Pixel XL is on NDE63H.
I logged the OTA download process used the link in there and got now the 68MB small OTA.zip.
Can I use TWRP and this small update OTA to update to NDE63U,
or do I need to use the large 850MB OTA file from the google develope site to do so -> marlin-ota-nde63u-56d5b07a.zip?
I think I will loose root by using the large one, but will I loose TWRP as well?
My preference would be to use the small one, but will it work via TWRP and will I loose root as well or will this only update the necessary files?
Any help is highly appreciated.
mancman
I haven't tried it on the pixel, but on my previous Nexus device (N6), the small OTA would fail if the devices was rooted or had any changes to the system partition - that's because the small OTA was an incremental update, and was checking to see if the system partition was modified in any way before applying the OTA.
The full OTA would work - but you would lose the root/TWRP. Reinstalling TWRP is just a fastboot command away, so why is that a big deal?
Hello jj14,
I tried it.
First within TWRP and then by sideload and both failed with the same error.
I first needed to get a newer version of adb, but it failed as said above as well via sideload.
See error message here in the attached picture.
Any hint?
As far as that error, it means the binary update files are missing. That could be because the structure of OTA's changed. Without seeing the OTA I cannot say for sure. I would post that screenshot in the twrp thread and ask @Dees_Troy what he thinks.
Hello Scott,
thanks for your answer.
I wrote Dess a message.
Attached 2 screenshots which show what is in the zip from the OTA file and one for the comparison to a Nexus 10 zip,
you see that the update-binary is missing, so Goggle has changed things here as you postulated.
Thanks,
mancman
I assume you are trying to sideload the full OTA file. If so, what error did you get using the ADB sideload? (yes, you will need the newest version of ADB - download from the Google developers site). TWRP is still very new, so there may still be some bugs to address - Dees is pretty good about quick updates/fixes though.
I may be wrong here but shouldn't you flash back stock recovery before applying stock ota ??
I purchased a Z2 Play (Freedom Mobile in Canada, XT1710-01, retca channel). I proceeded to unlock the bootloader, install TWRP and root (Magisk 13.3, then upgraded to v14). However, doing this obviously makes installing OTAs not possible. Unfortunately I didn't do a stock backup of anything before doing the above.
From my understanding, installing OTAs requires stock recovery and an unmodified system partition. So, I tried installing just the stock recovery from the RETAIL stock ROM (from here. Then I did a full uninstall of Magisk, expecting (hoping) that would put my phone back into a state (unmodified system partition) that would allow me to install OTA updates.
I presently have an OTA update pending (NPS26.118-15 which has July security updates and Moto Mods 2.0 support, among other things).
However, when I try to install it, my phone reboots and it displays the "Installing system update" screen for a few seconds, then goes to an "Error!" screen, with the green android laying down and an red exclamation mark coming out of his belly. OTA failed.
I am able to restart and boot back into Android, and get the message indicating the OTA failed and nothing was changed.
Can anyone offer any other thoughts or help on things I could try to get the OTA updates to apply? (Just for funsies, I did also try Chainfire's Flashfire, but had no luck with that either.)
I have Z2 Play from Freedom Mobile as well. I'm currently at NPSS26.118-19-4. I was bootlooping into TWRP and I had no other choice and took the risk and chanced flashing the ROM from Junior Passos over at his site. Can't post links but Google motozbrasil.
It says XT1710-07 but it's working fine for me. I'm rooted and passing SafetyNet as well. The ROM automatically detected and says retca on software channel and changed the last bit of string on the baseband as NA_Cust.
I can confirm it works but like I said was my only option. Please be careful. I'm not responsible if it doesn't work for you.
Edit: My SKU in Hardware Information displays XT1710-01 as well not XT1710-07.
atheart said:
I have Z2 Play from Freedom Mobile as well. I'm currently at NPSS26.118-19-4. I was bootlooping into TWRP and I had no other choice and took the risk and chanced flashing the ROM from Junior Passos over at his site. Can't post links but Google motozbrasil.
It says XT1710-07 but it's working fine for me. I'm rooted and passing SafetyNet as well. The ROM automatically detected and says retca on software channel and changed the last bit of string on the baseband as NA_Cust.
I can confirm it works but like I said was my only option. Please be careful. I'm not responsible if it doesn't work for you.
Edit: My SKU in Hardware Information displays XT1710-01 as well not XT1710-07.
Click to expand...
Click to collapse
That's great to hear. I've seen his ROM, but had concerns about flashing it on our device. Glad to hear, I'll probably give that a go, then.
Just to finish off this thread, I successfully installed @Junior Passos's ROM and everything is working great.
I didn't root or install TWRP (left it at stock) this time, I'm curious if future OTAs will work for me now.
Thanks for sharing this. I was wondering why "nobody" has tried to flashed the RETAIL stock image (which came from a motorola server) and is mirrored at
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
?
romhippo.com said:
Thanks for sharing this. I was wondering why "nobody" has tried to flashed the RETAIL stock image (which came from a motorola server) and is mirrored at
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
?
Click to expand...
Click to collapse
It's one and the same. On Junior's site, the download link he has links the the lolinet.com one.
(http://motozbrasil.blogspot.ca/2017/09/firmware-moto-z-play-xt1710-07-firmware.html)
Junior just has helper files and instructions to make it easy.
TravellingGuy said:
It's one and the same. On Junior's site, the download link he has links the the lolinet.com one.
(http://motozbrasil.blogspot.ca/2017/09/firmware-moto-z-play-xt1710-07-firmware.html)
Junior just has helper files and instructions to make it easy.
Click to expand...
Click to collapse
Ok, great. I guess, when I read "Junior's site" , I had this site in mind at https://www.androidfilehost.com/?w=files&flid=195559&sort_by=date&sort_dir=DESC which basically contains the "stock backup" of his XT1710-07 phone.
I should not have skimmed your posts. My bad
TravellingGuy said:
Just to finish off this thread, I successfully installed @Junior Passos's ROM and everything is working great.
I didn't root or install TWRP (left it at stock) this time, I'm curious if future OTAs will work for me now.
Click to expand...
Click to collapse
That's good to hear man. Now that's two so far that were successful including mine. Seems like ROM is cross compatible.
atheart said:
That's good to hear man. Now that's two so far that were successful including mine. Seems like ROM is cross compatible.
Click to expand...
Click to collapse
I also tried this RETAIL image, and it seems cross compatible in my case too. I flashed only the "service.xml" with RSD lite and did not lose any data. Software channel and model did not change either.
TravellingGuy said:
Just to finish off this thread, I successfully installed @Junior Passos's ROM and everything is working great.
I didn't root or install TWRP (left it at stock) this time, I'm curious if future OTAs will work for me now.
Click to expand...
Click to collapse
An update from me on this. I mentioned I installed Junior Passos's ROM (the August update one), but then left my phone at stock (no root, no TWRP) to see if OTAs would work. Good news, I got the notification about the September OTA update yesterday, and I was able to download and install it with no issues! Sweet.
TravellingGuy said:
An update from me on this. I mentioned I installed Junior Passos's ROM (the August update one), but then left my phone at stock (no root, no TWRP) to see if OTAs would work. Good news, I got the notification about the September OTA update yesterday, and I was able to download and install it with no issues! Sweet.
Click to expand...
Click to collapse
Do you have updates in English after doing all of this? I just got my Z2 Play from Amazon today and noticed that it is on the RETLA channel and all of my system updates are in Spanish. The phone still functions in English, and so far I have found nothing else that is not in my language. However, it kind of bothers me that my updates are not tied to my region, so I'm really hoping that there is a way to get my phone on the RETUS channel, or at the very least, get my update notes in my language.
So it looks like the major feature added is the Google Play assistant, which I don't even use on my phone.
But also, I believe the latest version of YouTube will be the stock app, which I just don't like.
I am rooted, which I realize will go away after the upgrade. But also, I don't have anything installed that requires root really. I wanted to take advantage of some xposed features, but apparently there is no version of the framework that supports nvidia shield tv 5.2?
So is it worth upgrading right now? Has anyone tried it? Anything notable worth upgrading for?
I'm in the same situation (rooted) as you. I tried to update, but I end up in TWRP and I don't know what to do from there. If I boot system it just start up as normal and ask me again to update.
Any ideas? Anyone?
What to do, what to do?
Kickasscowboy said:
I'm in the same situation (rooted) as you. I tried to update, but I end up in TWRP and I don't know what to do from there. If I boot system it just start up as normal and ask me again to update.
Any ideas? Anyone?
What to do, what to do?
Click to expand...
Click to collapse
Most likely have to wait for the developers image .
jionny said:
Most likely have to wait for the developers image .
Click to expand...
Click to collapse
And flash through FlashFire
orificium said:
So it looks like the major feature added is the Google Play assistant, which I don't even use on my phone.
But also, I believe the latest version of YouTube will be the stock app, which I just don't like.
Click to expand...
Click to collapse
I have a stock shield (not rooted), but had backed off the YouTube app to be the old one (the one that works with secondary accounts).
I let it upgrade and it did not force a YouTube update. After it finished, I'm still running YT 1.3.11. So you should be okay there.
Of course other than Google Assistant, I haven't found much new. What I really want is for Google Assistant to work with Google Play Music, but it doesn't do that (yet?).
I'm in the same boat as you guys. Currently rooted and debating the upgrade. I would think that we could update via flash fire if someone knows where the ota is stored once it downloads.
Sent from my Pixel XL using Tapatalk
I hear you guys. I will wait for OTA update to be downloadable or I might even consider returning to stock. I really don't have any use for root now.
FYI, Doesn't work with flashfire.
https://m.imgur.com/a/4ZKy6
n1gh7mar3 said:
FYI, Doesn't work with flashfire.
https://m.imgur.com/a/4ZKy6
Click to expand...
Click to collapse
That's not a developer image right? wouldn't think it would work unless it is the developer image or your bootloader is locked
I got mine to update even though its rooted.
After it finished downloading, it rebooted into twrp and installed the update automatically with no issues.
I did however get some issues after it finished updating.
The recovery/twrp is gone and cant boot into that anymore.
Root is of course gone.
And now im also just getting a black wallpaper in the launcher instead of the default nvidia one.
WisdomWolf said:
I'm in the same boat as you guys. Currently rooted and debating the upgrade. I would think that we could update via flash fire if someone knows where the ota is stored once it downloads.
Click to expand...
Click to collapse
data/data/com.nvidia.ota/app_download
jionny said:
That's not a developer image right? wouldn't think it would work unless it is the developer image or your bootloader is locked
Click to expand...
Click to collapse
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
n1gh7mar3 said:
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
Click to expand...
Click to collapse
Sorry I meant the developer rooted image that Nvidia usually releases shortly after a upgrade that you can flash over a unlocked bootloader and root and keep root
jionny said:
Sorry I meant the developer rooted image that Nvidia usually releases shortly after a upgrade that you can flash over a unlocked bootloader and root and keep root
Click to expand...
Click to collapse
I totally understand what you mean, I was already on 5.2.0 developer image, so I assume if presented with an OTA it's of the same type.
n1gh7mar3 said:
I totally understand what you mean, I was already on 5.2.0 developer image, so I assume if presented with an OTA it's of the same type.
Click to expand...
Click to collapse
No you have to get that from Nvidias site however last time I checked it was not up yet
n1gh7mar3 said:
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
Click to expand...
Click to collapse
you have to flash all the files inside, not only recovery. (nv-recovery-image-shield-atv-5.2.0.zip)
now it worked
Screen flickers
My shield got the latest upgrade (non root) and now my screen flickers from time to time. Any known solution to this issue ?
Tifulb said:
My shield got the latest upgrade (non root) and now my screen flickers from time to time. Any known solution to this issue ?
Click to expand...
Click to collapse
I've seen a few fixes for screen issues, either making sure in advanced display resolution settings things are correct, or disabling/renabling the CEC in settings.
You may want to check out the nvidia geforce forums thread, I'd probably start out middle to last several pages (assuming you read this soon, in a few days you'll just have to take a guess as there will be way more pages) https://forums.geforce.com/default/.../shield-experience-upgrade-6-0-for-shield-tv/
I think there's a post about chroma clipping which may be what yours is doing, but it could be some of the HDR stuff or something with the HDMI or CEC issues for all I know.
Hi,
i have a 2015 Shield (root) with 5.2 image.
I would back to stock image and unroot my shield.
I have download the "nv-recovery-image-shield-atv-5.2.0".
my approach.
*** Prerequisites:
1. Ensure that the bootloader is unlocked (see above step)
*** Flashing instructions:
1. Execute these commands on the host PC:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Is this the right way?
Thanks!
OTA zip shield 2015 6.0
if someone need:
Original ota zip for Shield TV 2015 (non pro) 5.2 -> 6.0
https://mega.nz/#!BChlSbaR!em9CV5PoRzalWnMWf7iqAj4oVeDQqLhrz_Q1GGXy0Ug
I've got the RETUS model, XT1710-01, of the Moto Z2 Play, and while I was successful in unlocking the bootloader and installing Magisk (I still have stock recovery), I have been unable to install the OTA updates. Even though they may not be vital to the device's functionality at the moment, I was hoping someone might be able to inform me as to how I might go about installing an OTA update.
I have seen that several other users have posted about the repository here that has the firmware ZIP files for our model phone.
Is there a set of steps I could follow in order to flash this update?
Do not install OTA with custom recovery.
Try this:
https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153
read care fully. it works well me on 09
Please anyone upload motorola update services apk from oreo rom
It is named ota in system partition
Search it with xplore and upload it
It is the easiest way to get oreo
#help
Tried it and not working
Anyone tried this idea?
ahmedAZ said:
Please anyone upload motorola update services apk from oreo rom
It is named ota in system partition
Search it with xplore and upload it
It is the easiest way to get oreo
#help
Click to expand...
Click to collapse
Updating the app won't get you oreo
Updates are pushed out in regions - they are geo restricted & also based on your current firmware
If you really want oreo the firmware from india/Brazil has been posted - just flash it via fastboot or just wait until they push it to your country & firmware version
Hey I was wondering, my wife just got her OTA notification for oreo and we have identical g5's cedric. I wanted to try to capture it on my phone so I restored to 137-93-14 and checked for updates.. It doesn't detect the ota.. Is it possible that having an unlocked bootloader and root prevents me from receiving it? I think I read somewhere that unlocked phones have it last. My wife's phone is totally stock untouched.
The reason I wanted to capture it even though the ota is everywhere on XDA is that I tried the twrp flashable oreo on my device and it didn't work. Which made me wonder if our update has something different than other phones (probably not) cause it seems that I'm the only one on the twrp oreo thread that hasn't been able to flash that update.
Btw I know I can't install official ota with my modified system I wasn't going to try it