Develop Bugs

[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!

RETEU Nougat

Hi there, im on custom rom (RR). My question is how can i update my phone via OTA, after that i will gonna root it again.? Just want to update my phone to latest security patch and after updating i will root it again. Can anyone help me? And sorry for noobish query. Thanks for help

Kap_Tutan said:
Hi there, im on custom rom (RR). My question is how can i update my phone via OTA, after that i will gonna root it again.? Just want to update my phone to latest security patch and after updating i will root it again. Can anyone help me? And sorry for noobish query. Thanks for help
Click to expand...
Click to collapse
You will have to reinstall to complete Stock (see link below). You can not OTA from a customer rom.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/

Jimi Mack said:
You will have to reinstall to complete Stock (see link below). You can not OTA from a customer rom.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Click to expand...
Click to collapse
If you already did update to Nougat via OTA, flashing that Marshmallow stock image can/will brick your device.
There is a generic RETAIL Nougat Stock image for the April Security Updates flying around somewhere. But generally you should install the stock version you originally had on your device, and then update from there.

BtbN said:
If you already did update to Nougat via OTA, flashing that Marshmallow stock image can/will brick your device.
There is a generic RETAIL Nougat Stock image for the April Security Updates flying around somewhere. But generally you should install the stock version you originally had on your device, and then update from there.
Click to expand...
Click to collapse
I downloaded the nougat april security patch of RETAIL. What do you mean by this "But generally you should install the stock version you originally had on your device, and then update from there"!
And is the retail april is working with my reteu dual sim? Do i still able to receive ota uodate when i flash the april patch?

Kap_Tutan said:
I downloaded the nougat april security patch of RETAIL. What do you mean by this "But generally you should install the stock version you originally had on your device, and then update from there"!
And is the retail april is working with my reteu dual sim? Do i still able to receive ota uodate when i flash the april patch?
Click to expand...
Click to collapse
I have no idea in what channel a phone will end up with the generic RETAIL images. I just did a dump of every single partition on my phone before I installed custom stuff, so I can always get back to how it was originally, and OTA from there.

BtbN said:
If you already did update to Nougat via OTA, flashing that Marshmallow stock image can/will brick your device.
There is a generic RETAIL Nougat Stock image for the April Security Updates flying around somewhere. But generally you should install the stock version you originally had on your device, and then update from there.
Click to expand...
Click to collapse
Below is a link on how to properly downgrade and then be able to take OTA.
---------- Post added at 07:22 AM ---------- Previous post was at 06:54 AM ----------
[/COLOR]
Kap_Tutan said:
Hi there, im on custom rom (RR). My question is how can i update my phone via OTA, after that i will gonna root it again.? Just want to update my phone to latest security patch and after updating i will root it again. Can anyone help me? And sorry for noobish query. Thanks for help
Click to expand...
Click to collapse
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118

Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118[/QUOTE]
Actually this is my first non-samsung phone. That's why totally noob in recovering my phone and revert back to stock. Please sorry for such a noob

Kap_Tutan said:
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118
Click to expand...
Click to collapse
Actually this is my first non-samsung phone. That's why totally noob in recovering my phone and revert back to stock. Please sorry for such a noob[/QUOTE]
No problem... any time you change a phone I always suggest to really look at the Guides and Discussion section and get to know the phone well before jumping in and hacking it.. Plus Moto did not make this one as simple to flash and recover as some of their others.
Good Luck.

Jimi Mack said:
Below is a link on how to properly downgrade and then be able to take OTA.
---------- Post added at 07:22 AM ---------- Previous post was at 06:54 AM ----------
[/COLOR]
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118
Click to expand...
Click to collapse
FYI link is broken.

ViperX85 said:
FYI link is broken.
Click to expand...
Click to collapse
Sorry, try this one...
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118

Jimi Mack said:
You will have to reinstall to complete Stock (see link below). You can not OTA from a customer rom.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Click to expand...
Click to collapse
Is this image signed?

Srandista said:
Is this image signed?
Click to expand...
Click to collapse
As far as I Moto has not released any signed firmware for the Addison.

Just flash this with RSD lite and you`ll have 7.1.1 with aug patch )

St.Noigel said:
Just flash this with RSD lite and you`ll have 7.1.1 with aug patch )
Click to expand...
Click to collapse
Flashing that on my reteu device resulted in a bootloop with the phone playing the "Hello Moto" sound over and over again.
I could flash LineageOS over it and it worked fine, but it did not give me a working stock OS.

BtbN said:
Flashing that on my reteu device resulted in a bootloop with the phone playing the "Hello Moto" sound over and over again.
I could flash LineageOS over it and it worked fine, but it did not give me a working stock OS.
Click to expand...
Click to collapse
You can try to do next:
1. Wipe everything (incl internal storage with TWRP)
2. Format (not wipe) data with TWRP
3. Go to fastboot and flash stock ROM with RSD lite
P.S. If you still have bootloop - just flash TWRP and SuperSU with it. But if you`ll do everything, what i wrote - You`ll have fully worked device.
Good luck )

