Develop Bugs

OTA only work with locked nexus ?

I have try restore Samsung ROM 4.0.2 on my galaxy nexus (using cwm restore function), and get OTA update, but can not boot the phone, it stop on cwm, it is because my phone is root, do I need unlock my phone before processes OTA update ?
and I done some modification on my phone e.g. dpi = 240, it will cause problem on OTA update ?
every Google OTA it is working on same way ?

All the images need to be stock...
Including your recovery/bootloader/radios for sure.

Jubakuba said:
All the images need to be stock...
Including your recovery/bootloader/radios for sure.
Click to expand...
Click to collapse
This. You'll need to flash the correct (stock) bootloader, recovery, and radio images before you can install any OTA updates. You can get them as a part of the Factory Image here.

hki_peter said:
I have try restore Samsung ROM 4.0.2 on my galaxy nexus (using cwm restore function), and get OTA update, but can not boot the phone, it stop on cwm, it is because my phone is root, do I need unlock my phone before processes OTA update ?
and I done some modification on my phone e.g. dpi = 240, it will cause problem on OTA update ?
every Google OTA it is working on same way ?
Click to expand...
Click to collapse
Changing any file on /system will cause the update to fail. To change your dpi, you needed to modify your build.prop file, so that will cause the OTA to fail. You need to replace your build.prop file (and any other files you changed) with a stock one.
Locked or unlocked makes no difference for OTAs.
Root or no root makes no difference for OTAs.
As for the radio and the kernel, it depends on the update: if the update patches either, then it will fail if you don't have the right kernel or radio. As Jubakuba and codesplice said, you will be safe for all OTAs if they are stock.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
codesplice said:
[snip]
You can get them as a part of the Factory Image here.
Click to expand...
Click to collapse
Unfortunately, older factory images are no longer available there, so he will not be able to get them from that source.

efrant said:
Unfortunately, older factory images are no longer available there, so he will not be able to get them from that source.
Click to expand...
Click to collapse
It sounded (to me) like the OP was only flashing 4.0.2 as a means of receiving an OTA update to a more recent release. If he were to simply install a 4.0.4 factory image, he would be good to go - and capable of receiving the next OTA.

codesplice said:
It sounded (to me) like the OP was only flashing 4.0.2 as a means of receiving an OTA update to a more recent release. If he were to simply install a 4.0.4 factory image, he would be good to go - and capable of receiving the next OTA.
Click to expand...
Click to collapse
Sorry, I guess I misunderstood your post. I thought you were saying to get the stock images from that page so that he could complete his OTA update.

[Q] OTA JSS15R While Rooted

Currently trying to update my Nexus 7 to JSS15R (8MB OTA that may have helped multitouch issue?)
I am running rooted stock ROM, unlocked bootloader etc. Current build number is JSS15Q.
I've heard the newer versions of SuperSU have the OTA fix built in. I haven't been able to update though. I noticed there was an update and I went to update my Nexus 7. It went to update like it should, but I got an error and it never changed.
Flashed the OTA fix thinking it would help. No.
Forced OTA update by stopping Google Framework. No.
Flashed SuperSU 1.65 and tried to update again. No.
Any suggestions on what I should do? Manually flash the update without loosing root or an data?

Did you reflash the ota after you flashed supersu?
What was the error message?

sfhub said:
Did you reflash the ota after you flashed supersu?
What was the error message?
Click to expand...
Click to collapse
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.

When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.

church said:
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
Click to expand...
Click to collapse
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.

datallboy said:
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
Click to expand...
Click to collapse
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.

church said:
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
Click to expand...
Click to collapse
I found a zip for the ota update, don't remember where, but should I be able just to flash it with TWRP without loosing anything?

It will lose the option to blend milkshakes

church said:
It will lose the option to blend milkshakes
Click to expand...
Click to collapse
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.

Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.

church said:
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
Click to expand...
Click to collapse
Stock recovery is on my device. I'm temporarily booting TWRP with the Nexus Toolkit so I can flash things.

datallboy said:
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
Click to expand...
Click to collapse
Next time you have an error with stock recovery (android fallen down) press/hold power, then press/release VolUp, then release Power.
This will show you the error log.
As to your current problem, if your unit won't download and notify you about JSS15R download it by hand and place in your virtual sdcard, then temporary boot into tarp and choose install, selecting the ota zip.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
datallboy said:
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Click to expand...
Click to collapse
Install the ota update.zip, then before reboot, immediately install supersu.
Do it that way and you won't lose root.

