Hi, I rooted my a9 back in May right around when 6.0.1 came out. Long story short, my device just gave up the ghost after a nasty interaction between the screen and concrete, so now I have a new device being shipped tomorrow. I figured the first thing I'll do is let it run any updates / OTAs it might have to get it up to date then attempt to root again.
I've been looking around for the past several hours trying to determine what the correct rooting method might be now given Nougat's rollout, but I haven't come across anything truly definitive yet. If anyone could enlighten me on what I'll need to do now to root this new version I'd be very appreciative.
Thanks in advance guys!
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
txag2011 said:
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
Click to expand...
Click to collapse
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
JohnRogers23 said:
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
Click to expand...
Click to collapse
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
I'm about to start the process trying to root using the above methods.. I'll post again when I have results.
txag2011 said:
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
Click to expand...
Click to collapse
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
JohnRogers23 said:
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
Click to expand...
Click to collapse
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
txag2011 said:
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
Click to expand...
Click to collapse
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
JohnRogers23 said:
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
txag2011 said:
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
Click to expand...
Click to collapse
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
JohnRogers23 said:
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
Click to expand...
Click to collapse
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
txag2011 said:
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
Click to expand...
Click to collapse
I'm glad you got it working. Strange you had to flash phh's Su separately though. Anyway, glad I could help.
Well Working !
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Dr.Anshuman said:
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Click to expand...
Click to collapse
Thanks! I got it more or less and went with magisk. Couldn't pass up a chance to have root and still get OTAs and use android pay. I'm still monkeying around trying to figure out how to use it to get liveboot back up and running.
Related
EDIT: this is for Marshmallow only. For Nougat some adjustments are required and this way *does not work*!
It's only some days that I have finally my Moto Z on hands and have to say it's really a great piece of hardware for... geeks!
At first it seems nothing particular because of its really-close-to stock Android (it isn't for unexperienced users in my opinion... they haven't added neither a reboot option to Vanilla Android! :cyclops, but more I use it, more I go with modifications, more I like it: it's really well developed to be modified and customized and in this is great!
It's very hard to brick in my opinion, I really love the simple (to access...) and well working system for fastboot/recovery/bootloader etc... and in this it is even better than I expected...
Now I want to share some of my experiences of these days to (eventually) help new users...
My idea was to unlock it installing recovery, root, Xposed support, etc. leaving firmware as stock as possible (for now... ) and in the most "systemless" mode possible... Let's start!
First step was to unlock bootloader. No particular issues here (but Motorola web site that was down for a while when I need it for unlock code...! ). Only thing to note, command adb reboot fastboot often reboot to system instead. No problem, since access to fastboot by keys is very simple on Z.
Unlocking bootloader made a factory reset too, but this is common...
Flash TWRP: no problem at all. Only thing, if you are going to make the first backup without letting TWRP patching your system partition to have a full stock backup, prepare to flash it twice, since if you don't find the required setting after, at first system boot, the stock recovery will be rewritten (a common behaviour anyway...). This TWRP (3.0.2.0) is complete and well working in my opinion. Nothing to be surprised, since it's an official version...
Second step has been to disable encryption. Encryption introduces a bit "slowerness" that I didn't want and could be an issue in case of problems to be resolved... more, I don't need it.
Stock kernel doesn't permit to disable it and phone arrives already encrypted (all data and internal storage too).
So I flashed in TWRP the patch to disable forced encryption that you could find here in another thread and it works fine.
Please note that to decrypt phone you have to not only wipe data, BUT to format it, deleting ALL the contents of internal storage too. So... save them before!
Wanting (if possible...) a systemless modified system (ehm....), next step was to flash Magisk v.9 in TWRP and install Magisk Manager apk. All fine, no problem at all.
Then I tried to root using phh's SuperUser as hinted as best method to use with Magisk. I tried flashing both v.266 & v.266-2 (latest...), no errors during flashing, BUT no one has been able to get root...
So I went with SuperSU v.2.78 (not a particular one... the stock one! ) and it flashed with no issues and obtained root in perfect way (I'm not sure if in system or systemless way...)
Xposed: I installed "Material version installer" apk, since it's able to install both system and systemless versions of Xposed.
I tried both the available systemless versions (v.86), that this apk download and make them installed by TWRP automatically, but none apparently work. So I uninstalled them and I went with stock (system) one, that installs and works fine at first attempt. Modules as GravityBox works perfectly as expected.
I hope these experienced could be usefull for others. I'm here for eventual opinions/suggestions/Q&A... :fingers-crossed:
EDIT: please note that "unencrypt" and "Magisk" steps *are mandatory* to have SuperSU installed with no issues. At 99% in systemless mode.
EDIT: root this way is obtained in system mode.
almost identical to what i did
tried the prerooted rom but got some chinese headers so decided to drop it.
went back to stock and rooted and exposed it the same u did.
added the turbo z kernel though which gave me better battery life.
reiteravi said:
almost identical to what i did
tried the prerooted rom but got some chinese headers so decided to drop it.
went back to stock and rooted and exposed it the same u did.
added the turbo z kernel though which gave me better battery life.
Click to expand...
Click to collapse
This will be my next step I think... I want to test it a bit with stock kernel to have a starting point to compare with...
@mods: Probably this should be put as sticky, since of the lot of requests about root issues...
Can you share the link to disable encryption patch file.. the link in the other thread isn't working.
Manish54 said:
Can you share the link to disable encryption patch file.. the link in the other thread isn't working.
Click to expand...
Click to collapse
Here you are...
enetec said:
Here you are...
Click to expand...
Click to collapse
Thanks
Just to be clear... I've not tested first hand yet (I'm happily sticky with MM for now...), BUT it's my opinion that all above should work fine on Nougat too...
Updated OP to clarify that root has been obtained in system mode this way... (su located in /system/xbin...)
superuser doesn't work
enetec said:
It's only some days that I have finally my Moto Z on hands and have to say it's really a great piece of hardware for... geeks!
At first it seems nothing particular because of its really-close-to stock Android (it isn't for unexperienced users in my opinion... they haven't added neither a reboot option to Vanilla Android! :cyclops, but more I use it, more I go with modifications, more I like it: it's really well developed to be modified and customized and in this is great!
It's very hard to brick in my opinion, I really love the simple (to access...) and well working system for fastboot/recovery/bootloader etc... and in this it is even better than I expected...
Now I want to share some of my experiences of these days to (eventually) help new users...
My idea was to unlock it installing recovery, root, Xposed support, etc. leaving firmware as stock as possible (for now... ) and in the most "systemless" mode possible... Let's start!
First step was to unlock bootloader. No particular issues here (but Motorola web site that was down for a while when I need it for unlock code...! ). Only thing to note, command adb reboot fastboot often reboot to system instead. No problem, since access to fastboot by keys is very simple on Z.
Unlocking bootloader made a factory reset too, but this is common...
Flash TWRP: no problem at all. Only thing, if you are going to make the first backup without letting TWRP patching your system partition to have a full stock backup, prepare to flash it twice, since if you don't find the required setting after, at first system boot, the stock recovery will be rewritten (a common behaviour anyway...). This TWRP (3.0.2.0) is complete and well working in my opinion. Nothing to be surprised, since it's an official version...
Second step has been to disable encryption. Encryption introduces a bit "slowerness" that I didn't want and could be an issue in case of problems to be resolved... more, I don't need it.
Stock kernel doesn't permit to disable it and phone arrives already encrypted (all data and internal storage too).
So I flashed in TWRP the patch to disable forced encryption that you could find here in another thread and it works fine.
Please note that to decrypt phone you have to not only wipe data, BUT to format it, deleting ALL the contents of internal storage too. So... save them before!
Wanting (if possible...) a systemless modified system (ehm....), next step was to flash Magisk v.9 in TWRP and install Magisk Manager apk. All fine, no problem at all.
Then I tried to root using phh's SuperUser as hinted as best method to use with Magisk. I tried flashing both v.266 & v.266-2 (latest...), no errors during flashing, BUT no one has been able to get root...
So I went with SuperSU v.2.78 (not a particular one... the stock one! ) and it flashed with no issues and obtained root in perfect way (I'm not sure if in system or systemless way...)
Xposed: I installed "Material version installer" apk, since it's able to install both system and systemless versions of Xposed.
I tried both the available systemless versions (v.86), that this apk download and make them installed by TWRP automatically, but none apparently work. So I uninstalled them and I went with stock (system) one, that installs and works fine at first attempt. Modules as GravityBox works perfectly as expected.
I hope these experienced could be usefull for others. I'm here for eventual opinions/suggestions/Q&A... :fingers-crossed:
EDIT: please note that "unencrypt" and "Magisk" steps *are mandatory* to have SuperSU installed with no issues. At 99% in systemless mode.
EDIT: root this way is obtained in system mode.
Click to expand...
Click to collapse
thanks for sharing.
for me superuser doesn't work; the phone doen't boot.
[email protected] said:
thanks for sharing.
for me superuser doesn't work; the phone doen't boot.
Click to expand...
Click to collapse
There could be only some reasons:
- you are ready on Nougat (this is tested with MM)
or
- you have missed one of the mandatory steps (read Magisk installation...)
or
- you haven't used the right SuperSU version. v. 2.78 SuperSU-v2.78-201609011115.zip is the tested one.
Please doublecheck.
enetec said:
There could be only some reasons:
- you are ready on Nougat (this is tested with MM)
or
- you have missed one of the mandatory steps (read Magisk installation...)
or
- you haven't used the right SuperSU version. v. 2.78 SuperSU-v2.78-201609011115.zip is the tested one.
Please doublecheck.
Click to expand...
Click to collapse
i'm on Nougat already.
[email protected] said:
i'm on Nougat already.
Click to expand...
Click to collapse
In this case, try to install phh's SuperUser v.259 instead of SuperSU v.2.78 and then install phh's SuperUser manager from Play Store.
I've not tested first hand but many are reporting this should work (and, it seems, not newer version too... only v.259 )
Please remember that this is going to patch your boot.img instead of system.img, so have a complete backup just in case... :fingers-crossed:
Here's a link to the Phh superuser r259 https://superuser.phh.me
Worked fine for me on Nougat :good:
enetec said:
In this case, try to install phh's SuperUser v.259 instead of SuperSU v.2.78 and then install phh's SuperUser manager from Play Store.
I've not tested first hand but many are reporting this should work (and, it seems, not newer version too... only v.259 )
Please remember that this is going to patch your boot.img instead of system.img, so have a complete backup just in case... :fingers-crossed:
Click to expand...
Click to collapse
My MOTOZ rooted now! thanks!
---------- Post added at 15:37 ---------- Previous post was at 15:36 ----------
supacrazyguy42 said:
Here's a link to the Phh superuser r259 https://superuser.phh.me
Worked fine for me on Nougat :good:
Click to expand...
Click to collapse
My MOTOZ rooted now! thanks!
i'm trying to install xposed
[email protected] said:
My MOTOZ rooted now! thanks!
---------- Post added at 15:37 ---------- Previous post was at 15:36 ----------
My MOTOZ rooted now! thanks!
i'm trying to install xposed
Click to expand...
Click to collapse
Great! There's no Xposed ready for Nougat just yet though.
Is there a method for locked bootloader?
Hey there!
I've unlocked my bootloader but couldn't find the way to install the TWRP.
How can I do that? :laugh:
Ah, I'm on 7.0 already!
mrlipz said:
Hey there!
I've unlocked my bootloader but couldn't find the way to install the TWRP.
How can I do that? :laugh:
Ah, I'm on 7.0 already!
Click to expand...
Click to collapse
You can flash it with fastboot.
fastboot flash recovery XXXXX.img
After flash, not reboot your phone first reboot to recovery
MyDarkThrone said:
You can flash it with fastboot.
fastboot flash recovery XXXXX.img
After flash, not reboot your phone first reboot to recovery
Click to expand...
Click to collapse
...*and* enable write modifications in /system.
Otherwise at first system boot TWRP will be overwritten by stock recovery again...
Sorry if this is in the wrong place, I suppose this is discussion.
Does anyone know a way to hide root from apps like Snapchat? None of the old methods seem to work, presumably because root works differently for this phone/Marshmallow, unless I'm making that up.
make sure you login to Snapchat before you root.
hugeguy said:
make sure you login to Snapchat before you root.
Click to expand...
Click to collapse
I tried unrooting, but it still didn't let me log in. :L No better option than that?
Darkscan said:
I tried unrooting, but it still didn't let me log in. :L No better option than that?
Click to expand...
Click to collapse
nope.. I had to reinstall the Rom and Login and then root the phone. After that you can take a backup of Snapchat with data using titanium pro
I think you can use suhide but i don't think it support nougat yet
Sent from my Pixel using Tapatalk
Have not tried it but there are some mods to make suhide work.
https://forum.xda-developers.com/pixel-xl/how-to/suhide-real-pixel-t3520001/page36
TonikJDK said:
Have not tried it but there are some mods to make suhide work.
https://forum.xda-developers.com/pixel-xl/how-to/suhide-real-pixel-t3520001/page36
Click to expand...
Click to collapse
Any chance there's a condensed version somewhere that doesn't make me go through 36 pages to find out what everyone's referencing?
See this is what I do. In twrp I click on the reboot tab then click on b I reset it will load in the b partition. I go to format advance options reset everything except your storage. Install ROM reinstall twrp reboot let screen load do your setup reboot to recovery make sure you are on partition b in reboot section go back install su zip. Reboot. Now restart phone to recovery click on reboot then hit partition a should lisd up on A partition dirty flash your rom.
Now partition A is stock no root. And partition B is rooted with su and I believe what changes you do on the rooted partition changes the non rooted partition since they share the same data. One is root one is not only down side is you need to restart to twrp to change partitions.
To me this us better the magisk. And any other options
Since magisk works but will fail at anytime and may take a couple restarts to get back up and running
Sorry about grammer hope you understand what I'm sayong
cgrimm9 said:
See this is what I do. In twrp I click on the reboot tab then click on b I reset it will load in the b partition. I go to format advance options reset everything except your storage. Install ROM reinstall twrp reboot let screen load do your setup reboot to recovery make sure you are on partition b in reboot section go back install su zip. Reboot. Now restart phone to recovery click on reboot then hit partition a should lisd up on A partition dirty flash your rom.
Now partition A is stock no root. And partition B is rooted with su and I believe what changes you do on the rooted partition changes the non rooted partition since they share the same data. One is root one is not only down side is you need to restart to twrp to change partitions.
To me this us better the magisk. And any other options
Since magisk works but will fail at anytime and may take a couple restarts to get back up and running
Sorry about grammer hope you understand what I'm sayong
Click to expand...
Click to collapse
I think I know what you're saying, but I'm not 100% sure and also don't know enough about how partitions work to want to embark on that endeavor.
Darkscan said:
I think I know what you're saying, but I'm not 100% sure and also don't know enough about how partitions work to want to embark on that endeavor.
Click to expand...
Click to collapse
Yeah same boat here.. would love to venture out and learn how both partitions work.. would love to do what that user described as I know it is doable with having two partitions... but on another note, I saw a thread to users who were softbricking their device by misusing the reboot to different partition options.. so i have decided to stay away from this until a more compatible TWRP can evolve and it's not tax season
Experimental magisk works fine to hide root. There is a thread.
Sent from my Pixel using Tapatalk
I ended up redoing my phone for the latest update. Decided to stay stock I did install TWRP then decided to run magisk it's not full root but does what I need.here is how I installed it.
1) Dirty or clean flash
2) Flash TWRP
3) Boot to System
4) Reboot to TWRP
5) Flash ElementalX kernel
6) Flash Magisk 11.6
7) Flash TWRP
8) Boot to System
9) reboot system again
10) open up magisk manager you should have magisk root
11) go to settings Enable Magisk Hide enable BusyBox enable systemless hosts
12) reboot phone open magisk manager you should now have magisk root and safety net green Android pay will work and so will apps like Snapchat pokemon go that direction modified systems.
Does magisk root allow root file management and/or Ad Away?
Hello, I'm still a noob trying to learn, so far with help of this forum I've learned to unlock and root my first android phone, now I'm trying to learn how to properly keep my device updated!
Can someone please give a little rundown to what are the correct steps to update OTA on a rooted twrp device?
I've been browsing the forums a lot but I seem to find a lot of different approaches, or too vague instructions.
It would be greatly appreciated if someone could help me out, step by step, and explain the steps with the commands I need to put in, if there are any.
Thank you
download the ota from here
place it on your phone
go to update on you phone then hit the cog and hit local update
let it up date
reboot to boot loader
fastboot twrp img again
then flash the installer
reboot recovery
then it will boot back in to recovery again
flash root
job done
Hello,
To save you having to fastboot boot TWRP, do the following:
Save the following files to your SDCard:
OTA.zip
Magisk.zip
TWRP.zip
Boot into TWRP
Flash OTA.zip first, then TWRP.zip straight after, then Magisk.zip straight after that, reboot.
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
Sorry yes, put the installer zip on the sdcard
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
i just download and install the OTA through system updates. Then boot to Trwp recovery and flash magisk . Profit
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide
to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You can flash the installer zip for TWRP through TWRP itself.
Doesn't installing OTA through system settings wipe TWRP? That's why I perform all my updates from TWRP directly.
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You have to do twrp/root again after updates. Unlock sticks, but twrp and root don't.
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Ajaykumar21066 said:
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Click to expand...
Click to collapse
It prob doesn't overwrite until u reboot so twrp may not have been overwritten on that partition yet, so would make sense, I need to try it out sometime
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Swatto is correct. The risk when using twrp is that you must reboot to recovery immediately after flashing the twrp installer zip, or you will boot to the old slot and things will be broken. Rebooting to recovery gets you onto the active, updated slot.
When you reboot to recovery and flash an OTA, you are flashing it to the other slot. The current slot is untouched, while the new active one is completely stock. The twrp installer zip flashes twrp to both slots.
This is the procedure to follow if you want to update via twrp. Personally, I prefer taking the OTA and reinstalling via fastboot just to make sure everything is clean.
lollyjay said:
I have personally tested the following with TWRP already installed and twrp-installer-enchilada-3.2.1-0.zip on your phone:
Download full (not incremental) OOS ROM to your phone and check MD5
Reboot to your installed TWRP
Install the OOS ROM
Do not reboot instead stay in TWRP
Install twrp-installer-enchilada-3.2.1-0.zip
Reboot Recovery
Wipe cache
Reboot System
Click to expand...
Click to collapse
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Thank you
DampDeceiver said:
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Click to expand...
Click to collapse
I have not tried that method as I want twrp, but that is the recommended approach.
I know things have changed with twrp, but it's not that hard once you get used to it. You just have to remember that your phone will switch active slots every time it gets an update or you flash an ota (for example, to go back to stock), so twrp, etc, have to be installed on the other slot before you boot to it. Once you get comfortable with that idea, the rest of it is pretty easy.
Well, I am glad to read this post. Its always interesting how things can be slightly different in every phone manufacturer's setup.
After my lady Huawei device (Honor 6x), I did not want to have to deal with their style of... Control over their devices.
And things seem much easier here, while also being a little confusing right now. I don't fully get the slot a/b stuff yet but it sounds like it's a system to ensure stability on the phone in cases where the newest update could install incorrectly the alternative slot has a backup to ensure the device will function.
Sorta sounds like the dual bios setup on some motherboards. It's good!
Right, so to summarise to ensure I got it right:
1) Downloaded large (1gb+) ota zip from one of these threads, official twrp recovery installing zip, new version of magisk recovery installing zip
2) in recovery install all 3 of those zips in that listed order
3) reboot to recovery again to ensure twrp is still installed
4) profit
Which twrp thread should I take the zip from? There are a few different threads. I shouldn't care about the fastboot version when I already have twrp installed, right?
Either way, it can be much easier than what I had to do on Huawei phones. (currently the easiest phone I used for customisation like this was Nexus 4, but gladly OP6 is getting pretty close to that same level).
Sent from my OnePlus 6 using XDA Labs
You're best off downloading from the official twrp site. If you already have it installed, no need to use the fastboot boot method. You should to reboot to recovery in between flashing twrp and magisk to be sure magisk gets installed on the active slot.
Swatto86 said:
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Click to expand...
Click to collapse
Question, more of a scenario really. So if I'm on slot A and have TWRP and Magisk installed, would it be alright to just do a local update and reboot, giving me a perfectly clean install in slot B? Does it work that way? Thanks!
I'm actually using a 6t, but worst case scenario I just use the MSM Download tool, still I wanna get the hang of these confusing A/B devices.
Hi! I've rooted a few devices in the past, but those devices were long past their software support period. The OP6 should be still supported for at least one more year so I'm not sure if rooting is worth it if it means I lose software updates. Am I going to receive updates if I root and install magisk?
Yes.. You'll receive updates. You'll have to use full rom zip to update and you'll also lose twrp and root.
Download full update zip (1gb+)
Boot to twrp
Flash rom.zip
Flash twrp
Reboot to twrp
Flash magisk
And also: please use search, this has been answered before a few times.
whizeguy said:
Yes.. You'll receive updates. You'll have to use full rom zip to update and you'll also lose twrp and root.
Download full update zip (1gb+)
Boot to twrp
Flash rom.zip
Flash twrp
Reboot to twrp
Flash magisk
And also: please use search, this has been answered before a few times.
Click to expand...
Click to collapse
I'm rooted and I take the ota updates and never lose twrp or root. This is also old news of how to do this.
So how you do it instead?
mixlex said:
I'm rooted and I take the ota updates and never lose twrp or root. This is also old news of how to do this.
Click to expand...
Click to collapse
So, you're saying that recovery and boot partition got separated from ROM?
Mord0rr said:
So how you do it instead?
Click to expand...
Click to collapse
After ota downloads and installs, do not reboot, back out and go to magisk. There is a module called twrp a/b retention. You run it, don't reboot yet. Open magisk up again, hit install magisk, you will get an option to install to inactive slot after an ota. Do so and then you can reboot and profit. I've been doing this since way back. It's like forgotten knowledge I guess. I just did it with ob16.
mixlex said:
After ota downloads and installs, do not reboot, back out and go to magisk. There is a module called twrp a/b retention. You run it, don't reboot yet. Open magisk up again, hit install magisk, you will get an option to install to inactive slot after an ota. Do so and then you can reboot and profit. I've been doing this since way back. It's like forgotten knowledge I guess. I just did it with ob16.
Click to expand...
Click to collapse
Well duh..
So, with your install type you still download full rom over OTA (yes... It does that).
Twrp retention is needed because ROM install sets stock boot/recovery. Same answer to root. (p.s I have flashed this way aswell, lots of times, the other way is more idiot proof since people seems to want to click reboot now anyhow).
Also, the way I wrote isn't an old way really, it's A way rather
,
whizeguy said:
Well duh..
So, with your install type you still download full rom over OTA (yes... It does that).
Twrp retention is needed because ROM install sets stock boot/recovery. Same answer to root. (p.s I have flashed this way aswell, lots of times, the other way is more idiot proof since people seems to want to click reboot now anyhow).
Also, the way I wrote isn't an old way really, it's A way rather
Click to expand...
Click to collapse
Well you asked didn't you, duh. Seems like nobody can say anything here without somebody being a smart-ass
mixlex said:
,
Well you asked didn't you, duh. Seems like nobody can say anything here without somebody being a smart-ass
Click to expand...
Click to collapse
Well the way you wrote it before could confuse new people, they would just install ota and think it's all good.. Reboot and boom... No root or custom recovery. That's the reason I asked.
whizeguy said:
Well the way you wrote it before could confuse new people, they would just install ota and think it's all good.. Reboot and boom... No root or custom recovery. That's the reason I asked.
Click to expand...
Click to collapse
Point taken
I'm at my wit's end here. I know I'm probably missing some critical step, but I haven't been able to install any OTAs since installing TWRP and Magisk. Fortunately, I was able to update to the latest TWRP before trying (the one that has working decryption) and backup Boot, the two Systems, and Data. I cannot stress enough how important this is!.
The OTA installer detects the device is rooted (or unlocked, if magisk isn't installed) and downloads the OTA. It then asks to install (which is does while booted to system, presumably to the side (A or B) that isn't updated), and asks to reboot. After reboot, the system fails to boot, then goes to the original OnePlus recovery (with the Chinese characters).
I seem to remember reading somewhere that I needed to shut the phone down instead of rebooting, but that doesn't seem to help. I want to know the correct procedure for updating, but I also want to better understand what is actually going on. I'm guessing the boot image on the other side gets overwritten by the OTA, which then flips you to that side, but I don't understand why it doesn't boot. Non-patched boot.img, I suppose?
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
RocketGeeezer said:
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
Click to expand...
Click to collapse
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Flapjack said:
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Click to expand...
Click to collapse
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
whatthekj said:
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
Click to expand...
Click to collapse
Thanks! Trying now!
Flapjack said:
Thanks! Trying now!
Click to expand...
Click to collapse
No problem. Let me know if you have any issues.
Well, it's different (booting to TWRP instead of stock recovery), but it still didn't work. It booted through the "warning...unlocked bootloader" screen twice, then went to TWRP, though without encryption. I was able to switch the boot slot and get into system again (just as it was before the flash), but I don't know what I did wrong.
The only thing different I did was use the tools under EX Kernel Manager to flash the TWRP retention script, as I couldn't find where Magisk could do that.
**EDIT**
Now when I try to do the OTA, I get a "System update installation failed".
I cleared the cache and tried it again, this time doing the retention zip from inside Magisk > Modules > Add (+ sign) option, which is what I'm assuming you did.
It did the exact same thing. After step four, I rebooted, and it went straight into recovery (without the option to decrypt).
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
RocketGeeezer said:
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
Click to expand...
Click to collapse
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Flapjack said:
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Click to expand...
Click to collapse
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Maybe do some research first. There is also a unbrick thread
RocketGeeezer said:
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Click to expand...
Click to collapse
I've tried that... several times. I wish it worked.
Maybe do some research first. There is also a unbrick thread
Click to expand...
Click to collapse
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Flapjack said:
I've tried that... several times. I wish it worked.
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Click to expand...
Click to collapse
Okay I updated just like we do with our pixels when we flash a custom ROM. TW RP flash your ota.zip,TWRP zip, reboot to recovery that will switch slots , because your update just flashed to the other slot, then flash magisk then reboot. That's how I did this last update. Oh and it's got to be the full ota from what I read anyways.