Develop Bugs

OTA After I Root?

Will i be able to apply the ota after i root my device i dont want to brick it or loose root?
Thankyou in advance

garner said:
Will i be able to apply the ota after i root my device i donty want to brick it or loose root?
Thankyou in advance
Click to expand...
Click to collapse
Yes but you'll need too root again after I believe.

recklesslife85 said:
Yes but you'll need too root again after I believe.
Click to expand...
Click to collapse
thanks for your reply hope it wont brick the device!

garner said:
thanks for your reply hope it wont brick the device!
Click to expand...
Click to collapse
It won't.
The OTA's come in one of two ways. An incremental package (where it updates from Revision X to revision Y and a full package).
The full package is a full ROM - it wipes /system and pushes everything.
The incremental update is much smaller and patches existing files. This is what you'll be getting. In order to do this the OTA does an assert on every file it wants to patch and makes sure that it hashes out to its expected value. If the hashed value does not match the expected value the update WILL NOT APPLY. You'll get error(7) and it will tell you which assert failed.
So, if you root and don't change anything in /system, flash a new kernel, use an insecure boot image then you'll be able to apply the OTA fine. You will need to fix the permissions on the su binary though as it will recursively chmod /system (su will still be there but with the wrong permissions). Flash the su update package again though and you'll be fine.

krohnjw said:
It won't.
The OTA's come in one of two ways. An incremental package (where it updates from Revision X to revision Y and a full package).
The full package is a full ROM - it wipes /system and pushes everything.
The incremental update is much smaller and patches existing files. This is what you'll be getting. In order to do this the OTA does an assert on every file it wants to patch and makes sure that it hashes out to its expected value. If the hashed value does not match the expected value the update WILL NOT APPLY. You'll get error(7) and it will tell you which assert failed.
So, if you root and don't change anything in /system, flash a new kernel, use an insecure boot image then you'll be able to apply the OTA fine. You will need to fix the permissions on the su binary though as it will recursively chmod /system (su will still be there but with the wrong permissions). Flash the su update package again though and you'll be fine.
Click to expand...
Click to collapse
Thankyou for clearing that up with me, i might just wait till after the ota release then do it

krohnjw said:
It won't.
The OTA's come in one of two ways. An incremental package (where it updates from Revision X to revision Y and a full package).
The full package is a full ROM - it wipes /system and pushes everything.
The incremental update is much smaller and patches existing files. This is what you'll be getting. In order to do this the OTA does an assert on every file it wants to patch and makes sure that it hashes out to its expected value. If the hashed value does not match the expected value the update WILL NOT APPLY. You'll get error(7) and it will tell you which assert failed.
So, if you root and don't change anything in /system, flash a new kernel, use an insecure boot image then you'll be able to apply the OTA fine. You will need to fix the permissions on the su binary though as it will recursively chmod /system (su will still be there but with the wrong permissions). Flash the su update package again though and you'll be fine.
Click to expand...
Click to collapse
what if I just unlock the bootloader and leave everything else the way it is?

rock7632 said:
what if I just unlock the bootloader and leave everything else the way it is?
Click to expand...
Click to collapse
You'll have no problems.

krohnjw said:
You'll have no problems.
Click to expand...
Click to collapse
cool, thanks. I plan on unlocking the bootloader as soon as I get the phone

I followed the directions to unlock the bootloader and root that are posted in the development forum.
Today I decided to try the OTA update.
It reboots to install it, tries to for a very short time and then goes to the picture of an android with an exclamation point. No Idea why, so I'll probably just go a different route.

I don't think mine did that. I was unlocked + rooted (but no CWM flashed or anything) - it rebooted to apply the update, I got a little progress bar for a minute and then it was done.

Restore Root after OTA
Hi,
Can anyone please help with guidance on how to restore root after an OTA update? Running stock ICS ROM (unlocked bootloader) and rooted using Superboot R3.
Can I just simly run the superboot again to root the device?
Thanks,
SAM