Forced OTA and it failed. I had already flashed the superSU.zip before
If you can't read this is the log...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop" [numbers and letters]
E: Error in /cache/(update file.zip)
(Status 7)
Installation aborted.
Any way to manually flash the update? Because SuperSU OTA isn't working.

So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.

Guhrasoh said:
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Click to expand...
Click to collapse
Now that you mention it I tweaked it with PimpMyRom. I'll take that off and try to update.

I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.

datallboy said:
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
Click to expand...
Click to collapse
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.

sfhub said:
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
Click to expand...
Click to collapse
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.

datallboy said:
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
Click to expand...
Click to collapse
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.

sfhub said:
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
Click to expand...
Click to collapse
I'll probably just backup apps + data and use JSS15R factory image. Made the mistake of not making a backup of my build.prop.
Good thing it's a Nexus Device!

How to update rooted device?

Hi,
I thought that after rooting OTA won't be available but I just got a notification about an update.
Is it safe to click "restart and install"? will it keep the device rooted?
if not, what's the easiest way to update?

nirfun said:
Hi,
I thought that after rooting OTA won't be available but I just got a notification about an update.
Is it safe to click "restart and install"? will it keep the device rooted?
if not, what's the easiest way to update?
Click to expand...
Click to collapse
Last time I updated, I noticed that TWRP took over the updating process if you have it flashed.
While updating, TWRP wont let the updating script to replace the recovery partition, so TWRP remains after the update, after that you have the option to flash more zips if you wish to.
I'd recommend you reflash SuperSU after the update.

nirfun said:
Hi,
I thought that after rooting OTA won't be available but I just got a notification about an update.
Is it safe to click "restart and install"? will it keep the device rooted?
if not, what's the easiest way to update?
Click to expand...
Click to collapse
TWRP wont flash the update... You can use Flashfire, get the latest firmware from here https://developers.google.com/android/images and flash using flashfire....

mcerk02 said:
TWRP wont flash the update... You can use Flashfire, get the latest firmware from here https://developers.google.com/android/images and flash using flashfire....
Click to expand...
Click to collapse
Should I download the OTA or full firmware?
Does it make sense the OTA is 1.1 GB?

nirfun said:
Should I download the OTA or full firmware?
Does it make sense the OTA is 1.1 GB?
Click to expand...
Click to collapse
I dont know what makes the OTA so large... I could be wrong but it is probably an OTA you would get if you were to be updating from M-N or something.... I just went right for the full firmware package, if you never used flashfire here is all the instructions https://flashfire.chainfire.eu/ but its pretty simple, click the + button at bottom right, click flash firmware package, select the files to flash and it will start doing its thing, I chose not to flash recovery when you get to that point, I was concerned it was gonna flash the stock recovery so didnt want to do that....

I flashed the OTA but now my root is gone

mcerk02 said:
TWRP wont flash the update... You can use Flashfire, get the latest firmware from here https://developers.google.com/android/images and flash using flashfire....
Click to expand...
Click to collapse
Last time I ran the update OTA, TWRP ran the update script just fine...

Hey guys! I have enrolled to beta program to get 7.1.1 so now I am on 7.1.1 October 5 patch. But I got a security update patch and I thought that I've done nothing with my root to the /system so I tried to update my phone using restart & update function in "System Update" . It brought up TWRP with some failed script. Now I'm on October 5 patch and I don't have any notification about system update and it shows that my system is up to date. How can I get and flash the November 5 security update? Please help

tauio111 said:
Last time I ran the update OTA, TWRP ran the update script just fine...
Click to expand...
Click to collapse
I heard others say this as well, I have NEVER had TWRP flash an OTA for me....
---------- Post added at 10:01 PM ---------- Previous post was at 09:55 PM ----------
Suren Manukyan said:
Hey guys! I have enrolled to beta program to get 7.1.1 so now I am on 7.1.1 October 5 patch. But I got a security update patch and I thought that I've done nothing with my root to the /system so I tried to update my phone using restart & update function in "System Update" . It brought up TWRP with some failed script. Now I'm on October 5 patch and I don't have any notification about system update and it shows that my system is up to date. How can I get and flash the November 5 security update? Please help
Click to expand...
Click to collapse
Here s the page for the 7.1.1 download, I would imagine it has the latest security update.... https://developer.android.com/preview/download.html

