Related
I keep checking for the update to 5.0.x and it keeps saying device is upto date...
But I think 5.0.x has rolled out right? Any ideas how to get it updated?
You could sideload it via ADB.
fury683 said:
You could sideload it via ADB.
Click to expand...
Click to collapse
Thanks found an article on how to do it. I assume the device is "Razor"? And the current is 5.0.1?
I think I need to do OTA KTU84P -> LRX21P
then have to do LRX21P -> LRX33C
Sound right?
https://www.google.com/?q=nexus 7 sideload 5.0.1
Download the OTA, put the device in ADB OTA mode and follow the instructions. It will only work on a 100% stock unmodified system.
fury683 said:
https://www.google.com/?q=nexus 7 sideload 5.0.1
Download the OTA, put the device in ADB OTA mode and follow the instructions. It will only work on a 100% stock unmodified system.
Click to expand...
Click to collapse
Google officially pushed it out right? Or is it being held back for some reason?
It did release, its just slow pushing out to all devices as there are still kinks with the update. Google usually pushes updates in waves, its just taking longer this time around. You can sideload it. And fury683 is incorrect in the device needing to be unmodified, at least in terms of root it is okay if your tablet is rooted. Just make sure you have an unlocked bootloader and adb devices and fastboot devices detects your tablet before sideloading.
renold458 said:
It did release, its just slow pushing out to all devices as there are still kinks with the update. Google usually pushes updates in waves, its just taking longer this time around. You can sideload it. And fury683 is incorrect in the device needing to be unmodified, at least in terms of root it is okay if your tablet is rooted. Just make sure you have an unlocked bootloader and adb devices and fastboot devices detects your tablet before sideloading.
Click to expand...
Click to collapse
If there are changes to your /system or /recovery (very common when the device is rooted) the OTA will likely fail verification, which it did for me when I tried. I had to use the factory images to go from 4.4.4 and 5.0 and eventually 5.0 to 5.0.1.
You can remove the -w flag from the flash-all.bat file in the factory images zip to prevent it from wiping data and it takes about 2 minutes to flash everything.
Well yes in terms of OTA it will most likely not work,I meant in terms of sideloading the image it is okay to be rooted and have a custom recovery. However as a note, my custom recovery and root was removed after sideloading, so I had to reroot and reflash TWRP as my tablet no longer had a recovery image.
renold458 said:
Well yes in terms of OTA it will most likely not work,I meant in terms of sideloading the image it is okay to be rooted and have a custom recovery. However as a note, my custom recovery and root was removed after sideloading, so I had to reroot and reflash TWRP as my tablet no longer had a recovery image.
Click to expand...
Click to collapse
I think I will just sit tight. I am told by google that they are still rolling out...
Hi, I have a Nexus 5X with unlocked bootloader and with rooted. Since some days ago, I have a notification with a security update, but with the custom recovery it is not automatically installed.
Is there any way to install this OTA updates?
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
martyfried said:
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The updates will not install on a rooted phone. Updates check if your software is stock and if not it will not update, includes recovery partition. Your best bet is to just update the ROM you're on. The ROM developer typically updates his base on a regular basis especially if it's one of the more active ones like Pure Nexus or Chroma among others.
If you really need Google updates to happen then you must go back to stock image and updates will work then.
Edit #2: If you are rooted but stock w/ TWRP, just unroot and flash stock recovery and the updates will work or you can ADB sideload the update zip w/ TWRP.
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The link I provided has explicit instructions. I remembered wrong, though. You don't need TWRP, you need to do it in Fastboot mode, so you need to find the latest Fastboot program, or install the Android SDK. Then follow step 10 in the link I provided.
I guess I have something to do when I get home. No update to platform tools.
https://developers.google.com/android/images
https://developers.google.com/android/ota
All seems good so far. Supposedly the charging issue is fixed...
Nothing via OTA update
Only images are available
Just get it on OTA via US IP (vpn), but update dont star
Im rooted, is't interfering??
These wouldn't allow a user to downgrade, correct? Like, to 7.1.0, use dePixel8, and then root?
Can the updates be installed out of sequence? I'm currently on the Oreo March update, can I install the May update without installing April first?
moyses said:
Nothing via OTA update
Only images are available
Just get it on OTA via US IP (vpn), but update dont star
Im rooted, is't interfering??
Click to expand...
Click to collapse
if you're rooted, then the ota won't apply via the google system update. your rom has to be completely stock in order for it to work. your bootloader can be unlocked. i don't know about flashing the ota via twrp. i've never done it.
Bramton1 said:
These wouldn't allow a user to downgrade, correct? Like, to 7.1.0, use dePixel8, and then root?
Click to expand...
Click to collapse
correct, they will not allow a user to downgrade. there isn't a downgrade method available for locked bootloaders.
Gulfstream 650 said:
Can the updates be installed out of sequence? I'm currently on the Oreo March update, can I install the May update without installing April first?
Click to expand...
Click to collapse
if you flash the full factory image, yes, you can flash the may update over the march update. i don't know about the otas though. i always flash the full factory image.
Does anyone know if I can flash the OTA on my nonrooted Pixel XL through TWRP ?
What is the best way to wipe+install the new Android P update on a Verizon Pixel 2 XL(locked bootloader)? I am on the Android P Beta so the Android P full release is showing in system updates but is it better to flash the OTA via USB instead or just update using the OTA system update and then erase all data?
Just update through the system settings and then do a factory reset. Unless you really want to unlock your bootloader.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
paradeedle said:
What is the best way to wipe+install the new Android P update on a Verizon Pixel 2 XL(locked bootloader)? I am on the Android P Beta so the Android P full release is showing in system updates but is it better to flash the OTA via USB instead or just update using the OTA system update and then erase all data?
Click to expand...
Click to collapse
Since you are looking for a fresh start anyway and willing to wipe your data, one way is to just do a factory data reset first, and then flash the OTA via fastboot. Full OTA's are already posted and available. Best of luck. :good:
v12xke said:
Since you are looking for a fresh start anyway and willing to wipe your data, one way is to just do a factory data reset first, and then flash the OTA via fastboot. Full OTA's are already posted and available. Best of luck. :good:
Click to expand...
Click to collapse
Perfect. Flashing the OTA via fastboot still allows OTA monthly updates as well then?
paradeedle said:
Perfect. Flashing the OTA via fastboot still allows OTA monthly updates as well then?
Click to expand...
Click to collapse
Yes, because it is a full OTA image. Many people with locked bootloaders have flashed full OTA's when their unit stopped receiving them manually to force them back on track. The full OTA is almost as big as the complete image > 1GB. Not to be confused with the incremental OTA ~ 50MB. Best of luck.
xringo said:
Just update through the system settings and then do a factory reset. Unless you really want to unlock your bootloader.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
Since when can you unlock the VZ model? I know I haven't spent as much time on the forums since bring relegated back to the land of the rootless, but I haven't noticed any big announcements anywhere. That thread seems to be for the Google version?
I'm on the stock ROM (Build number: OPNS27.76-12-22-3), rooted via Magisk and have the latest TWRP as my recovery. Say, an OTA update arrives (hopefully) in the future, could I just sideload it from my computer via adb? I know that downloading the file and installing it using the phone won't work as I'm on TWRP (it requires stock recovery). Erfan Abdi's website allows the download of the OTA zip from Moto's servers if one wants to sideload it via adb (https://erfanoabdi.000webhostapp.com/). If not, how can I apply the OTA update?
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
jst98 said:
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
Click to expand...
Click to collapse
So I should flash the stock recovery back and then sideload the OTA?
djdelarosa25 said:
So I should flash the stock recovery back and then sideload the OTA?
Click to expand...
Click to collapse
flash stock, take the ota's via ota, and then mod system. At least that's what I do. pita but it works. I back up with TBPro and copy backup to PC (ota clears internal storage) before I do that so rebuild is pretty quick.
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
jst98 said:
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
Click to expand...
Click to collapse
I have to flash stock to take ota. ymmv. Let me know if AUG is out.
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
KrisM22 said:
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
Click to expand...
Click to collapse
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
jst98 said:
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
Click to expand...
Click to collapse
a) right. what I said. uninstall magisk is dirty - it doesn't clean everything up..
b) I could suggest TBPro to back up your system. Then be sure to copy that backup to your PC because flashing the stock will wipe internal storage. Then flash stock. Then use TBPro to restore stuff. At least that's sortof what I do.
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
what security date are you on? Thanks.
KrisM22 said:
what security date are you on? Thanks.
Click to expand...
Click to collapse
june
JonasVFC said:
june
Click to expand...
Click to collapse
Thanks. That's what I'm on. I was wondering if Aug was out...
KrisM22 said:
Thanks. That's what I'm on. I was wondering if Aug was out...
Click to expand...
Click to collapse
Damn, Motorola's taking so long again.
djdelarosa25 said:
Damn, Motorola's taking so long again.
Click to expand...
Click to collapse
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
August security patch is out so I tried these steps.
It didn't work. While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened. Keep in mind, I flashed the Magisk and Xposed uninstallers and cleared Dalvik and cache before the attempt to sideload.
I just flashed the original June build (omitting the 'fastboot erase userdata' command to save myself from a potential pain in the ass) and then did I proceed to sideload the update via adb. After that, I flashed the latest TWRP and rooted using the latest Magisk (and f2fs fix as well). My data is intact (except for the root modifications and Magisk modules) but that is miles better than starting from scratch off a factory data reset.
I guess I answered my own question, then . You can't
KrisM22 said:
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
Click to expand...
Click to collapse
lol we are done. nothing new will come to us (owners of z1 play)
JonasVFC said:
lol we are done. nothing new will come to us (owners of z1 play)
Click to expand...
Click to collapse
yeah, lol, I'm playing with Pie. - Nothing new... HAH! silly rabbit.
djdelarosa25 said:
While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened.
Click to expand...
Click to collapse
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
tag68 said:
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
Click to expand...
Click to collapse
Nope, sorry. Though, I failed to mention that I did flash the original boot.img after encountering the error and tried again. You guessed it, it still failed. Maybe try flashing both boot and oem to see if it would work?