jasbur17 said:
I followed the directions to unlock the bootloader and root that are posted in the development forum.
Today I decided to try the OTA update.
It reboots to install it, tries to for a very short time and then goes to the picture of an android with an exclamation point. No Idea why, so I'll probably just go a different route.
Click to expand...
Click to collapse
This is exactly what mine did last night, (found the update from O2) now it wont see the update again ?
What do i need to do to get the update again ? and why didnt it work the 1st time ?

sidhaarthm said:
Hi,
Can anyone please help with guidance on how to restore root after an OTA update? Running stock ICS ROM (unlocked bootloader) and rooted using Superboot R3.
Can I just simly run the superboot again to root the device?
Thanks,
SAM
Click to expand...
Click to collapse
A little bump as I'm looking for the same answer, could anyone help me on this one please
Sorry, ignore my question, found out the answer in the superboot guide. Thanks!

Yes, just run the root batch file again.

r3k0 said:
This is exactly what mine did last night, (found the update from O2) now it wont see the update again ?
What do i need to do to get the update again ? and why didnt it work the 1st time ?
Click to expand...
Click to collapse
Do you have clockwork recovery installed?
I think that OTA fails if you have an alternative recovery.
I have root and unlocked bootloader, i flashed the original recovery over clockwork one...let's wait and see if OTA apply succesfully.

lesilent said:
Do you have clockwork recovery installed?
I think that OTA fails if you have an alternative recovery.
I have root and unlocked bootloader, i flashed the original recovery over clockwork one...let's wait and see if OTA apply succesfully.
Click to expand...
Click to collapse
The OTA update zip should get downloaded to /cache. You can then use CWM recovery to flash that if you don't want to revert to stock recovery.

New OTA update 11/24

Hi,
I got a new update today.
No, it is not android L
It said VoLTE improvement and updated stability.
Full firmware is available in sammobile: http://www.sammobile.com/firmwares/confirm/39231/N900TUVUENK3_N900TTMBENK3_TMB.zip/
If you already updated over OTA to NK3 and want to root without tripping Knox - Use Odin desktop to flash the kernels. It goes in the bootloader section in Odin.
1) Flash the NE6 kernel from here (http://www.mediafire.com/download/q7ri06fz1762zy3/N900TUVUDNE6_KERNEL.tar.md5)
2) Use Towelroot - get it from www.towelroot.com
3) Flash the NK3 kernel back (http://www.mediafire.com/download/t52121ld63gen6r/nk3_kernel.tar.md5)
This is what I did to get root with knox 0x0.

For some reason, I am unable to open the file. is it always like that? Or did it not download properly?
UPDATE: It flashes correctly - it is just a CSC update.
But: flash at your own risk. I am neither responsible nor probably knowledgeable enough to help you if you brick your phone.
I'll do my best though

I wouldn't be surprised if T-Mobile didn't document a newly locked bootoader and the ability to block rooting while disguising this as just a VoLTE update.
Edit: The download is corrupt on my end too.

Anonymously_Unknown said:
I wouldn't be surprised if T-Mobile didn't document a newly locked bootoader and the ability to block rooting while disguising this as just a VoLTE update.
Edit: The download is corrupt on my end too.
Click to expand...
Click to collapse
Took the plunge. Copied it to the cache folder, selected survival mode in SuperSU and updated.
It is just a CSC and Multi-CSC update. Updated successfully, root intact, Knox still 0x0.
It says cant open from PC and phone file explorers. But while updating, it says footer failed (or something like that) for system, kernel etc.
But for CSC and MULTI-CSC, it says successfully updated.
Steps to update: (I am not responsible for anything that happens)
1) SuperSU -> Settings -> Survival Mode (Not sure if necessary, since it only updates the CSC. I did it for safety)
2) Copy file to device (I copied in original cache/FOTA location)
3) Reboot to recovery (stock)
4) Apply OTA update from cache
5) Select the correct file in the cache/FOTA (or wherever you copied) folder
6) After it completes update, press any key to go back to recovery menu -> restart
7) Verify and enjoy.