mcerk02 said:
I heard others say this as well, I have NEVER had TWRP flash an OTA for me....
---------- Post added at 10:01 PM ---------- Previous post was at 09:55 PM ----------
Here s the page for the 7.1.1 download, I would imagine it has the latest security update.... https://developer.android.com/preview/download.html
Click to expand...
Click to collapse
It says that flashing factory image will prevent getting future OTAs. So should I check that webpage every month to get the security updates? Os there a way to get OTAs back?

http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/

Suren Manukyan said:
It says that flashing factory image will prevent getting future OTAs. So should I check that webpage every month to get the security updates? Os there a way to get OTAs back?
Click to expand...
Click to collapse
Not getting OTA's while rooted is nothing new.... You can check that page every now and then if you wanted to....

mcerk02 said:
Not getting OTA's while rooted is nothing new.... You can check that page every now and then if you wanted to....
Click to expand...
Click to collapse
Well actually now I got the OTA. The problem is I don't know how to flash it. Because FlashFire is not working anymore.

If you can figure out where is downloaded to I am sure flashfire will flash it, When mine was downloaded I couldn't find the file in system/cache or anywhere else so I gave up and just flashed the whole firmware package.... If you find it, let me know how it goes...

nirfun said:
Should I download the OTA or full firmware?
Does it make sense the OTA is 1.1 GB?
Click to expand...
Click to collapse
Yes it makes sense. These are not incremental OTA zips that you may be used to from previous Nexus devices.
mcerk02 said:
I dont know what makes the OTA so large... I could be wrong but it is probably an OTA you would get if you were to be updating from M-N or something....
Click to expand...
Click to collapse
This is a full OTA patch. The quick explanation is that these OTA zips will update over whatever you have installed (custom rom, stock, rooted, etc) and will patch every partition to the zips OTA level. You could be on OTA #1, 2, 6, 11 or whatever, the zip will update over each previous update.
Sent from my Nexus 5X using Tapatalk

mcerk02 said:
If you can figure out where is downloaded to I am sure flashfire will flash it, When mine was downloaded I couldn't find the file in system/cache or anywhere else so I gave up and just flashed the whole firmware package.... If you find it, let me know how it goes...
Click to expand...
Click to collapse
I think it is in data/ota_package/update.zip. I can see it with root browser but FlashFire doesn't see it.

Guys? No one knows how to update a rooted phone through OTA and without FlashFire?

Suren Manukyan said:
Guys? No one knows how to update a rooted phone through OTA and without FlashFire?
Click to expand...
Click to collapse
adb sideload an OTA image (file does not exist for 7.1.1 developer preview 2, fyi):
https://developers.google.com/android/ota
or
follow section 11 of my guide to update via fastboot:
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
adb sideload an OTA image (file does not exist for 7.1.1 developer preview 2, fyi):
https://developers.google.com/android/ota
or
follow section 11 of my guide to update via fastboot:
http://forum.xda-developers.com/showthread.php?t=3206930
Click to expand...
Click to collapse
As I said I've found a zip called update.zip in data/ota_package. Can it be the OTA , can I try to sideload it?

Suren Manukyan said:
As I said I've found a zip called update.zip in data/ota_package. Can it be the OTA , can I try to sideload it?
Click to expand...
Click to collapse
Supposing you have no other mods installed and no other changes to /system have been made, unroot, reboot, then see if you can adb sideload that update.zip. If it fails, you have two ways on how to do so successfully and without Flashfire like you asked.
Sent from my Nexus 5X using Tapatalk

Anyone received the Oreo ota

Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???

ttocs99 said:
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
Click to expand...
Click to collapse
Not yet. I'm on T-mobile.

mrpink10 said:
Not yet. I'm on T-mobile.
Click to expand...
Click to collapse
Same I spoke to Google support and they claim it's Al read available via ota

Haven't got it yet I bought my phone from Google.
Sent from my Nexus 5X using Tapatalk

Are you rooted? If so just get the ota from google and flash it with flashfire

jd1639 said:
Are you rooted? If so just get the ota from google and flash it with flashfire
Click to expand...
Click to collapse
Flashfire doesn't fully support Oreo yet so that's a no go, same with TWRP. ADB sideload might work.

I just flashed it this morning and had no problems.

I flashed a couple of hours ago official OTA package via ADB. No problems till now.

I took the plunge and flashed the 8.0 stock factory image the done a factory reset after to make sure and it been great ever since turned off animation and it's nippy just wish battery was about better but I'll give it a few days see if that goes

jd1639 said:
I just flashed it this morning and had no problems.
Click to expand...
Click to collapse
Did you use Flashfire?

Does anyone know why the battery drains so fast on Oreo even after fresh clean install

Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.

jd1639 said:
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
Click to expand...
Click to collapse
Well then, I guess it's just when coming from the beta that it doesn't work. Thanks for the heads up.

ttocs99 said:
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Click to expand...
Click to collapse
Enable dev options and disable always keep mobile data on.
I just noticed that for some reason that is checked in oreo and it shouldn't be unless you are never on WIFI.

ttocs99 said:
Same I spoke to Google support and they claim it's Al read available via ota
Click to expand...
Click to collapse
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.

I can confirm that jd1639's method works for people rooted with TWRP.
- download OTA (https://developers.google.com/android/ota)
- run Flashfire 60.0 (free version is OK)
- when asked "A system update has been detected", cancel
- Flash ZIP or OTA
- uncheck "restore boot and recovery images"
- press "EverRoot" and select "Inject SuperSU" and "Preserve recovery"
- Flash
- wait patiently
I tried flashing the modem FW using "Flash firmware package" on the OTA zip file. It rebooted and the screen went black for many minutes. I had to hard reset.
Can anyone confirm the 8.0 baseband? I have M8994F-2.6.39.3.03. I know that's the baseband for the 8.0 developer preview, but I wanted to make sure it was the final.

Billys20 said:
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
Click to expand...
Click to collapse
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?

tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
Nope
Sent from my Nexus 5X using Tapatalk

tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).

Billys20 said:
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Click to expand...
Click to collapse
6p here, downloaded ota (NOT factory), ran Tibu, ran Flashfire 7.0 pro as described and after three reboots and a while of booted finishing, was cleanly updated to 8.0.0. took < 20 min. [emoji2]
Sent from my Nexus 6P using Tapatalk

Locked bootloader - Fresh install Android P

What is the best way to wipe+install the new Android P update on a Verizon Pixel 2 XL(locked bootloader)? I am on the Android P Beta so the Android P full release is showing in system updates but is it better to flash the OTA via USB instead or just update using the OTA system update and then erase all data?

Just update through the system settings and then do a factory reset. Unless you really want to unlock your bootloader.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

paradeedle said:
What is the best way to wipe+install the new Android P update on a Verizon Pixel 2 XL(locked bootloader)? I am on the Android P Beta so the Android P full release is showing in system updates but is it better to flash the OTA via USB instead or just update using the OTA system update and then erase all data?
Click to expand...
Click to collapse
Since you are looking for a fresh start anyway and willing to wipe your data, one way is to just do a factory data reset first, and then flash the OTA via fastboot. Full OTA's are already posted and available. Best of luck. :good:

v12xke said:
Since you are looking for a fresh start anyway and willing to wipe your data, one way is to just do a factory data reset first, and then flash the OTA via fastboot. Full OTA's are already posted and available. Best of luck. :good:
Click to expand...
Click to collapse
Perfect. Flashing the OTA via fastboot still allows OTA monthly updates as well then?

paradeedle said:
Perfect. Flashing the OTA via fastboot still allows OTA monthly updates as well then?
Click to expand...
Click to collapse
Yes, because it is a full OTA image. Many people with locked bootloaders have flashed full OTA's when their unit stopped receiving them manually to force them back on track. The full OTA is almost as big as the complete image > 1GB. Not to be confused with the incremental OTA ~ 50MB. Best of luck.

xringo said:
Just update through the system settings and then do a factory reset. Unless you really want to unlock your bootloader.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
Since when can you unlock the VZ model? I know I haven't spent as much time on the forums since bring relegated back to the land of the rootless, but I haven't noticed any big announcements anywhere. That thread seems to be for the Google version?