Related
How can I safely update 4.5.91 to latest ota? My bootloader is locked, my phone is rooted with something called fastboot.
The ota update notification is getting annoying. Please help.
Sent from my MB860 using XDA
Just an FYI, "fastboot" is a protocol used to flash system files:
http://www.androidcentral.com/android-z-what-fastboot
Either way, if you want to stop the notifications you can use a root file manager (such as Root Explorer) to freeze the "Updater.apk" (or Upgrader.apk?) in the /system/app folder by adding a ".bak" to the end and rebooting.
You can maybe try "rootkeeper" and do the OTA but I don't know the extent of your modifications so I really can't recommend that.
Or you can take the leap and unlock the bootloader and flash custom ROMs.
nekrosoft13 said:
How can I safely update 4.5.91 to latest ota? My bootloader is locked, my phone is rooted with something called fastboot.
The ota update notification is getting annoying. Please help.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Or he can use the Automatic Update (PC Only) from here if he wants to stay stock:
http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
That will flash the 141 sbf onto your phone so you will lose root
Then you can re-root using the preinstall method using Fastboot again.
or just root / unlock and load a custom rom They are FAR superior that any stock atrix firmware! period!
Sent from my MB860 using Tapatalk
ok, i was able to unroot and run OTA using these directions http://forum.xda-developers.com/showpost.php?p=22723943&postcount=15
how can i root now? is there any method other then preinstall method?
I just received the Stagefright update patch this morning. The notification mentioned performance and stability improvements along with the Stagefright patch. For those of you wanting to dig through it and try to port it to a flashable zip for rooted users, here it is.
https://drive.google.com/file/d/0B0G3PnBHJjXmdno0cjhod3NNOTA/view?usp=sharing
I am currently running stock, unrooted but with TWRP installed. I had to extract the recovery from the zip file and flash via fastboot as the patch wouldn't flash with TWRP. It took a while to boot due to rewriting the cache, but it's finally up and running. I don't see real noticeable differences, either in look or performance. As long as the patch works, guess I'm OK.
Is there anyway to stop the update notifications?
Sent from my 710C using Tapatalk
I had it too, a5_dwg .. but I'm rooted with TWRP xD
so I'm ganna wait for the flashable zip if anyone still care about this phone anyway to do it
Also rooted and waiting for a .zip
YouArePoop said:
Is there anyway to stop the update notifications?
Sent from my 710C using Tapatalk
Click to expand...
Click to collapse
I froze the updater apk with link2sd....that seemed to do the trick
Sent from my 710C using Tapatalk
Anyone have an unrooted stock lollipop twrp or cwm backup? A5CHL. I want to OTA to this version but I can't go back to stock. the official lollipop RUU keeps failing saying, "RomTool.exe has stopped working." then I have to fastboot reboot to the older version.
I looked in the update, and it appears to be a bunch of patches. I have two ideas for how to make it work:
1 - Figure out how it checks the recovery version and chop that part out.
2 - make a copy of /system on my sdcard, change every instance of /system to /[sdcard-path]/system in binary-script, run script, then repack that as an update.
Sound about right, anyone? I'm tempted to try this out.
Sent from my 710C using XDA Free mobile app
The RUU.exe from HTC.com for a5_chl now includes this patch. So if people don't mind wiping their phone running the .exe and going completely back to stock, the option's there. My laptop still says, "romtool.exe has stopped working." So I'm screwed either way, an OTA or RUU.
I was curious if there is a way to take an ota on my stock rooted 6P with TWRP recovery.
I presume flashing the ota zip won't work if system has been modified in any way, however I did use systemless root... Can I flash the ota zip in TWRP?
P.S. I'm familiar with the fastboot process, done it quite a few times. Just curious if I'm going to have to do that each month for a security update.
Sent from my Nexus 6P using Tapatalk
GatorsUF said:
I was curious if there is a way to take an ota on my stock rooted 6P with TWRP recovery.
I presume flashing the ota zip won't work if system has been modified in any way, however I did use systemless root... Can I flash the ota zip in TWRP?
P.S. I'm familiar with the fastboot process, done it quite a few times. Just curious if I'm going to have to do that each month for a security update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The OTA installer looks at system, boot, and recovery. If there is any modification from stock, it will abort installation. So as long as you want to run with TWRP and a rooted system, you will have to fastboot flash the factory image files.
Is there somewhere where I can find the ota zip? I'm still stock.
cam30era said:
The OTA installer looks at system, boot, and recovery. If there is any modification from stock, it will abort installation. So as long as you want to run with TWRP and a rooted system, you will have to fastboot flash the factory image files.
Click to expand...
Click to collapse
Modifying the build prop for wifi tether and unlocked bootloader will tasty flag the ota update via flashing or waiting for ota being pushed?
Sent from my Nexus 6P using Tapatalk
imex99 said:
Modifying the build prop for wifi tether and unlocked bootloader will tasty flag the ota update via flashing or waiting for ota being pushed?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Unlocked bootloader has no effect. Build.prop edits will cause OTA install to abort.
cam30era said:
Unlocked bootloader has no effect. Build.prop edits will cause OTA install to abort.
Click to expand...
Click to collapse
So, just delete build prop edit, can flash ota zip with twrp, reboot, edit build prop and reboot again?
Trying to keep pay working...
Sent from my Nexus 6P using Tapatalk
imex99 said:
So, just delete build prop edit, can flash ota zip with twrp, reboot, edit build prop and reboot again?
Trying to keep pay working...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No. OTA can only be ADB sideloaded via stock recovery.
Hi guys,
My Nexus 6p got softbricked.
I have access to fastboot and stock recovery.
My bootloader is locked.
To fix this, I'm attempting to find the OTA zip that i can flash to revert to 6.0.1 from Nougat build: NRD90U
Can anyone help?
ronald5 said:
Hi guys,
My Nexus 6p got softbricked.
I have access to fastboot and stock recovery.
My bootloader is locked.
To fix this, I'm attempting to find the OTA zip that i can flash to revert to 6.0.1 from Nougat build: NRD90U
Can anyone help?
Click to expand...
Click to collapse
You need to download the factory image not the OTA. You will need to save your internal storage. This will return your phone to 6.0.1.
https://developers.google.com/android/nexus/images
I tried that but I get errors since the bootloader is locked
Sent from my SM-N920T using Tapatalk
Nexus Root Toolkit is your solution.
I tried the toolkit, i couldn't find the exact OTA zip made to revert build NRD90U to marshmallow.
I kept getting errors sideloading OTA (either error: status 7 or signature verification failed)
Sent from my SM-N920T using Tapatalk
ronald5 said:
I tried that but I get errors since the bootloader is locked
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Did you follow the steps to unlock the bootloader as described on the page ?
I can't unlock the bootloader since Adb debugging and Oem unlock were not turned on
Sent from my SM-N920T using Tapatalk
ronald5 said:
I tried the toolkit, i couldn't find the exact OTA zip made to revert build NRD90U to marshmallow.
Click to expand...
Click to collapse
1. Use the toolkit to only instal drivers.
2. On the Google site all OTA files are full updates, you can flash any of them, you don't need it in order
3. My advice, don't go back to Marshmallow, but flash the OTA for the 7.1 preview, it's more stable, and uses less battery than 7.0
The official OTA images:
https://developers.google.com/android/nexus/ota#angler
The preview OTA image:
https://developer.android.com/preview/download-ota.html
When i attempt to flash the OTA, this is what I get:
Opening update package...
Verifying update package...
E: Footer is wrong
Update package verifiable took 0.5 s (result 1)
E: Signature verification failed
Installation aborted.
Sent from my SM-N920T using Tapatalk
If your bootloader is locked then there isn't anything u can do.. Try returning it if possible
Sent from my Pixel XL using Tapatalk
There must be a way. Hopefully someone has achieved this and can help.
Sent from my SM-N920T using Tapatalk
ronald5 said:
There must be a way. Hopefully someone has achieved this and can help.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
If your BL is locked and you haven't enabled OEM unlocking and debugging, you are out of luck. You are effectively hard bricked.
Sent from my Nexus 6P using Tapatalk
You can flash an OTA even if the bootloader is locked. It seems that the download was unsuccessful, and the file is corrupted. Try to download it again.
istperson said:
You can flash an OTA even if the bootloader is locked. It seems that the download was unsuccessful, and the file is corrupted. Try to download it again.
Click to expand...
Click to collapse
He can't use an OTA to revert to MM from N, which is what he is trying to do. And, he could only take an OTA normally or via ADB sideload. Flashing via fastboot wouldn't work.
I tried both: flash.all.bat through Fastboot and sideload a zip through adb in stock recovery... neither worked for me
Sent from my SM-N920T using Tapatalk
Link to the developer Preview for anyone interested
https://developer.android.com/preview/download.html#top
I'm currently rooted, with TWRP. So ideally how to install and keep everything and I assume you just flash supersu.zip to root again.
TIA.
flashfire.
Thanks, just tried, but it doesn't seem to recognized this zip from the link above
angler-npf26f-factory-0cd1829d.zip
Is there a different zip to flash?
install it as firmware
Use fastboot and to save your data, don't flash userdata.img.
https://www.youtube.com/watch?v=dsKn2E68A0M
Quick q on the subject. Twrp, rooted, dp1, modded build.prop, flashed Pixel bootanimation and navbar buttons. I suppose I can't use flashfire, right?
Puck24 said:
Quick q on the subject. Twrp, rooted, dp1, modded build.prop, flashed Pixel bootanimation and navbar buttons. I suppose I can't use flashfire, right?
Click to expand...
Click to collapse
I have the same setup and also want to know how to flash without losing anything. Also would rather not adb. Will flashfire do this without losing root?
Also, I went to the OP link to get the ota, and it's just a Google page on how to test an update. Where do I get the update file?
Same here.
Sent from my Pixel XL using XDA-Developers mobile app
I actually got the OTA notification sometime in the last 8 hours while I was asleep. Saw some1 posting the link in the General section, I think
I also have (had) all the pixel goodies installed and flashed the OTA with FlashFire. Now everything is gone
I used FF. If you unchecked recovery and check modem, you'll keep recovery and root. Pixel goodies are gone, but easy to reflash
Confirm: you loose Pixel stuff but just reflash, only strange thing is that I had to flash Pixel Launcher thru twrp as with FlashFire it was not working.
Did you flashfire the OTA or the Factory Image of the DP2?
Enviado de meu Pixel XL usando Tapatalk
Factory image from here
https://developer.android.com/preview/download.html#device-preview
Carterman32 said:
I used FF. If you unchecked recovery and check modem, you'll keep recovery and root. Pixel goodies are gone, but easy to reflash
Click to expand...
Click to collapse
You did put the factory image on your nexus and then press the + button and flash firmware? Is that it? And then you can select to keep your datas and root?
And in order to keep TWRP, do I uncheck recovery or it will keep TWRP anyway?
Thanks in advance.
I unzipped and flashed just system.img in TWRP, followed by SuperSu, and then modified the vendor/build.prop to match the system/build.prop to keep from getting the "internal problem" alert. Maybe not the simplest method, but worked fine.
Sent from my Pixel XL using Tapatalk
timosuomi said:
I unzipped and flashed just system.img in TWRP, followed by SuperSu, and then modified the vendor/build.prop to match the system/build.prop to keep from getting the "internal problem" alert. Maybe not the simplest method, but worked fine.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Unless you have a specific desire not to do this, flash the matching vendor.img in TWRP. This is tied to that "internal problem" warning because of the proprietary drivers included in the file.
Also, I do not recommend flashing just the system.img for every update. You may run into a non functional camera when Google releases an OTA that requires the latest boot and vendor to be installed.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Unless you have a specific desire not to do this, flash the matching vendor.img in TWRP. This is tied to that "internal problem" warning because of the proprietary drivers included in the file.
Also, I do not recommend flashing just the system.img for every update. You may run into a non functional camera when Google releases an OTA that requires the latest boot and vendor to be installed.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Good call. I'm just coming from a Nexus 6, and I don't recall dealing with vendor.img with that or previous Nexii.
Sent from my Pixel XL using Tapatalk
timosuomi said:
Good call. I'm just coming from a Nexus 6, and I don't recall dealing with vendor.img with that or previous Nexii.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Ahh, that makes sense now. The vendor partition was originally part of the system. The Nexus 9 was the first Android device to feature a separate vendor partition and both 2015 Nexus devices launched with this separate partition.
Flash boot, system, and vendor each month OR whenever you move to a different month's OTA. With custom roms, just flash the vendor and custom rom. You can check /vendor/build.prop to see which vendor is currently installed.
Sent from my Nexus 5X using Tapatalk