https://www.google.com/android/beta
Factory Image direct link: http://storage.googleapis.com/andro.../walleye-ppp2.180412.013-factory-6406b348.zip
Opted in but I'm thinking like other developer previews, I probably should have not taken most current ota to may before. Oh well.. will wait until dp3 lol
...
My phone is rooted, I just received the update to install should I do it or do it manually?
xSunny said:
My phone is rooted, I just received the update to install should I do it or do it manually?
Click to expand...
Click to collapse
Do the OTA because a manual install won't receive future OTA updates.
---------- Post added at 07:37 PM ---------- Previous post was at 07:37 PM ----------
bmwh0r3 said:
Opted in but I'm thinking like other developer previews, I probably should have not taken most current ota to may before. Oh well.. will wait until dp3 lol
Click to expand...
Click to collapse
It should be fine since its the OTA update and not one you have to sideload
TechOut said:
It should be fine since its the OTA update and not one you have to sideload
Click to expand...
Click to collapse
It installed ota over Mays 8.1 update.
installed with custom recovery and magisk root and custom kernel. after reboot all work but lost magisk and xposed.
Where to find sideload ota.zip?
Just finished install and so far so good running very smooth no issues yet!
snowrelyt said:
[]
Factory Image direct link: []
Click to expand...
Click to collapse
Does everyone get this error when trying to download?
"Anonymous caller does not have storage.objects.get access to (I'm not allowed to post links yet )"
I upgraded via OTA (completely stock phone, so beware), but my phone no longer boots (system UI keeps restarting until eventually the phone reboots saying that my data may be corrupt and advising a factory reset), so I want to try flashing the factory image without wiping data, see if it helps.
dextart said:
Does everyone get this error when trying to download?
"Anonymous caller does not have storage.objects.get access to (I'm not allowed to post links yet )"
I upgraded via OTA (completely stock phone, so beware), but my phone no longer boots (system UI keeps restarting until eventually the phone reboots saying that my data may be corrupt and advising a factory reset), so I want to try flashing the factory image without wiping data, see if it helps.
Click to expand...
Click to collapse
Yes, it seems everyone is getting this error. It should be fixed soon.
Stock Verizon Pixel 2 XL here, signed up for Beta and checked for update, got the OTA. Installed just like any other update, works great.
snowrelyt said:
Yes, it seems everyone is getting this error. It should be fixed soon.
Click to expand...
Click to collapse
No not everyone is having this error mine isntalled rebooted and worked like a normal update
Can I update OTA when having TWRP and Magisk?
Mayex said:
Can I update OTA when having TWRP and Magisk?
Click to expand...
Click to collapse
Wouldn't an OTA require the factory bootloader
TechOut said:
No not everyone is having this error mine isntalled rebooted and worked like a normal update
Click to expand...
Click to collapse
I was talking about the error you get when you try to download the factory image.
Anyways, it looks like it's working now.
snowrelyt said:
I was talking about the error you get when you try to download the factory image.
Anyways, it looks like it's working now.
Click to expand...
Click to collapse
Yep, it does. Unfortunately for me, I managed to get myself into this mess with a locked bootloader and now only a full DP2 OTA .zip can maybe save me. Any chance anyone here has one?
Is Google Pay working on Android P DP2? This is what kept me from running DP1.
tibere86 said:
Is Google Pay working on Android P DP2? This is what kept me from running DP1.
Click to expand...
Click to collapse
The App starts up just fine and I was able to set it up without issues but I haven't tried using it for a payment yet
There is a magnifier when moving the text cursor. Finally....
Build is completely smooth and have May security patch. (I was expecting to have an older security patch like in previous betas).
I think is much smoother than Oreo...but let's see in a few days. Animations are nice.
The speed to switch between the last 2 apps is incredibly decreased with the new Home button gesture. But at least is not slow.
Sent from my Pixel 2
Related
Hi,
Anyone else having the following issues with ICS (stock, rooted):
Locked screen, using power button doesn't work
Reboot and stuck on Asus Logo?
both resulting in pressing on and power up to restart..
seems like this update isn't fully tested. I haven't done a full wipe, I simply updated through OTA... should I try this? If I do, can I do an ADB backup and restore?
Thanks folks
garpunkal said:
Hi,
Anyone else having the following issues with ICS (stock, rooted):
Locked screen, using power button doesn't work
Reboot and stuck on Asus Logo?
both resulting in pressing on and power up to restart..
seems like this update isn't fully tested. I haven't done a full wipe, I simply updated through OTA... should I try this? If I do, can I do an ADB backup and restore?
Thanks folks
Click to expand...
Click to collapse
its most likely because you were rooted and did modifications that caused the OTA to fail and mess something up.
The OTA itself was tested by ASUS, its you who did mods to the tablet that made the OTA fail for you. You'll most likely have to wipe and start all over. Or just DL a custom ROM.
zephiK said:
its most likely because you were rooted and did modifications that caused the OTA to fail and mess something up.
The OTA itself was tested by ASUS, its you who did mods to the tablet that made the OTA fail for you. You'll most likely have to wipe and start all over. Or just DL a custom ROM.
Click to expand...
Click to collapse
I wiped, totally cleaned the system, installed WW latest full blob then the update, and it occured. Just to note, my only mod was root, nothing else.
garpunkal said:
Hi,
Anyone else having the following issues with ICS (stock, rooted):
Locked screen, using power button doesn't work
Reboot and stuck on Asus Logo?
both resulting in pressing on and power up to restart..
seems like this update isn't fully tested. I haven't done a full wipe, I simply updated through OTA... should I try this? If I do, can I do an ADB backup and restore?
Thanks folks
Click to expand...
Click to collapse
WTF? You have errors. You no you didn't wipe.....Always Wipe. Always. ..Always... IF you don't and then get errors. wipe. Seriously....Wipe it. lol did I mention you should have wiped it?
zephiK said:
its most likely because you were rooted and did modifications that caused the OTA to fail and mess something up.
The OTA itself was tested by ASUS, its you who did mods to the tablet that made the OTA fail for you. You'll most likely have to wipe and start all over. Or just DL a custom ROM.
Click to expand...
Click to collapse
All I did was root... that shouldn't affect the OTA, especially as the OTA unrooted my device anyway!
I'll wipe now and let you know the outcomes.
fonix232 said:
I wiped, totally cleaned the system, installed WW latest full blob then the update, and it occured. Just to note, my only mod was root, nothing else.
Click to expand...
Click to collapse
'
Why did you do this; installed WW latest full blob then the update
Full wipe and then install the Full ICS WW. Thats all that should be needed.
so if I'm using stock rom and recovery... whats the best way to wipe.. through recovery or just through rom?
garpunkal said:
so if I'm using stock rom and recovery... whats the best way to wipe.. through recovery or just through rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1514658
OPTION B:
FULL version
In recovery do a full system reset. Delete that mofo.
Then install the Full US ICS zip.
can I use adb backup to restore all my apps and settings if I go for option B?
garpunkal said:
can I use adb backup to restore all my apps and settings if I go for option B?
Click to expand...
Click to collapse
I wouldn't. Atleast not right away. You have an issue. You don't no whats causing it. First Wipe and then reinstall. If after that you can't make the problem appear again, I would do a nandroid, and then attempt the restore of your apps. If no issues; Profit. But if you find issues after you can then restore to the nand and go through your apps one at a time to figure it out.
ok.
I still can't understand why this OTA on stock (rooted but unmodified) has problems.
I shouldn't have to wipe it.
garpunkal said:
ok.
I still can't understand why this OTA on stock (rooted but unmodified) has problems.
I shouldn't have to wipe it.
Click to expand...
Click to collapse
I have no real answers for you.
But I would assume its cause ICS updates the framework and countless other stuff that can't just be "updated". You would have thought they would have made the OTA auto Wipe. I would have. I could be completely off tho. Maybe its just broke. Lol
tweaked said:
'
Why did you do this; installed WW latest full blob then the update
Full wipe and then install the Full ICS WW. Thats all that should be needed.
Click to expand...
Click to collapse
- No ICS blob currently available
- This is the exact way everyone (I mean, every home user, without development background, etcetera, the "noobs") did it, who got the errors
So basically I did how officially it's done.
---------- Post added at 10:37 PM ---------- Previous post was at 10:36 PM ----------
tweaked said:
I have no real answers for you.
But I would assume its cause ICS updates the framework and countless other stuff that can't just be "updated". You would have thought they would have made the OTA auto Wipe. I would have. I could be completely off tho. Maybe its just broke. Lol
Click to expand...
Click to collapse
You're wrong. Asus made it in a way it shouldn't affect the system, yet, in some cases it does.
fonix232 said:
- No ICS blob currently available
- This is the exact way everyone (I mean, every home user, without development background, etcetera, the "noobs") did it, who got the errors
So basically I did how officially it's done.
---------- Post added at 10:37 PM ---------- Previous post was at 10:36 PM ----------
You're wrong. Asus made it in a way it shouldn't affect the system, yet, in some cases it does.
Click to expand...
Click to collapse
Well I said I could be wrong.
I wouldn't have done it that way.
On other Devices I have if you mess with the framework you have to full wipe. You can't just update. But, really what do I know. Im just a retard truely.
tweaked said:
I have no real answers for you.
But I would assume its cause ICS updates the framework and countless other stuff that can't just be "updated". You would have thought they would have made the OTA auto Wipe. I would have. I could be completely off tho. Maybe its just broke. Lol
Click to expand...
Click to collapse
I bet people (non tech saavy) would throw a fit if the update did a full wipe, even if it had a warning beforehand.
Toast95135 said:
I bet people (non tech saavy) would throw a fit if the update did a full wipe, even if it had a warning beforehand.
Click to expand...
Click to collapse
But I bet they would have still updated.
I swear Asus should fix these problems and they are more OTA updates issues and not the fact I didn't wipe.
Other people must be having these problems?!!?
garpunkal said:
I swear Asus should fix these problems and they are more OTA updates issues and not the fact I didn't wipe.
Other people must be having these problems?!!?
Click to expand...
Click to collapse
I had no real issues with ICS when I was running it. I just preffered OC and UV.
Once a kustom kernel is available I'll switch for good.
That said, there are a few threads with issues. Give a look through the first 4 pages for so.....
just reading a few of the other forums threads and loads of people are having these issues...
confused why it's not been fully tested...
garpunkal said:
just reading a few of the other forums threads and loads of people are having these issues...
confused why it's not been fully tested...
Click to expand...
Click to collapse
lol, you'd have to contact ASUS for that question and then you'd get some engrish answer about highly tested awesome upgrade.
Just received ota update to 4.4.4 45MB for xt 1045 lte usa version
djcody said:
Just received ota update to 4.4.4 45MB for xt 1045 lte usa version
Click to expand...
Click to collapse
The update isn't working for me, even after reflashing the stock recovery. Did you have to do anything special to get it to work, or have you not modified the ROM at all?
Mogster2K said:
The update isn't working for me, even after reflashing the stock recovery. Did you have to do anything special to get it to work, or have you not modified the ROM at all?
Click to expand...
Click to collapse
I had the stock 4.4.3 ROM rooted and with the Xposed Framework installed. No custom recovery or custom kernel ever installed (I always used "fastboot boot /path/to/recovery.img" rather than installing a recovery). The update worked fine for me. All I had to do was (after updating to 4.4.4) go into the Xposed framework installer, tell it to update/install the framework. I installed the 4.4.4 update through the OTA notification I received, not through the link in this thread. For me, the update was 41.1MB not 45MB. I downloaded the OTA over WiFi.
Before I installed the update, I booted ClockworkMod Recovery (again, booted not flashed) and made a nandroid backup. It couldn't backup my /data partition because it's encrypted, so I also made a full backup with Titanium Backup.
Full stock, no mods yet
Mogster2K said:
The update isn't working for me, even after reflashing the stock recovery. Did you have to do anything special to get it to work, or have you not modified the ROM at all?
Click to expand...
Click to collapse
I had same problem
I was on 4.3.3 stock using exposed installer, I used MotoToolAioV3 to restore stock recovery then took OTA, during install I kept getting an error.
The solution for me was to download stock recovery from here http://forum.xda-developers.com/showpost.php?p=53702274&postcount=268
extract the recovery then use MotoToolAioV3 to flash it, then accept the OTA and it should work, then if you're using exposed installer do what the other poster said and re-install xposed. Hope this helps.
castuis said:
I had same problem
I was on 4.3.3 stock using exposed installer, I used MotoToolAioV3 to restore stock recovery then took OTA, during install I kept getting an error.
The solution for me was to download stock recovery from here http://forum.xda-developers.com/showpost.php?p=53702274&postcount=268
extract the recovery then use MotoToolAioV3 to flash it, then accept the OTA and it should work, then if you're using exposed installer do what the other poster said and re-install xposed. Hope this helps.
Click to expand...
Click to collapse
Giving this a try, will report back
i just sad, I didn't mod anything because there is not yet full working ROM without bugs, mean the big one.
Anyway my One+ is on the way, Moto G is a good phone after breaking down my N4, going to sell soon
Got the update yesterday too working find no changes
Dialer still buggy
sonygoup said:
Got the update yesterday too working find no changes
Dialer still buggy
Click to expand...
Click to collapse
As I understand it, the main changes from 4.4.3 are compatibility with more SD cards, and some security updates to things like OpenSSL. I'm now able to use my 64GB Samsung EVO class 10 (MB-MP64DA/AM).
I managed to get the update installed after completely reflashing to stock (leaving the bootloader unlocked.)
sonygoup said:
Got the update yesterday too working find no changes
Dialer still buggy
Click to expand...
Click to collapse
The dialer is not buggy if you enable the animations in developer options (reset them to their default setting).
bozzykid said:
The dialer is not buggy if you enable the animations in developer options (reset them to their default setting).
Click to expand...
Click to collapse
Thanks dude
I turned it off because I hate it
New update is pretty great. Previously on 4.4.3 the radio would drop all connections seemingly at random when starting up a music app or YouTube, but after upgrading to 4.4.4 the radio seems to hold a much more consistent connection with fewer drops (none so far) . I previously thought this might have been a faulty SIM
:thumbup:
So if you want to hold off the OTA, this newer update to motoOTA stops all further ones.
Update, installs on 23.3.24 too hold off Lollipop if you like. Note, my speculation as Lolli has not arrived.
Will not install on su6/7!
It responds with: your SW up to date, lol!
It may work, rather NOT work, on previous builds too.
Source: not sure yet but the x 2014 or some new moto.
You will need Super Manager or the like to revert/uninstall.
BTW if you get in a pickle without this non functional app, the OTA is in cache. Once the OTA.zip is downloaded to /cache this app will not help. You must choose the install-later option then go to recovery & wipe cache. Once cache is wiped the damn recovery will not stop, you must hold the power to exit.
For some, if it does not work, I have attached screen shots of other Moto apps which may effect the OTA update.
Md5
aad5436c3b587b326865498a66a9cbb8
My Q now is should take the next update? Any issues with it? How is voLTE?
aviwdoowks said:
So if you want to hold off the OTA, this newer update to motoOTA stops all further ones.
It responds with: your SW up to date!
It may work on previous builds too.
Source: not sure yet.
You will need Super Manager or the like to revert/uninstall.
Click to expand...
Click to collapse
Installed it on my X running 4.4.4. Praying for root one day.
Root and BL unlock are more likely to happen on Lollipop than latest KitKat. Personally, I would take the OTA instead of holding my breath in hopes that a developer will waste time looking for an exploit on soon to be outdate firmware.
My .02 anyway...
aviwdoowks said:
So if you want to hold off the OTA, this newer update to motoOTA stops all further ones.
It responds with: your SW up to date, lol!
It may work on previous builds too.
Source: not sure yet but the x 2014 or some new moto.
You will need Super Manager or the like to revert/uninstall.
BTW if you get in a pickle without this the OTA is in cache, choose the later option then go to recovery & wipe cache. Once cache is wiped the damn recovery will not stop you must hold the power to exit.
Click to expand...
Click to collapse
So my unrooted Maxx is on 21.11.21 and I was getting the daily nag message to install the update. I installed this and still get the daily nag message. What exactly do I need to do? TIA
mblanton66 said:
So my unrooted Maxx is on 21.11.21 and I was getting the daily nag message to install the update. I installed this and still get the daily nag message. What exactly do I need to do? TIA
Click to expand...
Click to collapse
I presume the OTA got downloaded to cache, read the BTW....
That is, once the cache is filled the new app cannot stop it because it is in progress.
I did read the BTW.
Thanks, tho.
How are you supposed to remove it exactly? I've never used Super Manager before. Thank you in advance.
elvintopalov said:
How are you supposed to remove it exactly? I've never used Super Manager before. Thank you in advance.
Click to expand...
Click to collapse
SM has an apk manager which works in the free version.
It allows you to uninstall any data apk or updates of system apps, but not core/original system apps, (as well as BU any app) while unrooted.
I have the donate version.
aviwdoowks said:
So if you want to hold off the OTA, this newer update to motoOTA stops all further ones.
It responds with: your SW up to date, lol!
It may work, rather NOT work, on previous builds too.
Source: not sure yet but the x 2014 or some new moto.
You will need Super Manager or the like to revert/uninstall.
BTW if you get in a pickle without this the OTA is in cache. Once the OTA.zip is downloaded to /cache this app will not help. You must choose the install-later option then go to recovery & wipe cache. Once cache is wiped the damn recovery will not stop, you must hold the power to exit.
For some, if it does not work, I have attached screen shots of other Moto apps which may effect the OTA update.
Click to expand...
Click to collapse
Tried on a 2013 Moto X and still showing update available on 4.4.2
Here is an adb method which needs no root.
http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
From this thread
http://forum.xda-developers.com/showthread.php?p=57545543#post57545543
Hi all,
I got the update message(I'm on the RU firmware) but I'm also rooted and twrpd so my question is the following...Will the update process complete without me reverting to stock or will I have to before I go to 6.0?
Cheers
I don't recive the notification but I also wonder
I didn't have the patience to let the OTA download at a crawl while the servers are getting hammered, so I don't know, but I'm guessing it would fail. What I did do was download the full update from the MM thread, and "Install" it with TWRP (wiped cache etc after install). I haven't re-rooted yet, but it's running fine.
Sent from my YD201 using Tapatalk
hippy dave said:
I didn't have the patience to let the OTA download at a crawl while the servers are getting hammered, so I don't know, but I'm guessing it would fail. What I did do was download the full update from the MM thread, and "Install" it with TWRP (wiped cache etc after install). I haven't re-rooted yet, but it's running fine.
Click to expand...
Click to collapse
Did you wiped anything before installing it with the TWRP?
wilver said:
Did you wiped anything before installing it with the TWRP?
Click to expand...
Click to collapse
No, I used the button TWRP shows after install to wipe cache, but I kept my data. It's working fine for me so far but I can't promise it's not better to wipe it.
Sent from my YD201 using Tapatalk
Just check to see if they fixed the download speed problem and it looks like they've pulled the update out!
My download of the update cut out and now I can't see it either.
I stay with the Android 5 for the momment, the differences is worth it?
Well I did what hippy dave did and it seems to be working.
Something I wish could be customized is the bottom buttons on the EPD. The home button on the black theme is way too big :/
Done same as Dave, also installed superus and xposed, all fine =) other doubt I have, sometimes the back screen seens harder to unblock, anyone know why it happens or how to fix it? It have anything to do with the light in the place I am?
Nikolay1243D said:
Hi all,
I got the update message(I'm on the RU firmware) but I'm also rooted and twrpd so my question is the following...Will the update process complete without me reverting to stock or will I have to before I go to 6.0?
Cheers
Click to expand...
Click to collapse
From my fresh experience: install full version from torrent (http://4pda.ru/forum/dl/post/9988519/yotaphone2-user-full-RU1.1.47.zip.torrent) through TWRP, wipe cache, install SuperSU. And after that steps - reboot. All datas and apps on it's places.
Google Pixel October Factory and OTA Images are available to download with 4 functional updates and no security fixes.
OTA: https://dl.google.com/dl/android/aosp/sailfish-ota-ppr2.181005.003-db23e6d5.zip
Factory: https://dl.google.com/dl/android/aosp/sailfish-ppr2.181005.003-factory-727c51f5.zip
Boot image on my Google Drive: https://drive.google.com/file/d/1Krybqgb8BJcTI-67Pi2t9IQflOwW6YZo/view?usp=drivesdk
Changes:
Code:
- Improved performance for certain protected media formats (Pixel 2, Pixel 2 XL)
- Improved stability when using Android Auto (Pixel 2, Pixel 2 XL)
- Improved fast-charging behavior for Pixel devices (Pixel, Pixel XL)
- Modified Call Screening behavior when using Maps Navigation (All Pixels)
October security bulletin: https://source.android.com/security/bulletin/pixel/2018-10-01
So who's ready to fast charge on Pie?
Can someone explain what's the procedure to upgrade from a stock rooted ROM without loosing data? Will the package wipe data or keep it?
danial.aw said:
Can someone explain what's the procedure to upgrade from a stock rooted ROM without loosing data? Will the package wipe data or keep it?
Click to expand...
Click to collapse
If you install the OTA, you will not lose data. If you install the factory image, the installer will wipe everything by default. If you want to keep data, you have to edit the appropriate flash-all script to remove the "-w" switch, then save the script before running it.
Since you're already running stock rooted ROM, I suggest installing the OTA update through the following steps:
Boot to TWRP, go to Advanced -> ADB Sideload
Connect to computer
Follow the instructions at https://developers.google.com/android/ota
Be aware that you will lose TWRP and Magisk, and you'll have to reinstall them. You can reinstall Magisk from within the Magisk Manager app, or you can flash the .zip from TWRP.
Fast charge always worked for me on Pie, I don't get the hype.
still didn't get OTA( anyone on Verizon got it?
a1exus said:
still didn't get OTA( anyone on Verizon got it?
Click to expand...
Click to collapse
Get it and install it manually here:
https://developers.google.com/android/ota#sailfish
Hi, i got this problem that said "fingerprint hardware not available" randomly on my lockscreen when i tried to unlock my phone.
Is this possible to solve by flashing the Factory Images?
kntlbngsd said:
Hi, i got this problem that said "fingerprint hardware not available" randomly on my lockscreen when i tried to unlock my phone.
Is this possible to solve by flashing the Factory Images?
Click to expand...
Click to collapse
there is only one way to find out)
---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------
post-mortem said:
Get it and install it manually here:
https://developers.google.com/android/ota#sailfish
Click to expand...
Click to collapse
already did) thanks!
a1exus said:
still didn't get OTA( anyone on Verizon got it?
Click to expand...
Click to collapse
Are you enrolled in the Android Beta Program? Once I disenrolled I got the update.
z3pp3lin said:
Are you enrolled in the Android Beta Program? Once I disenrolled I got the update.
Click to expand...
Click to collapse
This also worked for me. I unenrolled and got it immediately.
wfraser207 said:
This also worked for me. I unenrolled and got it immediately.
Click to expand...
Click to collapse
Did the OTA wipe your phone? I was in the Beta program and am still waiting for the monthly security patch with the official version. When I select "Opt Out" on the Beta website it warns me that my data will be wiped...
cucumbers said:
Did the OTA wipe your phone? I was in the Beta program and am still waiting for the monthly security patch with the official version. When I select "Opt Out" on the Beta website it warns me that my data will be wiped...
Click to expand...
Click to collapse
Just install it manually, following Google's instructions. You won't lose data.
If you install the full factory image, you will lose data, by default. If you edit the script to remove the "-w" switch, then even that will not remove data.
Both of the above options require a computer.
post-mortem said:
Just install it manually, following Google's instructions. You won't lose data.
If you install the full factory image, you will lose data, by default. If you edit the script to remove the "-w" switch, then even that will not remove data.
Both of the above options require a computer.
Click to expand...
Click to collapse
Thanks. But I took the plunge, opted out of the Beta and did an OTA update anyway.
Turns out that if you had been in the Beta and got the final update to the official Android P build, you can opt out of Beta and start getting the OTAs again without your data getting wiped. You only get your data wiped if you are still on a Beta build when you leave. I should have remembered all of this, I did the exact same thing with the Android 8 Beta...
kentexcitebot said:
Google Pixel October Factory and OTA Images are available to download with 4 functional updates and no security fixes.
OTA: https://dl.google.com/dl/android/aosp/sailfish-ota-ppr2.181005.003-db23e6d5.zip
Factory: https://dl.google.com/dl/android/aosp/sailfish-ppr2.181005.003-factory-727c51f5.zip
Boot image on my Google Drive: https://drive.google.com/file/d/1Krybqgb8BJcTI-67Pi2t9IQflOwW6YZo/view?usp=drivesdk
Changes:
October security bulletin: https://source.android.com/security/bulletin/pixel/2018-10-01
So who's ready to fast charge on Pie?
Click to expand...
Click to collapse
How to get root and magisk on October update?
Currently on oreo custom ROM rooted with magisk, what's best way to upgrade, can I do so without losing root or will I need to re-root, and will I lose data? Or is it best to save data elsewhere and start completely fresh?
acidspider said:
Currently on oreo custom ROM rooted with magisk, what's best way to upgrade, can I do so without losing root or will I need to re-root, and will I lose data? Or is it best to save data elsewhere and start completely fresh?
Click to expand...
Click to collapse
Update to what? If there is a newer version of your custom ROM, follow the instructions in the relevant thread. If you want to upgrade to a different custom ROM or stock ROM, you'll have to reroot, unless the custom ROM is prerooted. You will likely need to backup and restore all user data.
So I realized that I'm still on the August update. I double checked to make sure I'm no longer enrolled in the beta program and still no updates pop. Am I able to flash the OTA in twrp?
SkinnyT said:
So I realized that I'm still on the August update. I double checked to make sure I'm no longer enrolled in the beta program and still no updates pop. Am I able to flash the OTA in twrp?
Click to expand...
Click to collapse
OTA flashing in TWRP has been hit and miss over the past couple of years (some TWRP/OS versions have worked while others haven't). I honestly don't know the current status, but since you are obviously BL unlocked it is easier to just install the factory image with the flash-all . Delete the -w from the batch file to keep your data of course. Either way, you will need to root again and install TWRP if you want to replace the factory recovery. The only difference is that the factory image will not swap you into the other A/B partition automatically.
SkinnyT said:
So I realized that I'm still on the August update. I double checked to make sure I'm no longer enrolled in the beta program and still no updates pop. Am I able to flash the OTA in twrp?
Click to expand...
Click to collapse
Yes, you can flash the OTA manually. Follow the instructions here. Make sure you are using the latest version of TWRP.
Works fine in twrp.
Sent from my Pixel XL using Tapatalk