Related
As a long time Android power user, I rooted my Nexus as soon as I got the phone. However, I completely forgot about the best thing Nexus devices have to offer, OTA updates.
I completely ditched OTA before since I was on custom ROMs most of the time on other devices.
So here are the questions.
1) How will modifying the system partition affect OTAs? Will they still show up and I won't be able to install them?
2) How can I get OTA back and working? Does a simple "fastboot flash system/boot system.img/boot.img" with the stock system and boot partition fix the issue? If not, what do I do? And will it involve data wiping?
3) If I don't do those, I can still do a manual update for the system partition using fastboot, correct?
Note: I rooted the device using the Nexus Toolkit method over at the dev sub.
Sent from my Nexus 6P using XDA Forums
341464 said:
As a long time Android power user, I rooted my Nexus as soon as I got the phone. However, I completely forgot about the best thing Nexus devices have to offer, OTA updates.
I completely ditched OTA before since I was on custom ROMs most of the time on other devices.
So here are the questions.
1) How will modifying the system partition affect OTAs? Will they still show up and I won't be able to install them?
2) How can I get OTA back and working? Does a simple "fastboot flash system/boot system.img/boot.img" with the stock system and boot partition fix the issue? If not, what do I do? And will it involve data wiping?
3) If I don't do those, I can still do a manual update for the system partition using fastboot, correct?
Note: I rooted the device using the Nexus Toolkit method over at the dev sub.
Sent from my Nexus 6P using XDA Forums
Click to expand...
Click to collapse
1. They'll still show up, but any attempt to install them will fail.
2. See my guide.
3. Yes.
Heisenberg said:
1. They'll still show up, but any attempt to install them will fail.
2. See my guide.
3. Yes.
Click to expand...
Click to collapse
So wait, what's the status now on the latest SuperSU package? I've heard that its system-less installation now?
Sent from my Nexus 6P using XDA Forums
341464 said:
So wait, what's the status now on the latest SuperSU package? I've heard that its system-less installation now?
Sent from my Nexus 6P using XDA Forums
Click to expand...
Click to collapse
There are two versions, the traditional version, and the systemless version.
Heisenberg said:
There are two versions, the traditional version, and the systemless version.
Click to expand...
Click to collapse
Speaking of OTA and systemless. I have opted for the systemless root method. If I want to install an OTA, all I have to do is flash the stock boot image, install update, then re root correct? Assuming there are no changes to system?
Sent from my Nexus 6P using Tapatalk
Hello there,
I thought that there were more people with this problem, but I've this problem: first off, I got stock MM installed on my Style xt1572. Unlocked bootloader and the latest TWRP. But when I try to install SuperSU via TWRP, it just get stuck before the reboot animation. Any idea's what I could try perhaps?
Edit: Solution is just using the SuperSU in this thread: http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792
Thanks.
Did you select install SuperSU when twrp asked ? After flashing newest supersu?
Sent from my XT1575 using Tapatalk
Settler11 said:
Hello there,
I thought that there were more people with this problem, but I've this problem: first off, I got stock MM installed on my Style xt1572. Unlocked bootloader and the latest TWRP. But when I try to install SuperSU via TWRP, it just get stuck before the reboot animation. Any idea's what I could try perhaps?
Thanks.
Click to expand...
Click to collapse
Which SuperSU version are you using?
Settler11 said:
Hello there,
I thought that there were more people with this problem, but I've this problem: first off, I got stock MM installed on my Style xt1572. Unlocked bootloader and the latest TWRP. But when I try to install SuperSU via TWRP, it just get stuck before the reboot animation. Any idea's what I could try perhaps?
Thanks.
Click to expand...
Click to collapse
Men i have the same problem and i dont know what to do :/
@patt yes.
@Doktaphex The one TWRP asked me to install and the latest beta. 2.49. Same problem.
Depending on the version of SuperSU that you are using there are 2 different rooting methods.
My suggestion would be to use the systemless root option here: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
v2.65 is what you want. When you flash this in twrp it will automatically patch the boot image on your device (whilst also creating a backup of the original). It sounds as though you are both trying to use a version of SuperSU that implements the standard rooting method, this would mean that you must manually flash a modified boot image in order to bypass Android 6.0's internal system modification checks!
Flash the stock boot.img. Then see if it boots. Then ^^^ this^^^
Settler11 said:
@patt yes.
@Doktaphex The one TWRP asked me to install and the latest beta. 2.49. Same problem.
Click to expand...
Click to collapse
Do not allow twrp to attempt to install superSU
IMPORTANT!!!!
Because you have already allowed twrp to do this, you will need to reflash your system partition to ensure that all traces of that version of SuperSU are removed before you flash the newer version.
I hope this helps you guys.
patt2k said:
...
reflash your system partition
....
Click to expand...
Click to collapse
What do you mean with that? We've to reflash a rom, kernel? What?
Settler11 said:
@patt yes.
@Doktaphex The one TWRP asked me to install and the latest beta. 2.49. Same problem.
Click to expand...
Click to collapse
You are not suppose to click install superSU when twrp asks for it.
Sent from my XT1575 using Tapatalk
patt2k said:
You are not suppose to click install superSU when twrp asks for it.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Yes.. But as you can see, I've done that already. But I got a restore without it. But even if I install that latest beta, the problem still presumes.
Settler11 said:
What do you mean with that? We've to reflash a rom, kernel? What?
Click to expand...
Click to collapse
Sorry, I should have been more clear in my instructions. I would go ahead and reflash the rom that you want to use and then flash superSU v2.65.
Reboot and if twrp asks if you want it to install superSU choose the option for it NOT to do so.
Settler11 said:
Yes.. But as you can see, I've done that already. But I got a restore without it. But even if I install that latest beta, the problem still presumes.
Click to expand...
Click to collapse
I had this issue but I had backup of my stock rooted rom. I'd suggest maybe go back to stock with restore tool?
Sent from my XT1575 using Tapatalk
patt2k said:
I had this issue but I had backup of my stock rooted rom. I'd suggest maybe go back to stock with restore tool?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I'M on stock! And that restore tool is for Pure, not Style! And I don't want to install a custom rom. Stock rom is still fine for me.
Settler11 said:
I'M on stock! And that restore tool is for Pure, not Style! And I don't want to install a custom rom. Stock rom is still fine for me.
Click to expand...
Click to collapse
Idk then sorry I have pure
Sent from my XT1575 using Tapatalk
Also tried Kingo root funny enough, but no go.
Edit: Wow, okay. Installing some kind of version of SuperSU does the trick apparently. It's in here:
http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792
I haven't downloaded any security patches since I followed the main guide and rooted my phone.
I now have seen the news regarding the security update and how many critical flaws there are so I would like to update.
How can I do so without losing root?
Losing root shouldn't really be a concern. All you need to do is flash SuperSU again afterwards, which takes about a minute.
https://play.google.com/apps/testing/eu.chainfire.flash
This is an app by Chainfire called Flashfire. It works perfectly for what you want. I have used it myself on a few occasions. Let me know how it worked for you.
Sent from my Nexus 6P using XDA-Developers mobile app
+1 FlashFire
If you are impatient and don't want to wait for the OTA zip, just download the factory image and flash the following files using flashfire.
boot.img
system.img
vendor.img
Remember to disable security before you flash or you will have an issue with the vendor.img.
Heisenberg said:
Losing root shouldn't really be a concern. All you need to do is flash SuperSU again afterwards, which takes about a minute.
Click to expand...
Click to collapse
Hey, so I'm rooted with stock ROM and EX kernel but received the April update, any info why I got it?
I thought if you're rooted you weren't supposed to get an OTA update.
Sent from my Nexus 6P using Tapatalk
Doodsz said:
Hey, so I'm rooted with stock ROM and EX kernel but received the April update, any info why I got it?
I thought if you're rooted you weren't supposed to get an OTA update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You'll still receive the OTA, you just can't flash it via the traditional method.
I remember using the FlashFire method a month ago. The update worked and I didn't lose root, but I lost TWRP in the process.
ZabiGarma said:
I remember using the FlashFire method a month ago. The update worked and I didn't lose root, but I lost TWRP in the process.
Click to expand...
Click to collapse
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Sent from my Nexus 6P using XDA-Developers mobile app
dratsablive said:
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Click to expand...
Click to collapse
I couldn't flash it with FlashFire. I had to reinstall it from PC, which ended up with TWRP asking for a password, meaning I had to end up wiping the phone, which was worse than doing the regular OTA update.
ZabiGarma said:
I couldn't flash it with FlashFire. I had to reinstall it from PC, which ended up with TWRP asking for a password, meaning I had to end up wiping the phone, which was worse than doing the regular OTA update.
Click to expand...
Click to collapse
The new version of twrp 3.0.2.0 has been fixed. At least for me it worked.
Nice, I haven't installed the latest TWRP. I'll give it a try.
What I don't recall, though, is if last time I lost the applications I installed by flashing them with TWRP (like viper4android) or which rely on root.
I always remove security before flashing updates. Only issue is setting up the Imprint and adding cards back to Android Pay.
dave2metz said:
https://play.google.com/apps/testing/eu.chainfire.flash
This is an app by Chainfire called Flashfire. It works perfectly for what you want. I have used it myself on a few occasions. Let me know how it worked for you.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Is FlashFire no longer available?
dratsablive said:
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
If you use FlashFire just deselect recovery from the list when you load the latest update.
Sent from my Nexus 6P using XDA-Developers mobile app
Flash stock recovery and then ADB sideload the update. Links can be found in general. Then when it's done reflash twrp and SuperSU. Pretty easy. I've done it.
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!
Hello all,
I am several versions behind on my P2XL simply because it is rooted and I have to it manually. Haven't had time to do it but I know I am missing out on several security updates that seem to be rather important so it is time to update. I would prefer not to wipe my phone; however, since j am so many versions behind maybe it's better to do so?
Curious am I able to just install the February update over my current October build or do I have to push each update to the device before moving to the next?
Please let me know, thanks so much
cwburns32 said:
Hello all,
I am several versions behind on my P2XL simply because it is rooted and I have to it manually. Haven't had time to do it but I know I am missing out on several security updates that seem to be rather important so it is time to update. I would prefer not to wipe my phone; however, since j am so many versions behind maybe it's better to do so?
Curious am I able to just install the February update over my current October build or do I have to push each update to the device before moving to the next?
Please let me know, thanks so much
Click to expand...
Click to collapse
You can just use the Feb update. You don't need to go thru all the updates to that point. And you don't have to wipe the device. Just run the flash all batch file in the factory image with the -w removed.
You will have to download the full ota from Google's page and flash it if you want to skip every incremental update.
Sent from my Pixel 2 XL using XDA Labs
And/or you can flash the February OTA via twrp if fastboot isn't your cup-o-tea. However, no matter what route you choose, you'll still have to install twrp and root again. Happy flashing :good:
jd1639 said:
You can just use the Feb update. You don't need to go thru all the updates to that point. And you don't have to wipe the device. Just run the flash all batch file in the factory image with the -w removed.
Click to expand...
Click to collapse
MrMeeseeks said:
You will have to download the full ota from Google's page and flash it if you want to skip every incremental update.
Click to expand...
Click to collapse
Badger50 said:
And/or you can flash the February OTA via twrp if fastboot isn't your cup-o-tea. However, no matter what route you choose, you'll still have to install twrp and root again. Happy flashing :good:
Click to expand...
Click to collapse
Thank you all!! Fastboot or TWRP work for me. Glad I don't need to wipe device.
Any issues with rooting on new Feb patch? Or same process with Magisk as it's been?
cwburns32 said:
Thank you all!! Fastboot or TWRP work for me. Glad I don't need to wipe device.
Any issues with rooting on new Feb patch? Or same process with Magisk as it's been?
Click to expand...
Click to collapse
Same process, no issues.
jd1639 said:
Same process, no issues.
Click to expand...
Click to collapse
What he said! :laugh:
jd1639 said:
Same process, no issues.
Click to expand...
Click to collapse
Badger50 said:
What he said! :laugh:
Click to expand...
Click to collapse
Sounds good!! Any one using Viper4Android on the new Feb build? If so, how is it working? Thanks!
cwburns32 said:
Sounds good!! Any one using Viper4Android on the new Feb build? If so, how is it working? Thanks!
Click to expand...
Click to collapse
The 3.3 version magisk module working fine for me :good:
Badger50 said:
The 3.3 version magisk module working fine for me :good:
Click to expand...
Click to collapse
Are you also using Dolby on top of Viper, I was for a while with great results but can't seem to find Dolby 9 as opposed to the 8.1 I was using previously.
Flashing via ADB without -w , I recall doing this previously but don't remember what I need to exactly in the commands so I don't have to wipe phone. Could someone please kindly advise?
cwburns32 said:
Are you also using Dolby on top of Viper, I was for a while with great results but can't seem to find Dolby 9 as opposed to the 8.1 I was using previously.
Flashing via ADB without -w , I recall doing this previously but don't remember what I need to exactly in the commands so I don't have to wipe phone. Could someone please kindly advise?
Click to expand...
Click to collapse
Yep, using Dolby as well. Here, you can use my copy :good: https://drive.google.com/file/d/1B5oSZ96oi7JC_IQnU1qiNPwQWPjr72aL/view?usp=drivesdk
As far as updating, make sure your platform-tools are up to date. Extract the February update, and place all those files in your platform-tools folder.
Then edit the flash-all.bat file, removing the -w, and leaving a space between the remaining words, and save the edit.
Put your phone in bootloader mode, plug it in to your pc, open a command prompt on your platform-tools folder, and type: fastboot flash-all
Let it do it's thing, then boot up to the OS to make sure it's all good.
Then fastboot into twrp, flash the twrp installer zip, then flash magisk zip, then your custom kernel(if used) Boot up, and there ya go
Badger50 said:
Yep, using Dolby as well. Here, you can use my copy :good: https://drive.google.com/file/d/1B5oSZ96oi7JC_IQnU1qiNPwQWPjr72aL/view?usp=drivesdk
As far as updating, make sure your platform-tools are up to date. Extract the February update, and place all those files in your platform-tools folder.
Then edit the flash-all.bat file, removing the -w, and leaving a space between the remaining words, and save the edit.
Put your phone in bootloader mode, plug it in to your pc, open a command prompt on your platform-tools folder, and type: fastboot flash-all
Let it do it's thing, then boot up to the OS to make sure it's all good.
Then fastboot into twrp, flash the twrp installer zip, then flash magisk zip, then your custom kernel(if used) Boot up, and there ya go
Click to expand...
Click to collapse
Lol my luck...
I just flashed your dolby version but it just fc's after showing the Dolby opening screen for a couple seconds.
Any other mods needed?
CyberpodS2 said:
Lol my luck...
I just flashed your dolby version but it just fc's after showing the Dolby opening screen for a couple seconds.
Any other mods needed?
Click to expand...
Click to collapse
Yeah, uninstall any other sound mods you have. Then flash the Dolby.zip in twrp, then install ViPER4Android FX version 3.3 magisk module, reboot, then install the AML module. Then you should be good :good: