Related
In case anyone finds this helpful, I've captured and uploaded the 5.1 OTA for xt1032 on Bell/Virgin Mobile in Canada: http://d-h.st/gOVo
Thanks man !!!
I wonder if I can install it via my custom recovery or via the bootloader?
And I don't know if your cell is rooted or not, but I have trouble installing via OTA. People told me that I had to unroot my cell and put a STOCK recovery instead of a custom. But I've never been able to update via OTA, I even uninstall Xposed but it's still not working.
CX456 said:
Thanks man !!!
I wonder if I can install it via my custom recovery or via the bootloader?
And I don't know if your cell is rooted or not, but I have trouble installing via OTA. People told me that I had to unroot my cell and put a STOCK recovery instead of a custom. But I've never been able to update via OTA, I even uninstall Xposed but it's still not working.
Click to expand...
Click to collapse
Yep, AFAIK you have to have stock everything (system, recovery, etc.) in order to successfully update via OTA. I just grabbed the latest 5.0 firmware from http://forum.xda-developers.com/moto-g/general/official-stock-firmware-t3207116, backup-ed my files, flashed my phone with the above firmware (which erases everything and resets your phone to factory state except for unlocked bootloader), then proceeded to update via OTA.
vincent_c2 said:
Yep, AFAIK you have to have stock everything (system, recovery, etc.) in order to successfully update via OTA. I just grabbed the latest 5.0 firmware from http://forum.xda-developers.com/moto-g/general/official-stock-firmware-t3207116, backup-ed my files, flashed my phone with the above firmware (which erases everything and resets your phone to factory state except for unlocked bootloader), then proceeded to update via OTA.
Click to expand...
Click to collapse
Sorry for the two last weeks late, I was really busy this time.
I just solved my problem, in fact, I install the stock recovery of another country and making so I couldn't update via OTA. I've been in this link below to retrieve the Bell's recovery and I managed to go from 5.0.2 to 5.1 with no problem!
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
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
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
The RS988 finally has a new OS update with Google patch level Dec 1st, and that means that we are finally good against blueborne and krack!
Sent from my RS988 using Tapatalk
I just installed it. It's about time. I was beginning to wonder if they had stopped support on the RS988. I hear the LG G5 is supposed to get Oreo, but I have a feeling that the RS988 will get left out based on how the updates have gone so far.
Hi! Has the modem changed?
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Nispero said:
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Click to expand...
Click to collapse
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
kattolo said:
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
spinoza_web said:
Hi! Has the modem changed?
Click to expand...
Click to collapse
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Nispero said:
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
Click to expand...
Click to collapse
the best source of full stock roms as well as info on the phone I could find so far is https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
kattolo said:
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Click to expand...
Click to collapse
Here's the baseband version with RS98821c: MPSS.TH.2.0.c1.4-00047-M8996FAAAANAZM-1.88674.1.101802.1
The numbers are slightly different at the end compared to RS98821d , but I'm not sure what if anything might have changed.
maybe, for getting OTA should we just get unroot? How to do it properly?
If recovery is not the stock one, it will not be possible to install the OTA.
Alternatively you might need to wait for someone to make a flashable zip you could flash with TWRP, but given the fact development on this phone is not too active you might need to wait for a while before is available
Sent from my RS988 using Tapatalk
Awkydee said:
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
Click to expand...
Click to collapse
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
brewerywagon said:
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
Click to expand...
Click to collapse
First I flashed the magisk uninstaller and rebooted back to recovery. Then I flashed the 21c COMPLETE ZIP and didn't flash magisk so it would replace TWRP with the stock recovery on reboot. Then I rebooted and when I tried to update it went to the stock and threw up an error then rebooted. Upon reboot it displayed a message saying that I couldn't update because my device had been rooted. So I rebooted back in to bootloader and flashed TWRP again. Then I flashed 21a COMPLETE ZIP and no magisk so that the stock recovery would replace TWRP. I rebooted and went through setup and took OTA updates until I was on 21d. Then rebooted back into bootloader and flashed TWRP. Then rooted and we've through setup. I tried every other way but this was the only way that worked for me. I hope it helps!
should be an easier way. Did u see some changes to the radio?
Some of you may remember that last year I had the misfortune of installing the Brightpoint ROM on my Unlocked G5, which completely messed the phone up by not allowing it to connect to AT&T's LTE. It was a process to re-flash the older ROMs/Bootloader and then rebuild it to a stable 21c. I had used it for a while like that, and the only problem I had was that when ending a voice call (HSPA) it would take a while to change back to LTE.
I ended up going with the S8 over the summer (Samsung discount + Note 2 trade in) which got it for $18/month. I've been using it ever since and the LTE to HSPA Voice to LTE change-off on the S8 is done within a second, unlike the G5.
My mom had been using an unlocked Samsung S5 for almost a year now, and it's constantly dropping calls, and this past week it froze on her and required a battery pull, so was thinking of having her try out my (unused) G5 to see if she liked it more. When I turned the G5 on today, I updated all the apps, and then installed the 21d OTA update. The hand-off from voice to LTE still is not as fast as my S8, but seems to be improved from the 21c firmware.
ROM Posted
Just to let you all know, I have posted the latest 21d stock ROM in my thread here: https://forum.xda-developers.com/lg-g5/development/stock-21c-roms-flashable-zips-imgs-t3679907
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
ingressor said:
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
Click to expand...
Click to collapse
I'm not having any reboot issues when playing music.
The October Security Patch for those on OPP28.85-16 has come out.
You can sideload the OTA if you're on untouched OPP28.85-16 or flash the TWRP zip if you've have TWRP.
Edit:
For the TWRP flashable zip, check this thread .
I removed it from this thread after I realized it's not OPPS28.85-16-2 but OPPS28.85-13-2
Notice that if you're on retca or reteu channel, or any other channel where you've got an Oreo version other than OPP28.85-16, then you should either wait for the OTA notification to pop up on your phone or flash the TWRP flashablr zip.
THIS OTA ZIP IS ONLY COMPATIBLE WITH OPP28.85-16. FLASHING IT OVER OPP28.85-13 OR ANY OTHER VERSION WILL HARD BRICK YOUR DEVICE
That is because this OTA patches the device's gpt table. So if you're not on OPP28.85-16 and sideload this= :crying::crying: goodbye Cedric
Downloads:
OTA : https://drive.google.com/file/d/1PHJqkdFgS-erSJ0jc54cTWvUrNRQWfZJ/view?usp=drivesdk
PS I removed the TWRP link, it's actually for OPPS28.85-13-2
Sorry for the bad edition, I'm sleepy and don't have a computer around.
Flashed the twrp ota by Nzedpred yesterday and it's working like a charm. Previously I was on OPP28.85-16
Hi, i'm having some troubles to make my moto g5 identified when i'm gonna sideload the ota. how can I solve it?
merlinolillo said:
Flashed the twrp ota by Nzedpred yesterday and it's working like a charm. Previously I was on OPP28.85-16
Click to expand...
Click to collapse
Twrp Dirty flash works or i should do clean install?
the TWRP-Link shows a ...13-2, not a ...16-2, is this correct?
can not update from ota package.
every time I check for updates, Moto Update doesn't recognize local packages. Had to apply patch via Recovery
iKnocks said:
Hi, i'm having some troubles to make my moto g5 identified when i'm gonna sideload the ota. how can I solve it?
Click to expand...
Click to collapse
Have you installed the usb drivers from Motorola's website?
If you didnt, then do it, but if you've already done so and still the phone is not detected, type %tmp% on your file explorers address bar (assuming you're on windows) and and then search for .msi fules. Find the .msi correspondent to your Motorola drivers and install it mannualy.
ahmedAZ said:
Twrp Dirty flash works or i should do clean install?
Click to expand...
Click to collapse
If you were on stock a dirty flash works, if you were on a custom ROM you'll get lots of bugs
kare_meesner said:
the TWRP-Link shows a ...13-2, not a ...16-2, is this correct?
Click to expand...
Click to collapse
Yeah it's indeed OPPS28.85-13-2, Ill make a separate thread for it
PsyClip-R said:
can not update from ota package.
every time I check for updates, Moto Update doesn't recognize local packages. Had to apply patch via Recovery
Click to expand...
Click to collapse
No, that's not the way you do it. You have to install Motorola usb drivers, then install ADB/platform-tools, then enable usb debugging and connect the to the pc using the usb cable.
After you've done that you'll type adb devices and you should see your phone's serial number. If that shows up, type adb sideload ota-filename.zip
ahmedAZ said:
Twrp Dirty flash works or i should do clean install?
Click to expand...
Click to collapse
Yes, I made a dirty flash and it works perfectly
merlinolillo said:
Yes, I made a dirty flash and it works perfectly
Click to expand...
Click to collapse
you dont have any problems with gmail sync?
OTA Side load not working for me. Get Error 7.
Downloaded earlier that day the twrp File and installed, but then I saw that this was -13-2. Completely delete my G5 again and installed 85-16 again.
Now downloaded the OTA File, in TWRP used ADB Sideload (adb devices showed my G5) but ended with Error 7.
freeZbies said:
Have you installed the usb drivers from Motorola's website?
If you didnt, then do it, but if you've already done so and still the phone is not detected, type %tmp% on your file explorers address bar (assuming you're on windows) and and then search for .msi fules. Find the .msi correspondent to your Motorola drivers and install it mannualy.
Now it worked, thank you btw
Click to expand...
Click to collapse
woozie.2007 said:
you dont have any problems with gmail sync?
Click to expand...
Click to collapse
Not at all. Gmail sync is working fine at me
merlinolillo said:
Not at all. Gmail sync is working fine at me
Click to expand...
Click to collapse
for me doesnt, is syncing after half an hour or even one hour, but if i unlock the screen is syncing in few seconds
can you upload full oreo stock rom after october patch?
I need it to relock bootloader , other roms not working
Street_Fighter said:
can you upload full oreo stock rom after october patch?
I need it to relock bootloader , other roms not working
Click to expand...
Click to collapse
I haven't heard of that being available out there, but u can relock using the firmware provided in this thread and apply this OTA afterwards, that way you'll have a relocked bootloader and will be in the latest security patch, although if you're not on retus/retbr/retin I recommend you to find a firmware specific to your channel (even if it's an old one) and relock your bootloader using it, and then apply the OTA's that pop up on your notifications, so as not to relock the bootloader with a firmware from another channel, which will prevent you from receiving future otas.
But if you're on one of the three quoted channels you should be fine when fastbooting this firmware.
this update fix the wifi tethering of third-party applications?