Related
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..
Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.
inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app
I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...
Never mind
I received a Motorola OTA notification for a minor maintenance update which patched the "stagefright" vulnerability in my Moto X 2014 Pure Edition xt1095. I captured the OTA ZIP file from my cache folder, and it is attached to this post. Size of OTA ZIP is 4.29MB. (Note that Motorola OTA updates are named for the software version from which you must apply the update, not the software version to which you are upgrading.)
This is for a stock, unrooted xt1095 running Android Lollipop 5.1.
Prerequisite:
System version: 23.16.3
Build number: LPE23.32-21.6 or LPE23.32-21.3
After update:
System version: 23.16.6
Build number: LPE23.32-21.6 or LPE23.32-21.3 (unchanged)
You should be able to adb sideload this from stock recovery if you know how. If you're rooted, you'll need to request the stock 23.16.3 firmware from Motorola, and at least flash system.img and recovery.img to get back to stock system and recovery. After you do that, you might be able to sideload the OTA zip.
Deleted, sorry.
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.
Thanks thenestor and Romracer worked perfectly as stated I went with twrp flash -
I just installed this update from the stock recovery and it worked flawlessly. Thanks for uploading this. My wife got it a few days ago and updated before I could grab the the zip file.
Sent from my XT1095 using Tapatalk
Flintberg said:
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.
Click to expand...
Click to collapse
System.img? Download please
I reflashed system.img of my current version and then flashed the zip in twrp.
romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?
I'm rooted with adaway applied, I tried flashing romracer's file but I'm stuck on the boot screen saying that my bootloader is unlocked. Is it because of adaway?
romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thank you so much for this! I lost my stock recovery so this is a godsend.
Flintberg said:
I reflashed system.img of my current version and then flashed the zip in twrp.
Click to expand...
Click to collapse
system.img have the backup to download and can flash? Sorry my english
tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
I'm having the same problem! Any idea how to fix it?
Damn. That file from romracer broke my phone
seriously....i can't fix it
@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops
sh33z0r said:
@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops
Click to expand...
Click to collapse
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
supremekizzle said:
Damn. That file from romracer broke my phone
seriously....i can't fix it
Click to expand...
Click to collapse
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
macravin said:
I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?
Click to expand...
Click to collapse
RSchmauk said:
I'm having the same problem! Any idea how to fix it?
Click to expand...
Click to collapse
Did you have Xposed install? Reflash the install zip. Otherwise see above.
romracer said:
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
Did you have Xposed install? Reflash the install zip. Otherwise see above.
Click to expand...
Click to collapse
i was rooted with xposed only, and now my phone won't turn on, stuck on the boot screen...
i have two questions,
If i reflash system.img, will that wipe anything?
is there a system.img only file that i can download, downloading 1.1 gbs on my slow connection will take 4 hours, i can't afford 4 hours without a phone....
After the ota, my phone won`t turn on, like many here. What i`m worried about is that my PC is not recognizing my phone in adb. What can I do?
I was also rooted, with stock everything else but hung on the unlocked bootloader warning screen. I'm thinking AdAway or Greenify must have modified /system since that's really the only root stuff I use. For the time being I just restored my /system backup and it's working but I'll eventually need to flash stock system.img I'm guessing. Otherwise I'm gonna end up accidentally tapping the update nag screen and screwing it up again.
*NOTE: I tried to update my XT1575 Moto-X Pure Edition from a file on this page and it was a disaster! I now have the OTA visible on my phone, see screenshot, that keeps popping up. My phone is currently rooted, unlocked, and has TWRP installed, all courtesy of WinDroid tool. Windroid was painless, easy, and got the job done pretty quickly. Now that I can take the OTA update, is there an instruction page somewhere showing how to take the upgrade and keep root and recovery TWRP? That is the gist of what I really need.
I have a new Motorola Moto-X Pure Edition, rooted and TWRP with WinDroid app from Windows. This made it incredibly easy to unlock bootloader, install TWRPm and root. I am very happy with this system and some Xposed modules. I heard all the hoopla about the new Marshmallow rollout but did not have it offered to me on this phone. So, I did it manually from this page:
Stock/Rooted/Debloated X1575 6.0 MPH24.49-18
So much to choose from so I downloaded the moto_x_pure_edition_rooted_x1575_mph24.49-18_v1-deodexed.zip and flashed it in TWRP, after making a nandroid backup in TWRP. Everything seemed to work fine but I had problems after problems. My 32 GB ext-sdcard "vanished" and the system insisted that I reformat the card as "Portable" or "Permanent". I chose portable. I could not get Xposed working properly. My password manager would not work, when I updated from the play store, I got the message that all Android 6 apps now require a password at first run. Huh? What password? None of the passwords I have for the password managers would open the app.
Before losing 30+ GB of data on my ext-sdcard, I copied it to PC, then when complete I put it back in the phone, allowed the format as portable, then pulled the card and restored my stuff. Nothing was working right and it was pretty scary as this is my only phone. I restored the TWRP backup and had some settling in issues, but it worked, all but for WiFi. I could not turn it on! Like a spring on the switch, the moment you switched on WiFi, it snapped right back to the OFF position. No more WiFi. A friend sent me a stock recovery zip file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip.
This file, once unzipped, will flash the entire phone back to stock. He send me a small modem-flash.bat file because he thinks that I have an Android 6 radio in an Android 5 device. After running the flash-modem.bat, I got my WiFi back.
flash-modem.bat
Code:
@ECHO Off
@Echo Test
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
.fastboot reboot
Now I am really, really gun shy. I now have the dreaded update message on my phone, see screenshot. I found some good instructions here:
[GUIDE] Unlock/Root/Flash for Moto X Style/Pure
Are these instructions safe if I take the OTA update?
What preparations should be made prior to taking OTA aside from a TWRP backup?
Must I really format my ext-sdcard to use Marshmallow?
What other kind of weird things will happen?
Thank you so much, scared "sheetless in Florida"
:
Ohmster said:
*NOTE: I tried to update my XT1575 Moto-X Pure Edition from a file on this page and it was a disaster! I now have the OTA visible on my phone, see screenshot, that keeps popping up. My phone is currently rooted, unlocked, and has TWRP installed, all courtesy of WinDroid tool. Windroid was painless, easy, and got the job done pretty quickly. Now that I can take the OTA update, is there an instruction page somewhere showing how to take the upgrade and keep root and recovery TWRP? That is the gist of what I really need.
I have a new Motorola Moto-X Pure Edition, rooted and TWRP with WinDroid app from Windows. This made it incredibly easy to unlock bootloader, install TWRPm and root. I am very happy with this system and some Xposed modules. I heard all the hoopla about the new Marshmallow rollout but did not have it offered to me on this phone. So, I did it manually from this page:
Stock/Rooted/Debloated X1575 6.0 MPH24.49-18
So much to choose from so I downloaded the moto_x_pure_edition_rooted_x1575_mph24.49-18_v1-deodexed.zip and flashed it in TWRP, after making a nandroid backup in TWRP. Everything seemed to work fine but I had problems after problems. My 32 GB ext-sdcard "vanished" and the system insisted that I reformat the card as "Portable" or "Permanent". I chose portable. I could not get Xposed working properly. My password manager would not work, when I updated from the play store, I got the message that all Android 6 apps now require a password at first run. Huh? What password? None of the passwords I have for the password managers would open the app.
Before losing 30+ GB of data on my ext-sdcard, I copied it to PC, then when complete I put it back in the phone, allowed the format as portable, then pulled the card and restored my stuff. Nothing was working right and it was pretty scary as this is my only phone. I restored the TWRP backup and had some settling in issues, but it worked, all but for WiFi. I could not turn it on! Like a spring on the switch, the moment you switched on WiFi, it snapped right back to the OFF position. No more WiFi. A friend sent me a stock recovery zip file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip.
This file, once unzipped, will flash the entire phone back to stock. He send me a small modem-flash.bat file because he thinks that I have an Android 6 radio in an Android 5 device. After running the flash-modem.bat, I got my WiFi back.
flash-modem.bat
Code:
@ECHO Off
@Echo Test
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
.fastboot reboot
Now I am really, really gun shy. I now have the dreaded update message on my phone, see screenshot. I found some good instructions here:
[GUIDE] Unlock/Root/Flash for Moto X Style/Pure
Are these instructions safe if I take the OTA update?
What preparations should be made prior to taking OTA aside from a TWRP backup?
Must I really format my ext-sdcard to use Marshmallow?
What other kind of weird things will happen?
Thank you so much, scared "sheetless in Florida"
:
Click to expand...
Click to collapse
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Hi Ohmster. Hope you are well. I experienced the exact same "mess" as you have. In fact, I had the identical setup (Lollipop, TWRP, Nova, etc.). I tried the FLASH-ALL approach multiple times as well as separate reflash of the modem included in the CLARK_RETUS zip (followed steps line by line). But I'm still stuck without wifi (slides back to "off" immediately). prior to all this, I did a factory wipe as well as subsequent "fastboot -w". Any ideas? I'm on day 3 without a phone Thanks in advance for your wisdom!!
nypeach said:
Hi Ohmster. Hope you are well. I experienced the exact same "mess" as you have. In fact, I had the identical setup (Lollipop, TWRP, Nova, etc.). I tried the FLASH-ALL approach multiple times as well as separate reflash of the modem included in the CLARK_RETUS zip (followed steps line by line). But I'm still stuck without wifi (slides back to "off" immediately). prior to all this, I did a factory wipe as well as subsequent "fastboot -w". Any ideas? I'm on day 3 without a phone Thanks in advance for your wisdom!!
Click to expand...
Click to collapse
Hi Ohmster. Seems that your "positive mojo" did the trick... I tried one more time and finally up and running. Thanks for your posts and wisdom!!!
samwathegreat said:
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Click to expand...
Click to collapse
Do you think it would work if I did a Full Unroot using SuperSU and then uninstalled it using TiBu. Then flashed stock recovery using the restore to stock tool. So at that point I would have unrooted, removed SuperSu, and flashed back the stock recovery image. Do you think this would do the trick, or is it just best to completely flash the entire device using the restore to stock tool in full. I can recover from a soft brick but don't want a complete brick. Do you think my method is worth a try and that it wouldn't cause a complete brick condition? I would like to not have to reset my phone completely, but will if that is the only best way to get onto MM. Thanks.
nypeach said:
Hi Ohmster. Seems that your "positive mojo" did the trick... I tried one more time and finally up and running. Thanks for your posts and wisdom!!!
Click to expand...
Click to collapse
Actually my XT1575 is running and is in good shape now. I was lucky, @OldBaldy got on Hangouts with me and walked me through it. He sent me a large file which I believe to be the original stock rom for the Moto-X with a flash.bat file in so as long as you have your Windows drivers installed with ADB and Fastboot working. It took me the entire night to get that working with the correct drivers because Baldy had to go to bed.
The file I really needed for this is a 1.27 GB file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip. He told me NOT to run the FLASH-ALL.bat inside because all he wanted to do was reset the WiFi radio from an Android 6 radio to an Android 5 radio. Baldy was really smart and edited the restore system bat file to a tiny little "StockROM_FlashModem.txt" and it worked! WiFi came right back!
After that, I had to use adb over USB to flash the system back to original lollipop with no root, take the OTA update, then flash the boot.image file, update done, then flash the boot.img before installing SuperSU and most of this we did with ADB over USB. You cannot flash BETA-SuperSU-v2.52.zip until you flash that boot.img file.
If I was smart, I would have copy/pasted all the adb stuff we did into a text file, but of course, I didn't. But yes it is all working quite well now.
BEWARE:
Xposed does work in MM but not everything. I had to go back to TWRP, remove Xposed, and then enable only a couple of them that I know are safe like AdBlocker and Greenify.
I cannot give you anymore details since I screwed it up myself a couple of times and ended up redoing it on my own and again with Baldy's help.
NOTE:
Baldy did want something out of all this help he was giving me, he wanted the very first nandroid TWRP backup system files that I made immediately as soon as I got the update done because that is a perfectly clean backup and if you ever wanted to put your phone back to stock, that backup would do it.
Before giving up on Xposed and being sure that this was lousing up my phone; self boots, black screen, would not boot, bootloop, etc., I finally realized that this phone actually WORKS, man. It has to be the Xposed files,and modules that are causing the problems. And after removing all but the 2 I mentioned, the phone works great now. I will add more modules, very, very slowly and test each one for a couple of days before I clear it and dare add another one.
Ohmster said:
Actually my XT1575 is running and is in good shape now. I was lucky, @OldBaldy got on Hangouts with me and walked me through it. He sent me a large file which I believe to be the original stock rom for the Moto-X with a flash.bat file in so as long as you have your Windows drivers installed with ADB and Fastboot working. It took me the entire night to get that working with the correct drivers because Baldy had to go to bed.
The file I really needed for this is a 1.27 GB file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip. He told me NOT to run the FLASH-ALL.bat inside because all he wanted to do was reset the WiFi radio from an Android 6 radio to an Android 5 radio. Baldy was really smart and edited the restore system bat file to a tiny little "StockROM_FlashModem.txt" and it worked! WiFi came right back!
After that, I had to use adb over USB to flash the system back to original lollipop with no root, take the OTA update, then flash the boot.image file, update done, then flash the boot.img before installing SuperSU and most of this we did with ADB over USB. You cannot flash BETA-SuperSU-v2.52.zip until you flash that boot.img file.
If I was smart, I would have copy/pasted all the adb stuff we did into a text file, but of course, I didn't. But yes it is all working quite well now.
BEWARE:
Xposed does work in MM but not everything. I had to go back to TWRP, remove Xposed, and then enable only a couple of them that I know are safe like AdBlocker and Greenify.
I cannot give you anymore details since I screwed it up myself a couple of times and ended up redoing it on my own and again with Baldy's help.
NOTE:
Baldy did want something out of all this help he was giving me, he wanted the very first nandroid TWRP backup system files that I made immediately as soon as I got the update done because that is a perfectly clean backup and if you ever wanted to put your phone back to stock, that backup would do it.
Before giving up on Xposed and being sure that this was lousing up my phone; self boots, black screen, would not boot, bootloop, etc., I finally realized that this phone actually WORKS, man. It has to be the Xposed files,and modules that are causing the problems. And after removing all but the 2 I mentioned, the phone works great now. I will add more modules, very, very slowly and test each one for a couple of days before I clear it and dare add another one.
Click to expand...
Click to collapse
Hi Ohmster. Thanks again. So are you on Marshmallow? I got back with your info above and back to 5.1.1 (CLETUS). I tried to take the OTA and it downloaded, went to install, and I watched it just say "error" while on the installation screen. I'm going to try again. Let me know if you all set or in the same boat Thanks again!
samwathegreat said:
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Click to expand...
Click to collapse
nypeach said:
Hi Ohmster. Thanks again. So are you on Marshmallow? I got back with your info above and back to 5.1.1 (CLETUS). I tried to take the OTA and it downloaded, went to install, and I watched it just say "error" while on the installation screen. I'm going to try again. Let me know if you all set or in the same boat Thanks again!
Click to expand...
Click to collapse
Did you get back to stock using CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip? I have still not gone through the process yet as I am concerned about messing up the process. I want to ask a few questions here. I am well accustomed to fastboot flashing but want to be exactly sure of what to flash and the reason for doing it. I am on stock 5.1.1 LP with bootloader unlocked and rooted with SuperSU. So first I need to use Shawn5162's zip to restore me back to complete stock without root, then I need to go in and setup the phone to at least get the MM OTA, then install the OTA and hope all goes well. Lastly, to root again I need to use Shawn5162's zip to flash boot.img only, then flash TWRP, and finally flash SuperSU again. Is all this correct? Thank you.
robn30 said:
Did you get back to stock using CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip? I have still not gone through the process yet as I am concerned about messing up the process. I want to ask a few questions here. I am well accustomed to fastboot flashing but want to be exactly sure of what to flash and the reason for doing it. I am on stock 5.1.1 LP with bootloader unlocked and rooted with SuperSU. So first I need to use Shawn5162's zip to restore me back to complete stock without root, then I need to go in and setup the phone to at least get the MM OTA, then install the OTA and hope all goes well. Lastly, to root again I need to use Shawn5162's zip to flash boot.img only, then flash TWRP, and finally flash SuperSU again. Is all this correct? Thank you.
Click to expand...
Click to collapse
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
OldBaldy said:
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
robn30 said:
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
Click to expand...
Click to collapse
That boot img is for style only, not for pure. There is another called boot_root_mm_clark_retus.zip
Search for that file, it's the one you need for Supersu 2.5.2
You can use either supersu 252 of 256. I used 252 and have had no problems. If you have flashed TWRP, just put the supersu of your choice and the boot_root.zip files on you phone and flash with TWRP.
Sent from my XT1575 using Tapatalk
OldBaldy said:
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
IGNORE ME My Bad.... Back at 5.1.1 and staying here for a while Thanks again for your awesome support. I really appreciate it.
nypeach said:
Hi OldBaldy. Sorry I'm still having a tough time. As mentioned, I got back to 5.1.1 per the above process. I read your latest note and flashed the latest twrp (2.8.7.1) and took the MM OTA. It's now flashing the "teamwin" screen over and over. Should I be patient or bail? Thanks again for your patience and help!!!
Click to expand...
Click to collapse
You have to take the OTA BEFORE you flash TWRP. What you need to do now is get back into fastboot and flash the stock recovery img from the 5.1.1 factory image. Then reboot into system and take the OTA. After it installs, then follow the above instructions.
Sent from my XT1575 using Tapatalk
robn30 said:
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
Click to expand...
Click to collapse
No, that is the wrong root img to flash prior to installing SuperSU 2.52.
File Type: zip boot_root_mm_clark_retus.zip - [Click for QR Code] (10.01 MB, 756 views)
The file you want is in this post #290
Ohmster said:
No, that is the wrong root img to flash prior to installing SuperSU 2.52.
File Type: zip boot_root_mm_clark_retus.zip - [Click for QR Code] (10.01 MB, 756 views)
The file you want is in this post #290
Click to expand...
Click to collapse
Yup, I realized that plus someone else informed me that wasn't the one. I got her all taken care of and she is up and running smooth as can be. The battery on MM is really good. I'm impressed. I also wrote up a huge how to on the whole process and posted it. Should contain all the necessary steps in one place now. It gets a bit crazy having to dig all over the place to gather all that is needed. These threads get quite large and finding stuff gets more difficult as the days go by.
Sent from my XT1575 using Tapatalk
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
You must do the following:
1. Return to complete stock - that means get rid of root and TWRP. Best way to do that is download the factory image from Google, extract the boot, recovery, and system images from the factory image, and Flash those, for example: fastboot flash recovery recovery.img Don't flash data.img so you can keep your data.
2. OTAs depend on stock recovery to load, so now that you're back to stock, you have 2 choices. You can simply boot your phone normally, wait for the notification for the update, install it, and you're done - or, you can access android's stock recovery and side load the OTA zip using ADB. Good luck
Sent from my Nexus 6P using Tapatalk
Gamer_Josh said:
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
Click to expand...
Click to collapse
I forgot to mention that I also had TWRP recovery installed. The result was like it is with a normal OTA update, as none of my data/apps/settings were affected. Worked like a charm!
DJBhardwaj said:
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
ponzi314 said:
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
Click to expand...
Click to collapse
You are sure that you used the correct OTA file?
DJBhardwaj said:
You are sure that you used the correct OTA file?
Click to expand...
Click to collapse
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
ponzi314 said:
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
Click to expand...
Click to collapse
That's weird. It has worked for me everytime, and most users here.
DJBhardwaj said:
That's weird. It has worked for me everytime, and most users here.
Click to expand...
Click to collapse
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
tech_head said:
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
Click to expand...
Click to collapse
Sideloading the update, right?
DJBhardwaj said:
Sideloading the update, right?
Click to expand...
Click to collapse
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
tech_head said:
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
Click to expand...
Click to collapse
I also avoid using any toolkits. Yes I know they are fast and easy, and of course someone's hardwork. But I like to everything manual, same as you. :highfive:
I usually like to do things like that manually, because I like to know how things work. But I was under a bit of a time crunch at that point, so decided to try the Nexus Root Toolkit. Though I do understand the procedure of sideloading OTA updates via ADB, from researching and reading on the forums here.
Anywho, I hope you are able to get it going OP.
The OTA fixed it for me, thank you so much!
This is my first oneplus and non-carrier device and I'm unsure of whether to accept this OTA update. I'm pretty sure I would lose root, maybe twrp but stay unlocked? My concern is having to wipe device again. Without an SD card I'd have to transfer a lot of stuff back and forth.
I read that I could just flash magisk from TWRP after installing an OTA update. I took the update and now my phone thinks I just installed the OS for the first time and TWRP is gone. So.... don't do that.
I am SO frustrated. I should have read more posts.
Bubba Fett said:
This is my first oneplus and non-carrier device and I'm unsure of whether to accept this OTA update. I'm pretty sure I would lose root, maybe twrp but stay unlocked? My concern is having to wipe device again. Without an SD card I'd have to transfer a lot of stuff back and forth.
Click to expand...
Click to collapse
My method:
Download the TWRP 3.2.3-22 installer zip to your device https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Download the full 1.6 GB ZIP to your device - OnePlus6TOxygen_34_OTA_018_all_1812260723_29c01e732b714cfa.zip
https://forum.xda-developers.com/on...os-9-0-4-ota-oneplus-6t-t3860953/post78026655
Boot into recovery and install TWRP 3.2.3-22 zip
Reboot Recovery
Backup (see next post)
Install the full 1.6 GB download
Install TWRP 3.2.3-22 zip again
Reboot Recovery
Flash Magisk-v18.0.zip
Reboot System
Sent from my crosshatch using XDA Labs
Follow the guide here: Link
If you have TWRP, and are rooted:
- Download the full package from above.
- Boot to TWRP, flash that full ROM package you downloaded.
- Flash the TWRP installer.
- Reboot to recovery. (The ROM installs to the opposite slot, so rebooting to recovery again switches to that slot that you just installed that update to)
- Now that you are in TWRP again install Magisk.
- Reboot to System.
- No data or Apps lost. You will be good to go.
I get it now. Little different than I'm used to. Thanks!
Edit.. Just saw the answer to my question farther into the link. I thought it was for devs. Thanks for not beating me up! ?
valzi said:
I read that I could just flash magisk from TWRP after installing an OTA update. I took the update and now my phone thinks I just installed the OS for the first time and TWRP is gone. So.... don't do that.
I am SO frustrated. I should have read more posts.
Click to expand...
Click to collapse
I did something similar, but just flashed twrp using adb again, like you did the first time. Then flash the twrp installer after. It made twrp stick when you reboot to recovery. Don't forget to flash Magisk again. The link in post 4 is great. wish I would have read it before asking.
It was so much easier on my Oneplus One. I just took OTA updates without doing anything unusual at all. No flashing. I was using a custom rom though. Maybe that's the answer now?
Or maybe I should just unroot and deal with the inconveniences of an unrooted phone.
Well, first of all you want lose your data when you do upgrade through OTA.
If you use magisk, tap uninstall and restore images. Then do OTA update but do not reboot. Clear recent apps and go back to magisk: install it to inactive slot. Then reboot.
You will lose customer recovery though, so if you want it, sideload it again with PC.
geminium said:
Well, first of all you want lose your data when you do upgrade through OTA.
If you use magisk, tap uninstall and restore images. Then do OTA update but do not reboot. Clear recent apps and go back to magisk: install it to inactive slot. Then reboot.
You will lose customer recovery though, so if you want it, sideload it again with PC.
Click to expand...
Click to collapse
What is the advantage to this method?
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
OhioYJ said:
Follow the guide here: Link
If you have TWRP, and are rooted:
- Download the full package from above.
- Boot to TWRP, flash that full ROM package you downloaded.
- Flash the TWRP installer.
- Reboot to recovery. (The ROM installs to the opposite slot, so rebooting to recovery again switches to that slot that you just installed that update to)
- Now that you are in TWRP again install Magisk.
- Reboot to System.
- No data or Apps lost. You will be good to go.
Click to expand...
Click to collapse
If I have TWRP, do I still need to uninstall Magisk, or can I just follow the TWRP guide and skip the Magisk guide?
@valzi I don't remove Magisk when doing the updates. I just reinstall. I always use the TWRP method.
valzi said:
What is the advantage to this method?
Click to expand...
Click to collapse
I've only used this method, the only thing I can think of is, it's just easier. Go into Magisk, click Uninstall, click restore images, don't reboot, do your OTA update, don't reboot after it's done, go back into Magisk, click install, then click install to slot (Or something like that. It'll say after OTA next to it.) All of those steps are done within Android and not recovery. Do note though, I haven't tried it with custom recovery INSTALLED on my device. YMMV
OMGWTFISTHIS said:
I've only used this method, the only thing I can think of is, it's just easier. Go into Magisk, click Uninstall, click restore images, don't reboot, do your OTA update, don't reboot after it's done, go back into Magisk, click install, then click install to slot (Or something like that. It'll say after OTA next to it.) All of those steps are done within Android and not recovery. Do note though, I haven't tried it with custom recovery INSTALLED on my device. YMMV
Click to expand...
Click to collapse
Hmm. That seems a lot more complicated to me if you have to lose your data though.
---------- Post added at 03:04 AM ---------- Previous post was at 02:57 AM ----------
OhioYJ said:
@valzi I don't remove Magisk when doing the updates. I just reinstall. I always use the TWRP method.
Click to expand...
Click to collapse
Thanks for the help!