St.Noigel said:
You can try to do next:
1. Wipe everything (incl internal storage with TWRP)
2. Format (not wipe) data with TWRP
3. Go to fastboot and flash stock ROM with RSD lite
P.S. If you still have bootloop - just flash TWRP and SuperSU with it. But if you`ll do everything, what i wrote - You`ll have fully worked device.
Good luck )
Click to expand...
Click to collapse
Step 3 is what I did originally, including erasing userdata. With that exact stock ROM.
I only wanted to update the bootloader and radio firmware, so I don't overly care it does not boot by itself, as I'm using LaOS.
Just as a note for anyone trying to use that image.

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

Cannot update to Oreo

I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.

Comet1966 said:
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Click to expand...
Click to collapse
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk

piscesjoey said:
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It's like the system and recovery don't have access to the storage at all.

Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.

Uzephi said:
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Click to expand...
Click to collapse
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859

Comet1966 said:
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Click to expand...
Click to collapse
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?

Uzephi said:
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Click to expand...
Click to collapse
I did the flashall and that's it. I have no idea what's up with it

Comet1966 said:
I did the flashall and that's it. I have no idea what's up with it
Click to expand...
Click to collapse
What is your current version? -11/November patch?

Uzephi said:
What is your current version? -11/November patch?
Click to expand...
Click to collapse
This

Comet1966 said:
This
Click to expand...
Click to collapse
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.

Uzephi said:
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Click to expand...
Click to collapse
I am trying that one again. Factory reset didn't help either.

I did the flashall to 122-59-8. Now I am updating to 122-59-8-6

Comet1966 said:
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Click to expand...
Click to collapse
Which version of the bootloader? If the Oreo bootloader then perhaps this will result in an error.
If you installed Oreo Global or TMO after that, the bootloader will be upgraded to Oreo, perhaps this will lead to an error.

So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.

Comet1966 said:
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Click to expand...
Click to collapse
Wow, must've been some kind of bad flash previously? Either way glad that you've finally joined the rest of us!
Sent from my Moto Z (2) using Tapatalk

October patch: cannot update

Downloaded the October patches and now phone has been for 1h on spinning wheel with status "preparing system update"

I am new to stock ROM after years of custom ROMs that would update at least monthly. Now on Android 10 on my pixel 2 xl should I expect OTA updates automatically? I tried to update ROM in the settings menu and it still says I have the latest update but it is September not October. Do I have to reload the factory image? I'd much rather flash an update wIth TWRP or the phone to do it automatically. It is the only reason I chose to use the stock ROM rather than Lineage or something else that updates.

Anyone with the same problem or a solution?

Problem yes - Solution no. Worked the last few months without a problem but this month I cant update. Seems they screwed it up somehow.

Same here cannot update

You both mean that you don't find the update or that it downloads and then you get stuck on preparing system update?
My friend here managed to update...

thegios said:
Downloaded the October patches and now phone has been for 1h on spinning wheel with status "preparing system update"
Click to expand...
Click to collapse
almahix said:
I am new to stock ROM after years of custom ROMs that would update at least monthly. Now on Android 10 on my pixel 2 xl should I expect OTA updates automatically? I tried to update ROM in the settings menu and it still says I have the latest update but it is September not October. Do I have to reload the factory image? I'd much rather flash an update wIth TWRP or the phone to do it automatically. It is the only reason I chose to use the stock ROM rather than Lineage or something else that updates.
Click to expand...
Click to collapse
thegios said:
Anyone with the same problem or a solution?
Click to expand...
Click to collapse
D-m-x said:
Problem yes - Solution no. Worked the last few months without a problem but this month I cant update. Seems they screwed it up somehow.
Click to expand...
Click to collapse
humdrum2009 said:
Same here cannot update
Click to expand...
Click to collapse
Are all of you updating via OTA or factory image?

OTA

thegios said:
OTA
Click to expand...
Click to collapse
Then your full stock, bootloader locked I assume. Does side loading the OTA work?

Badger50 said:
Then your full stock, bootloader locked I assume. Does side loading the OTA work?
Click to expand...
Click to collapse
Full stock and locked bootloader.
How do I sideload an OTA?
I used to do it from Twrp but since I have a Pixel again I'm not unlocking or rooting any longer

thegios said:
Full stock and locked bootloader.
How do I sideload an OTA?
I used to do it from Twrp but since I have a Pixel again I'm not unlocking or rooting any longer
Click to expand...
Click to collapse
You can do it from stock recovery. Full instructions can be found here :good:
https://developers.google.com/android/ota

You mean "Apply update from Sd card"?

I have downloaded the OTA zip file, put in in the root of my phone, entered recovery mode and chosen "apply update from sd card" but then no file is found

rooted
is rooted sideload possible with twrp

thegios said:
I have downloaded the OTA zip file, put in in the root of my phone, entered recovery mode and chosen "apply update from sd card" but then no file is found
Click to expand...
Click to collapse
The OTA zip file should be in your platform-tools folder if I remember correctly.