CravingMender9 said:
Took the plunge. Copied it to the cache folder, selected survival mode in SuperSU and updated.
It is just a CSC and Multi-CSC update. Updated successfully, root intact, Knox still 0x0.
It says cant open from PC and phone file explorers. But while updating, it says footer failed (or something like that) for system, kernel etc.
But for CSC and MULTI-CSC, it says successfully updated.
Steps to update: (I am not responsible for anything that happens)
1) SuperSU -> Settings -> Survival Mode (Not sure if necessary, since it only updates the CSC. I did it for safety)
2) Copy file to device (I copied in original cache/FOTA location)
3) Reboot to recovery (stock)
4) Apply OTA update from cache
5) Select the correct file in the cache/FOTA (or wherever you copied) folder
6) After it completes update, press any key to go back to recovery menu -> restart
7) Verify and enjoy.
Click to expand...
Click to collapse
Interesting - any difference in About Device screen in Settings? Perhaps share a screenshot? Just curious

dwitherell said:
Interesting - any difference in About Device screen in Settings? Perhaps share a screenshot? Just curious
Click to expand...
Click to collapse
Don't see any difference. VoLTE was working fine anyways.

new update
I just updated too and mine shows the last numbers now of my version as NK3? I have looked to find anything about this update but havent had any success. The latest update i can find any information on is NF9. I do not really see any significant changes to anything UI wise at least but i did just finish the update bout 15 mins ago.

stlstyles said:
I just updated too and mine shows the last numbers now of my version as NK3? I have looked to find anything about this update but havent had any success. The latest update i can find any information on is NF9. I do not really see any significant changes to anything UI wise at least but i did just finish the update bout 15 mins ago.
Click to expand...
Click to collapse
Yep, that sounds right then.
Not much info, but a little is found here anyway.

Update
dwitherell said:
Yep, that sounds right then.
Not much info, but a little is found here anyway.
Thanks bud, i was looking for confirmation that this was a legit build version or if i messed some stuff up. This was the first time i have done an update. I rooted it first hour i had it and havent done any updates because i didnt want to mess with it. I went from NB4 to this NK3. I was expecting to end up on NF9 and was pretty surprised seeing NK3 after it was finished. lol Then googled it and found nothing out there referring to this version, so i was a bit confused.
Click to expand...
Click to collapse

dwitherell said:
Yep, that sounds right then.
Not much info, but a little is found here anyway.
Click to expand...
Click to collapse
This is weird. I did the update and it is still NF9.
The funny thing is, the update page on TMobile says that T-Mobile Free Inflight Texting has been added as a new feature. I already had that. I have used it multiple times in flight.

Sammobile has it now. Looks more than just a csc.
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T

toastido said:
Sammobile has it now. Looks more than just a csc.
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T
Click to expand...
Click to collapse
correct.
Full firmware is available in sammobile: http://www.sammobile.com/firmwares/confirm/39231/N900TUVUENK3_N900TTMBENK3_TMB.zip/
I think I got a corrupt OTA. I had to recover using KIES, lost root.
Re-rooted again:
1) Flashed the NE6 kernel from here (http://www.mediafire.com/download/q7ri06fz1762zy3/N900TUVUDNE6_KERNEL.tar.md5)
2) Used Towelroot from www.towelroot.com
3) Flashed the NK3 kernel back (http://www.mediafire.com/download/t52121ld63gen6r/nk3_kernel.tar.md5)
This is what I did to get root with knox 0x0. Also updated OP. I only created the kernel for this, since that is all I needed and was in a hurry.
Can you do the remaining files for anyone else who wants it? As you always do an excellent job on that

CravingMender9 said:
correct.
Full firmware is available in sammobile: http://www.sammobile.com/firmwares/confirm/39231/N900TUVUENK3_N900TTMBENK3_TMB.zip/
I think I got a corrupt OTA. I had to recover using KIES, lost root.
Re-rooted again:
1) Flashed the NE6 kernel from here (http://www.mediafire.com/download/q7ri06fz1762zy3/N900TUVUDNE6_KERNEL.tar.md5)
2) Used Towelroot from www.towelroot.com
3) Flashed the NK3 kernel back (http://www.mediafire.com/download/t52121ld63gen6r/nk3_kernel.tar.md5)
This is what I did to get root with knox 0x0. Also updated OP. I only created the kernel for this, since that is all I needed and was in a hurry.
Can you do the remaining files for anyone else who wants it? As you always do an excellent job on that
Click to expand...
Click to collapse
Yeah it's downloading. I'll have the parts up either later tonight or tomorrow. [emoji6]
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T

New baseband available?

davwman said:
New baseband available?
Click to expand...
Click to collapse
Here:
http://www.mediafire.com/download/qqng1iw2pzfijhu/modem.bin

can someone provide new OTA File only ?

CravingMender9 said:
Here:
http://www.mediafire.com/download/qqng1iw2pzfijhu/modem.bin
Click to expand...
Click to collapse
Did it have a new NON-HLOS.BIN too? Was getting ready to make a new odin file and saw that file in there from previous update.

NMonster69 said:
Did it have a new NON-HLOS.BIN too? Was getting ready to make a new odin file and saw that file in there from previous update.
Click to expand...
Click to collapse
Here: http://www.mediafire.com/download/7e8elhtsyakbvtz/NON-HLOS.bin

CravingMender9 said:
Here: http://www.mediafire.com/download/7e8elhtsyakbvtz/NON-HLOS.bin
Click to expand...
Click to collapse
Can non-hlos.bin be flashed in mobile Odin?

CravingMender9 said:
Here: http://www.mediafire.com/download/7e8elhtsyakbvtz/NON-HLOS.bin
Click to expand...
Click to collapse
I made an odin file using your two files. If anyone wants it let me know.

Unable to update to Android 5.0.2

Dear all,
I hope anyone can help me. I am trying to update to the latest Android version which I got OTA today. I have rooted my device and I am running TWRP (version 2.8.5.0) since some time. (Rooted it to restore some apps using Titanium backup). When I try to update using the OTA my device boots into recovery. When I choose install and select the downloaded zip file my device gives me the following error:
E: Zip signature verification dailed: 1
Disabling the ZIP verification doesn't work as I will just get another error message.
I have tried sideloading the ROM using adb commands but so far this hasn't worked either.
Anyone can give me some directions as how to continue from here? I would really like to update my device to Android 5!
Update with solution (for me):
What worked for me was downloading the OTA update like I would normally do. Then connect the phone to the computer and copy the downloaded update file to the computer (should be located on internal memory/download/). Once you have the file on your computer extract it, and then extract the file 'firmware'. Inside this second file should be a recovery.img. If you flash this recovery to your phone (no need to unroot or relock your bootloader) you will then be able to install the update.

That's because you need stock recovery to flash OTA. It won't work with TWRP because the OTA ZIP works different than a custom ROM.
Go back to stock everything and it'll work.
Or wait a couple of days till the boys here come up with a lollipop rom.

Ok thanks a lot, that'll help me I'll let you guy know if I run into any more problems.

how revert back to stock rom
JuanArg said:
That's because you need stock recovery to flash OTA. It won't work with TWRP because the OTA ZIP works different than a custom ROM.
Go back to stock everything and it'll work.
Or wait a couple of days till the boys here come up with a lollipop rom.
Click to expand...
Click to collapse
sir give step by step guide for reverting back to stock rom so as to install ota lollipop

there's have another way?
i had update from my HTC Disre EYE to 5.0 LLP [file name: OTA_EYE_TUHL_L50_SENSE60_MR_hTC_Asia_WWE_2.19.707.1-1.17.707.9_release_426512hhqv3ttmt8g0i6n3.zip(823MB)](if you want this file just tell me)
bootloader unlocked, S-ON, Rooted(SuperSU). at first began update install there's tried to go to Recovery Mode, right?, but mine is TWRP 2.8.5.0, that's doesn't work right, and i found this http://forum.xda-developers.com/desire-eye/general/update-to-android-5-0-2-t3081580 and i swear to god i'm not sure how can i do it right, i'm rookie for HTC. and then i just use fastboot flash recovery.img from this http://forum.xda-developers.com/des...1-15-502-7-t2966590/post57350873#post57350873, then seem like it work but it failed anyway. if i have to rollback to same old state of original ROM, i have to use HTC RUU right?, but all i can find is rom from USA, i'm not sure it will works in ASIA. i want to update to LLP so bad 'cause i still have problem with HTC write protection.
any solution for this, please help:silly:

sir my phone also on same condition and on 1.17.707.9
please send above file link for me I have no update notification
now we want ruu

sir please send file link

Use these two files. First restore the stock nandroid using twrp (remember to choose NO when twrp prompts you to install supersu and root rom).
After you successfully restore the backup, flash stock recovery.
That should take care of it.
https://docs.google.com/file/d/0B21aRK6c7mFWM19zTU9kYzc4YVU/edit?usp=docslist_api
https://docs.google.com/file/d/0B21aRK6c7mFWSmRpU2RLcTNtQkk/edit?usp=docslist_api
Sent from my HTC Desire EYE using XDA Free mobile app

It works!!!!
JuanArg said:
Use these two files. First restore the stock nandroid using twrp (remember to choose NO when twrp prompts you to install supersu and root rom).
After you successfully restore the backup, flash stock recovery.
That should take care of it.
Sent from my HTC Desire EYE using XDA Free mobile app
Click to expand...
Click to collapse
Your post save my life, sir. Now I can back to 4.4.4 with 1.17.707.9 software number!!! THANKS.

sorry for lately
hbrajhbh1 said:
sir please send file link
Click to expand...
Click to collapse
just got out few days, "drive.google.com/file/d/0Bz42d4oUm2q_SWNaTV9zbTBHSkU/view?usp=sharing" is the zip file update from HTC Asia_WWE_2.19.707.1-1.17.707.9, i hope it will help:cyclops:

sir sorry to say this link is not working? Please review

pkzr said:
i had update from my HTC Disre EYE to 5.0 LLP [file name: OTA_EYE_TUHL_L50_SENSE60_MR_hTC_Asia_WWE_2.19.707.1-1.17.707.9_release_426512hhqv3ttmt8g0i6n3.zip(823MB)](if you want this file just tell me)
bootloader unlocked, S-ON, Rooted(SuperSU). at first began update install there's tried to go to Recovery Mode, right?, but mine is TWRP 2.8.5.0, that's doesn't work right, and i found this http://forum.xda-developers.com/desire-eye/general/update-to-android-5-0-2-t3081580 and i swear to god i'm not sure how can i do it right, i'm rookie for HTC. and then i just use fastboot flash recovery.img from this http://forum.xda-developers.com/des...1-15-502-7-t2966590/post57350873#post57350873, then seem like it work but it failed anyway. if i have to rollback to same old state of original ROM, i have to use HTC RUU right?, but all i can find is rom from USA, i'm not sure it will works in ASIA. i want to update to LLP so bad 'cause i still have problem with HTC write protection.
any solution for this, please help:silly:
Click to expand...
Click to collapse
Are you able to install this OTA after you returned to stock .17.707.9 ?
You were on 1.17.707.9 and you received the above mentioned file as OTA ?
Can it be installed by stock recovery (un-rooted phone) or do i have to root and install twrp to install this OTA ?
thanks

after I reverted to stock version I get ota notification.
i flashed stock recovery and unrooted and then only able to install lollipop update succeefully

hbrajhbh1 said:
after I reverted to stock version I get ota notification.
i flashed stock recovery and unrooted and then only able to install lollipop update succeefully
Click to expand...
Click to collapse
I brought my phone 4 days ago ... It is on stock kit Kat 1.17.707.9 (unrooted) . Now how can I install the above shared OTA? Can you give steps plz.

prmah said:
Are you able to install this OTA after you returned to stock .17.707.9 ?
You were on 1.17.707.9 and you received the above mentioned file as OTA ?
Can it be installed by stock recovery (un-rooted phone) or do i have to root and install twrp to install this OTA ?
thanks
Click to expand...
Click to collapse
1. i unable to install that OTA and i can not return to original ROM of 1.17.707.9, i still don't know HOW.
2. Yes, go to Setting > About > Software Update
3. Yes, it's can install with Original Recovery and it's not work with TWRP.
hbrajhbh1 said:
after I reverted to stock version I get ota notification.
i flashed stock recovery and unrooted and then only able to install lollipop update succeefully
Click to expand...
Click to collapse
How to Revert to Stock Version?, Just uninstall SuperSU?, and how to unroot it?
prmah said:
I brought my phone 4 days ago ... It is on stock kit Kat 1.17.707.9 (unrooted) . Now how can I install the above shared OTA? Can you give steps plz.
Click to expand...
Click to collapse
go to Setting > About > Software Update

as ur phone new one and u have not done any root or unlock so update is easy
check for lollipop update in settings/about/software update?it will notify.if update available download and install.

hbrajhbh1 said:
as ur phone new one and u have not done any root or unlock so update is easy
check for lollipop update in settings/about/software update?it will notify.if update available download and install.
Click to expand...
Click to collapse
I think OTA is not available in India right now.
But when I m trying to install the above shared OTA(Google drive link) from stock recovery , a as soon as I select "apply from phone storage " phone reboots on its own .
I wana install lollipop please help.

prmah said:
I think OTA is not available in India right now.
But when I m trying to install the above shared OTA(Google drive link) from stock recovery , a as soon as I select "apply from phone storage " phone reboots on its own .
I wana install lollipop please help.
Click to expand...
Click to collapse
in usual way of that you have to put update file in Download folder in internal memory(after that you may have to restart) and then go to setting > about > software update, checking for update and wait the way that should be.

pkzr said:
in usual way of that you have to put update file in Download folder in internal memory(after that you may have to restart) and then go to setting > about > software update, checking for update and wait the way that should be.
Click to expand...
Click to collapse
I did that but no luck.
placed ota file in download folder then restarted the phone. Then check for update but still the same message "there are no updates available for your phone"

So i just got the ota update today the lollipop for my country (Egypt) i had phone rooted with custom recovery TWRP i tried installing the update and failed.. then i flashed the stock recovery and still fails...gone to supersu and settings and unrooted it and tried again, still fails...
relocked the bootloader and STILL fails this now got me so mad because upon every install failure i had to redownload the update (it takes a long time tho) so if anyone could help me here i will be so thankful.

Guide [Simple]: OTA update with rooted and unlocked

Hi,
This guide is based in my first post about how to do it with the Moto G4: http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
(Read it for full info).
Then, here the updated info for the Moto G5+:
1) If you are in NPN25.137-33 and like to apply the last OTA, but you have rooted and/or flashed a custom recovery (TWRP) + custom kernel, then you can.
2) Requirements: original SYSTEM and BOOT partitions. If you have flashed another version, then restore the originals. You can use any backups from you, or you can download from here: http://drive.google.com/open?id=0B6-Tz_7kDyxsZnVNa0pldnhndG8
(Thank you to GtrCraft: http://forum.xda-developers.com/showpost.php?p=72387571&postcount=15)
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Warning: Don't install this OTA if you don't have the exact version of the required firmware.
4) After install the OTA, reboot and check the new version. At that point the ROM isn't rooted. Then, you need to re-root.
That's all!

Tried flashing and it fails.

You need stock recovery to flash OTA's

GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Click to expand...
Click to collapse

bvsbutthd101 said:
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
Click to expand...
Click to collapse
Well the OTA isn't meant for reteu firmware. So that will bring problems with it

bvsbutthd101 said:
Tried flashing and it fails.
Click to expand...
Click to collapse
Because isn't for your device OR you have modified SYSTEM or BOOT.

GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
FALSE!
GtrCraft said:
Well the OTA isn't meant for reteu firmware. So that will bring problems with it
Click to expand...
Click to collapse
TRUE! :silly:

manos78 said:
Because isn't for your device OR you have modified SYSTEM or BOOT.
Click to expand...
Click to collapse
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)

bvsbutthd101 said:
Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).

manos78 said:
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).
Click to expand...
Click to collapse
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA

bvsbutthd101 said:
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
bvsbutthd101 said:
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
So did you get this OTA normally as a system update, indicating that we should be receiving it now?

Dahenjo said:
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
So did you get this OTA normally as a system update, indicating that we should be receiving it now?
Click to expand...
Click to collapse
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.

bvsbutthd101 said:
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.
Click to expand...
Click to collapse
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.

Dahenjo said:
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.
Click to expand...
Click to collapse
Yeah I got mine the day it came out from amazon, using on Verizon.

Here is a flashable stock zip based on reteu firmware:
https://drive.google.com/open?id=0B6-Tz_7kDyxsU2NlTERsSzZsalk

U have*67 files??

Same Here
US variant XT1687 4/64GB on Sprint but no OTA notification. Maybe I should just wait another week before flashing this. Not sure if there is something in the SIM the server notices and stops updates on some carriers. But maybe the SIM is how they decide, not sure what else they could go by other than IP to detect the carrier.
bvsbutthd101 said:
Yeah I got mine the day it came out from amazon, using on Verizon.
Click to expand...
Click to collapse

I also have XT1687 4/64G US on 25.137-33 + root & TWRP, and no OTA notification.
So, is there a way to go to -67 (flash over TWRP, restore back to -15 stock)?
I could not understand the right answer from all the thread on the subject.

Sorry for this noob question: I have just rooted a brand new phone. After the first login the OTA warning popped out so I downloaded it. When finished I got a loop on the recovery; I fastbooted boot and got my phone working again ... what do I have to do? Thanks.

Hi,
My upgraded guide: http://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175

Official Moto G5 and G5 Plus Android 8.1 Oreo OTA ZIP file [OPSS28.85-17-4]

This is the OTA update I received for the G5 Plus.
The phone was running a North American (retus) build OPSS28.85-17-2 (October 1, 2018 patch level) prior to the update. After the update, the phone is running OPSS28.85-17-4 (December 1, 2018 patch level).
MD5: f840a71b9a1b347b13274c668adf77a0
SHA1: fb53a9a872c8a881f4bde111aaade4f23bb7a9a4
SHA256: d20bcd877222429dfc1620c5265b91cf29b2768d8e51314ef7b8f3ee0d9bba45
File size: 73,434,767 bytes (~70MB)
https://drive.google.com/file/d/1XWbH8emmxduw_yosNJASndgxesbwrp5d/view?usp=sharing
https://www.dropbox.com/s/1tyh80849p1qdsy/potter_US_OPS28.85-17-4_patch.zip?dl=0

reserved for future use

Please help!
Hello, how do I install this update if I have TWRP? I have searched for the stock recovery and I have not had luck.

MasterDoggy said:
Hello, how do I install this update if I have TWRP? I have searched for the stock recovery and I have not had luck.
Click to expand...
Click to collapse
If you have TWRP installed I suspect you have rooted your device or tweaked it in some other way.
In this case OTA updates won't work.
You have to be on unrooted full stock firmware incl. stock recovery (can be found in the related fastboot firmware as "recovery.img").
If you are:
Transfer the file to phone’s internal storage. Go to Settings > apps Provide storage permission to Motorola Update Services app. Check for OTA updates from Settings.
The package will be automatically detected and system upgraded.
(Source: https://forum.xda-developers.com/g5...fficial-moto-g5-g5-plus-t3848246/post77748504 )

Wolfcity said:
If you have TWRP installed I suspect you have rooted your device or tweaked it in some other way.
In this case OTA updates won't work.
You have to be on unrooted full stock firmware incl. stock recovery (can be found in the related fastboot firmware as "recovery.img").
If you are:
Transfer the file to phone’s internal storage. Go to Settings > apps Provide storage permission to Motorola Update Services app. Check for OTA updates from Settings.
The package will be automatically detected and system upgraded.
(Source: https://forum.xda-developers.com/g5...fficial-moto-g5-g5-plus-t3848246/post77748504 )
Click to expand...
Click to collapse
Phone doesn't detect the update package using this method. Please suggest if the file name needs to be changed.

checksamir said:
Phone doesn't detect the update package using this method. Please suggest if the file name needs to be changed.
Click to expand...
Click to collapse
You have to ask the OP, @Amishrabbit for that. But yes, the name the file has now is wrong, it has to be named something like Blur_Version.xx.xx.xx.potter.retail.en.US .

-redacted-

Wolfcity said:
You have to ask the OP, @Amishrabbit for that. But yes, the name the file has now is wrong, it has to be named something like Blur_Version.xx.xx.xx.potter.retail.en.US .
Click to expand...
Click to collapse
Well, my initial reply closed itself without posting, so I'm trying again.
I'm a novice at this stuff. I don't know any instructions about how to install it. I do know that I extracted the URL for the update from the logcat output from the phone on a debugger, and the URL was live for about 10 minutes and now doesn't respond, so presumably it's a time-limited download.
I did rename the file, and I know it's from an official OTA source URL, so I'm pretty sure you can't install it with TWRP. I don't have TWRP installed on this phone and retrieved and installed it using the normal System Update method.
I've attached a screenshot of the phone's version numbers. I can't find a reference to the "Blur" number above on the phone's UI, but the file itself contains the following string, so this appears to be a pairing of (newer version) (older version)
Code:
Blur_Version.28.231.5.potter.retail.en.US )Blur_Version.28.211.2.potter.retail.en.US

The Blur* filenames were only for nougat OTAs, Oreo OTAs are named according to the version you are upgrading *from*.
They can't be installed using TWRP, the stock recovery is required, as is an untouched system, OEM, modem, and other partitions.
If you're rooted, just use the TWRP flashable zips, easier...
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Note that I do have the most recent retus zip there, but haven't yet updated the OP. Link for that is in the last couple of pages.

NZedPred said:
The Blur* filenames were only for nougat OTAs, Oreo OTAs are named according to the version you are upgrading *from*.
They can't be installed using TWRP, the stock recovery is required, as is an untouched system, OEM, modem, and other partitions.
If you're rooted, just use the TWRP flashable zips, easier...
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Note that I do have the most recent retus zip there, but haven't yet updated the OP. Link for that is in the last couple of pages.
Click to expand...
Click to collapse
I guess Blur version works for Oreo as well. I have used the name "Blur_Version.28.21.5.potter.retail.en.US.zip" and system detected the update immediately.
Unable to upload the screenshot due to network issues..

SujataSam said:
I guess Blur version works for Oreo as well. I have used the name "Blur_Version.28.21.5.potter.retail.en.US.zip" and system detected the update immediately.
Unable to upload the screenshot due to network issues..
Click to expand...
Click to collapse
Thanks. It worked like a charm.

february security patch maybe?

any news of February 2019 update?

ashutoshmatari said:
any news of February 2019 update?
Click to expand...
Click to collapse
Seems not. If you see only questions about it but no answers it's unlikely. But feel free to search by yourself in the known sources or use Google and if you find something: Share it.

https://support.motorola.com/in/en/solution/MS137632
here is the maintenance release note of February 2019, but actual release of update is not known.

ashutoshmatari said:
https://support.motorola.com/in/en/solution/MS137632
here is the maintenance release note of February 2019, but actual release of update is not known.
Click to expand...
Click to collapse
Just got it

I have an ota to move from 17-4 to 17-6.
https://www.dropbox.com/s/b8i3l0qgi...8.85-17-6_OTA_Package_OPSS28.85-17-4.zip?dl=0
You'll have to rename it to get it to work automatically. Unfortunately I don't know what the name would need to be. You can however sideload it through ADB. Haven't done that myself so hopefully someone can help with that too.

hopefully they will release it soon for other regions too.

ashutoshmatari said:
hopefully they will release it soon for other regions too.
Click to expand...
Click to collapse
Why shouldn't they?