Related
I have pointed this out in several places, but I wanted to make a thread about it so that it gets more widespread attention.
When the 5.1 update is released, if instead of taking the OTA you use Motorola Device Manager to update, you will have a copy of the 5.1 fxz for your device on your computer. It will be in the folder c:\programdata\motorola\SUE\firmwares if you have a PC.
If the OTA has already begun to download on your device, then MDM won't update you b/c it will say there is an update in progress. So if you are rooted, you must delete or freeze the MotorolaOTA app. If you are not rooted, I think there may be some way to avoid the OTA but idk, you would have to read up on it. I think you may be able to wipe your data partition and/or cache if the download has begun in order to erase it, idk.
Thanks for the info. Will give it a try.
bumping this up b/c 5.1 is coming soon!!!!
JulesJam said:
bumping this up b/c 5.1 is coming soon!!!!
Click to expand...
Click to collapse
Any link that says so?
Sent from my XT1095
Hopefully there's some Verizon love
AGISCI said:
Any link that says so?
Click to expand...
Click to collapse
http://www.droid-life.com/2015/05/0...droid-5-1-updates-here-are-the-release-notes/
Why? What is wrong with ota?
lobango said:
Why? What is wrong with ota?
Click to expand...
Click to collapse
Nothing is wrong with it. The point in getting the fxz is that it will be a full image that we can share.[emoji2]
Sent from my XT1095
i saw this on gsm arena.
http://www.gsmarena.com/motorola_posts_android_51_release_notes_for_1st_and_2nd_gen_moto_x-news-12165.php
nevermind
bump!
Would it possible to use that to update the soak test (23.1.28) to 5.1? Like just let it update normally, or pull system.img and boot.img and flash those through fastboot to update without it complaining about wrong firmware?
jcracken said:
Would it possible to use that to update the soak test (23.1.28) to 5.1? Like just let it update normally, or pull system.img and boot.img and flash those through fastboot to update without it complaining about wrong firmware?
Click to expand...
Click to collapse
AFAIK, MDM will not update your phone if its system shows 5.1 regardless of how you got that.
So what does it say your Android Version is in Settings -> About Phone? If it says 5.1, AFAIK, MDM will not try to update.
JulesJam said:
AFAIK, MDM will not update your phone if its system shows 5.1 regardless of how you got that.
So what does it say your Android Version is in Settings -> About Phone? If it says 5.1, AFAIK, MDM will not try to update.
Click to expand...
Click to collapse
But that shouldn't preclude the second option of manually flashing the img files, right? Can someone post the FXZ? I'd like to try this.
jcracken said:
But that shouldn't preclude the second option of manually flashing the img files, right?
Click to expand...
Click to collapse
Correct.
jcracken said:
Can someone post the FXZ? I'd like to try this.
Click to expand...
Click to collapse
Nobody has that yet. That is the whole point of this thread - to get people to use MDM so that we will have the fxz for all of the devices.
MDM won't update the devices until the OTA is pushed. But if your phone has started to download the OTA, MDM will say an update is in progress so it won't download the files.
What I am saying is that people should not take the OTA - disable MotorolaOTA - and use MDM to update to get the fxz.
bump
JulesJam said:
bump
Click to expand...
Click to collapse
You should be able to get the OTA update file using this method but I don't believe it will give a FXZ file. The OTA's generally just patch the existing file system instead of replacing it with a brand new/full image.
Steve-x said:
You should be able to get the OTA update file using this method but I don't believe it will give a FXZ file. The OTA's generally just patch the existing file system instead of replacing it with a brand new/full image.
Click to expand...
Click to collapse
No, I get the system.img, boot.img, recovery.img, gpt.bin, logo.bin, fsg.mbn, motoboot.img, and NON-HOLOS.bin and they are flashable by mfastboot. There is also an xml file that RSDLite can read.
Attached is a screenshot of the directory where you can find them:
c:\ProgramData\Motorola\SUE\Firmwares
JulesJam said:
No, I get the system.img, boot.img, recovery.img, gpt.bin, logo.bin, fsg.mbn, motoboot.img, and NON-HOLOS.bin and they are flashable by mfastboot. There is also an xml file that RSDLite can read.
Attached is a screenshot of the directory where you can find them:
c:\ProgramData\Motorola\SUE\Firmwares
Click to expand...
Click to collapse
Very cool, and very useful.
bump!
This update is known as 6.0.1 (MMB29S): https://dl.google.com/dl/android/aosp/shamu-mmb29s-factory-fc7b590e.tgz
Anyone want to confirm that we can still use systemless root for this update?
Xplicit84 said:
Anyone want to confirm that we can still use systemless root for this update?
Click to expand...
Click to collapse
why, whats the point? why wouldnt you be able to use systemless root with it?
simms22 said:
why, whats the point? why wouldnt you be able to use systemless root with it?
Click to expand...
Click to collapse
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Xplicit84 said:
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Click to expand...
Click to collapse
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Everything's fine for me.
FYI, the radio.img and bootloader.img are the same as MMB29K, so they don't need to be flashed. Boot.img and cache.img are the same size, but I'll flash them anyway. System.img is a different size, so it definitely needs to be flashed.
Looks like the kernel is the same.
Sent from my Nexus 6 using Tapatalk
anyone having trouble downloading the new system image from the site?
simms22 said:
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Click to expand...
Click to collapse
While this is true. These security updates are meant to target thing like the root exploits. So while things may still work don't be surprised if it does start needing updates each time Google pushes a security patch. It's a cat and mouse game that will be played until Google manages to lock it down to the point that it is not worth it to root.
maddoggin said:
anyone having trouble downloading the new system image from the site?
Click to expand...
Click to collapse
The factory image download was very slow. Timed out the first time. Second time it worked OK, but still took about 30 minutes.
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
tsongwh said:
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
Click to expand...
Click to collapse
I second this too. Thank you in advance
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
daimonmustdie said:
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
Click to expand...
Click to collapse
Stock w/ systemless root and Elite kernel.
To applying the update I downloaded the factory image from https://developers.google.com/android/nexus/images untar and unzip image-shamu-mmb29s.zip to get at the system.img file. Then did fastboot flash system system.img, just finished booting and and 'upgrading' my apps. It looks like something in boot.img changed too, but everything seems to be running perfectly fine without flashing it; note that I do have a custom kernel installed, so that might have something to do with it.
If you also fastboot flash boot boot.img then you will likely need to go through the root process again to modify the boot.img to allow root to work properly.
Code:
$diff shamu-mmb29k shamu-mmb29s
Binary files shamu-mmb29k/boot.img and shamu-mmb29s/boot.img differ
...
Binary files shamu-mmb29k/recovery.img and shamu-mmb29s/recovery.img differ
Binary files shamu-mmb29k/system.img and shamu-mmb29s/system.img differ
Stock ROM, TWRP
I have followed the instructions and flashed only the system.img..Nexus 6 - Unlocked, Rooted, Stock ROM, TWRP. It appears everything is running well and the Update notification hasn't appeared..this update was constantly appearing in the notification window and was reported as 5.8mb downloaded patch.
Thanks for your help.
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?
Nice find thanks
Now just need the modified boot.img for this newest build.
Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.
Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?
Can you post a link to OTA
bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.
Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.
tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.
I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.
Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
You must do the following:
1. Return to complete stock - that means get rid of root and TWRP. Best way to do that is download the factory image from Google, extract the boot, recovery, and system images from the factory image, and Flash those, for example: fastboot flash recovery recovery.img Don't flash data.img so you can keep your data.
2. OTAs depend on stock recovery to load, so now that you're back to stock, you have 2 choices. You can simply boot your phone normally, wait for the notification for the update, install it, and you're done - or, you can access android's stock recovery and side load the OTA zip using ADB. Good luck
Sent from my Nexus 6P using Tapatalk
Gamer_Josh said:
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
Click to expand...
Click to collapse
I forgot to mention that I also had TWRP recovery installed. The result was like it is with a normal OTA update, as none of my data/apps/settings were affected. Worked like a charm!
DJBhardwaj said:
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
ponzi314 said:
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
Click to expand...
Click to collapse
You are sure that you used the correct OTA file?
DJBhardwaj said:
You are sure that you used the correct OTA file?
Click to expand...
Click to collapse
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
ponzi314 said:
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
Click to expand...
Click to collapse
That's weird. It has worked for me everytime, and most users here.
DJBhardwaj said:
That's weird. It has worked for me everytime, and most users here.
Click to expand...
Click to collapse
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
tech_head said:
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
Click to expand...
Click to collapse
Sideloading the update, right?
DJBhardwaj said:
Sideloading the update, right?
Click to expand...
Click to collapse
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
tech_head said:
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
Click to expand...
Click to collapse
I also avoid using any toolkits. Yes I know they are fast and easy, and of course someone's hardwork. But I like to everything manual, same as you. :highfive:
I usually like to do things like that manually, because I like to know how things work. But I was under a bit of a time crunch at that point, so decided to try the Nexus Root Toolkit. Though I do understand the procedure of sideloading OTA updates via ADB, from researching and reading on the forums here.
Anywho, I hope you are able to get it going OP.
The OTA fixed it for me, thank you so much!
Hi there,
i try to install factory image on my nexus 6P 8.0.0 (OPR6.170623.017, Sep 2017) with the adb commands, everthing works ok but after turn on the device, the logo of starting android is moves and moves and moves and no start of the system, in the previus version it works correct, there is something on these version that makes it wrong?
secondly, i think i will downgrade to 8.0.0 (OPR6.170623.013, Aug 2017, Not for TMO/USCC/Fi), there is option to upgrade using flashfire ? if so, which version i need to download full ota image or factory image for that?
thank you
update:
so i managed to install factory image 8.0.0 (OPR6.170623.017, Sep 2017) , but when i go to settings under updates still there is update of 991MB - it's very strange.
also i need to know about the flash fire which version i need to security updates full ota image or factory image for that?
thank you
Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.
wizardwiz said:
Been answered already.
The latest is 019 and after 017 you will get that OTA of 019.
Click to expand...
Click to collapse
and where i can find these to download? it's not on the developer site,
also i have another questions
thank you
You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.
wizardwiz said:
You can get the 019 OTA (991Mb) file here
https://forum.xda-developers.com/sho...&postcount=282
It is weird that people get 019 OTA update of 991Mb after updating to 017. I do agree on that.
Click to expand...
Click to collapse
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks
I7210I said:
i got 404 page, but i found it and install it now everything is ok.
so about the flash fire which version i need for the security updates full ota image or factory image for that?
and what to sign over the app to save the data and the root and the twrp recovery?
thanks
Click to expand...
Click to collapse
New link
https://forum.xda-developers.com/showpost.php?p=73762462&postcount=282
I used the 019 OTA and flashed it after unrooting, and reverted to factory recovery. Kept ElementalX kernel and it worked like charm.
ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?
I7210I said:
ok and for next updates, what to sign with the flashfire?and what to choose to download full ota image or factory image for that?
Click to expand...
Click to collapse
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.
v12xke said:
I have always avoided OTA's and used the full Google image. They are usually available at the same time. I only select Boot, System & Vendor. It works every time without fail. It's never not worked across multiple Nexus devices. If there is a new bootloader or radio (modem) which is rare, I drop down to fastboot and flash those manually. FF is a Godsend for someone like me who has Nexus devices and updates monthly with security updates. My .02 cents.
Click to expand...
Click to collapse
i assume you don't have TWRP?
I7210I said:
i assume you don't have TWRP?
Click to expand...
Click to collapse
Yes, I use TWRP. It is always preserved using FF.
so you need to preserve the recovery, isn't it?
I7210I said:
so you need to preserve the recovery, isn't it?
Click to expand...
Click to collapse
haha. yes, you use (select) the preserve recovery option. It makes a copy of your recovery partition (TWRP) so you don't lose your custom recovery. There is a FAQ on using FF here. Best of luck to you.
Thank you