Related
Hello,
I got my Google Pixel literally two days ago and I was looking around xda and other websites for root on this phone. And so far, I haven't seen anything simple. I saw that Chainfire has rooted the Pixel and Pixel XL but I read some comments saying that if you installed the OTA update, then it won't work And I unfortunately installed an OTA that was available.
It was just overall confusing to read considering this isn't my first Android phone or is this my first root.
So I was wondering if I can still root the phone I have that's running Android 7.1.
I got my phone a few days ago as well, made sure everything was entirely up to date, and then rooted two days ago without a problem. I started with the boot-to-root version and then I updated to SR5... no problems thus far!
Fastboot boot TWRP and flash the newest SuperSU in the TWRP thread. Should work fine if you want stock recovery. But, this is Google.. boot TWRP then flash the TWRP zip then flash SuperSU. Be happy. Don't take otas and update via fastboot and repeat above steps.
???? said:
I got my phone a few days ago as well, made sure everything was entirely up to date, and then rooted two days ago without a problem. I started with the boot-to-root version and then I updated to SR5... no problems thus far!
Click to expand...
Click to collapse
What's an SR5 and what's the boot-to-root method?
k.s.deviate said:
Fastboot boot TWRP and flash the newest SuperSU in the TWRP thread. Should work fine if you want stock recovery. But, this is Google.. boot TWRP then flash the TWRP zip then flash SuperSU. Be happy. Don't take otas and update via fastboot and repeat above steps.
Click to expand...
Click to collapse
So fastboot boot TWRP, then the TWRP zip and finally SuperSU?
binaryn00b said:
What's an SR5 and what's the boot-to-root method?
So fastboot boot TWRP, then the TWRP zip and finally SuperSU?
Click to expand...
Click to collapse
Yes, fastboot boot TWRP, once booted in, flash the TWRP zip (it flashes to both partitions) then flash the SuperSU zip. Reboot, profit.
k.s.deviate said:
Fastboot boot TWRP and flash the newest SuperSU in the TWRP thread. Should work fine if you want stock recovery. But, this is Google.. boot TWRP then flash the TWRP zip then flash SuperSU. Be happy. Don't take otas and update via fastboot and repeat above steps.
Click to expand...
Click to collapse
Is updating via fastboot same as nexus format?
Fastboot flash boot/system/cache(na in pixel) /recovery(?)/vendor
Asking cause there's so many new files inside the Ota zip folder.
queerquirks said:
Is updating via fastboot same as nexus format?
Fastboot flash boot/system/cache(na in pixel) /recovery(?)/vendor
Asking cause there's so many new files inside the Ota zip folder.
Click to expand...
Click to collapse
Here's a good guide: http://www.androidcentral.com/how-manually-upgrade-your-nexus
binaryn00b said:
What's an SR5 and what's the boot-to-root method?
Click to expand...
Click to collapse
If you see here there are different builds. SR3 (boot-to-root) does NOT use TWRP, so I used that and then I updated to SR5 here.
My Google Pixel will be here in a few days. I downloaded these files:
SR5-SuperSU-v2.78-SR5-20161130091551.zip
twrp-3.0.2-0-alpha2-fastboot-sailfish.img
(I also have twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip on hand in case I need it.)
Will this method work?
Copy SR5-SuperSU-v2.78-SR5-20161130091551.zip to the device
adb reboot bootloader
fastboot boot twrp-3.0.2-0-alpha2-fastboot-sailfish.img
From TWRP install the SR5 zip
I don't need TWRP for anything more than rooting (which I have always done on my Nexus devices), but I keep seeing instructions where a TWRP img is first booted, then a TWRP zip is installed. Is it necessary to install TWRP in order to root because of the new partition layout, or can I root by simply booting to TWRP?
CatThief said:
My Google Pixel will be here in a few days. I downloaded these files:
SR5-SuperSU-v2.78-SR5-20161130091551.zip
twrp-3.0.2-0-alpha2-fastboot-sailfish.img
(I also have twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip on hand in case I need it.)
Will this method work?
Copy SR5-SuperSU-v2.78-SR5-20161130091551.zip to the device
adb reboot bootloader
fastboot boot twrp-3.0.2-0-alpha2-fastboot-sailfish.img
From TWRP install the SR5 zip
I don't need TWRP for anything more than rooting (which I have always done on my Nexus devices), but I keep seeing instructions where a TWRP img is first booted, then a TWRP zip is installed. Is it necessary to install TWRP in order to root because of the new partition layout, or can I root by simply booting to TWRP?
Click to expand...
Click to collapse
You can just root by booting twrp. Don't have to flash it if you don't want to. Though it could be useful for flashing other zips and kernels.
Sent from my Pixel using Tapatalk
CatThief said:
My Google Pixel will be here in a few days. I downloaded these files:
SR5-SuperSU-v2.78-SR5-20161130091551.zip
twrp-3.0.2-0-alpha2-fastboot-sailfish.img
(I also have twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip on hand in case I need it.)
Will this method work?
Copy SR5-SuperSU-v2.78-SR5-20161130091551.zip to the device
adb reboot bootloader
fastboot boot twrp-3.0.2-0-alpha2-fastboot-sailfish.img
From TWRP install the SR5 zip
I don't need TWRP for anything more than rooting (which I have always done on my Nexus devices), but I keep seeing instructions where a TWRP img is first booted, then a TWRP zip is installed. Is it necessary to install TWRP in order to root because of the new partition layout, or can I root by simply booting to TWRP?
Click to expand...
Click to collapse
i just did this, exactly. one thing I didn't anticipate is TWRP asking me for a 'password' in order to decrypt the filesystem. I had to provide my PIN as I don't use a password. everything went fine!
poolemit said:
i just did this, exactly. one thing I didn't anticipate is TWRP asking me for a 'password' in order to decrypt the filesystem. I had to provide my PIN as I don't use a password. everything went fine!
Click to expand...
Click to collapse
Thank you for reminding me. I always keep screen lock disabled on my devices, so I assume I need to set up a PIN with the Pixel. I recall a bug in a prior version of TWRP for the Nexus 9 where there was a prompt for a password, but even after I set one up and tried again I couldn't get into recovery. It sounds like it actually works this time.
Thank you guys for all the help! I managed to successfully root my phone and install TWRP.
One thing I'm having trouble with right now is that in Titanium Backup, when I try to change the file directory, it says that I cannot access the '/' folder.
Any help?
Also, another small thing. I remember in the Pixel Launcher, instead of the date appearing next to the Google search icon, the weather would appear. I messed around with all the settings I could find, and I can't seem to change the date back to the weather. Is that something that can be changed in Nova Launcher or no? Because I'm gonna recreate the Pixel Launcher in Nova.
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Don't do it. 5.1.8 will be released end of next week and you will be doing this all over again. I was going to myself but I'm waiting until the next release until someone pushes full writeup and review
You can install it via the update manager. But yes, you are going to lose twrp and root, which is not a problem at all since it took me only like 5 minutes to get it all working again.
I followed this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
memocatcher said:
You can install it via the update manager. But yes, you are going to lose twrp and root, which is not a problem at all since it took me only like 5 minutes to get it all working again.
I followed this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Thanks
dgunn said:
Don't do it. 5.1.8 will be released end of next week and you will be doing this all over again. I was going to myself but I'm waiting until the next release until someone pushes full writeup and review
Click to expand...
Click to collapse
Lol... And after that there will be a new build in another week...
The more updates, the better. We won't complain, do we? I'm glad, we don't suffer for updates like SAMEsung-users do.
Manivannan9444 said:
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Click to expand...
Click to collapse
Updating via twrp and then (before reboot) re flashing twrp.zip and magisk will grant you to maintain twrp and root
Manivannan9444 said:
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Click to expand...
Click to collapse
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
sarthak kumar said:
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
Click to expand...
Click to collapse
if u update through the OS like updater app or anything, u will have to re-flash twrp using the fastboot method, if you already have twrp installed then just update via twrp with full zip, install twrp installer zip, and then magisk (i usually reboot back to recovery after i install twrp installer then flash magisk). Then you are done, u do not lose anything and do no wipe anything either
Bradl79 said:
if u update through the OS like updater app or anything, u will have to re-flash twrp using the fastboot method, if you already have twrp installed then just update via twrp with full zip, install twrp installer zip, and then magisk (i usually reboot back to recovery after i install twrp installer then flash magisk). Then you are done, u do not lose anything and do no wipe anything either
Click to expand...
Click to collapse
Should i have to change slot after twrp flash of full rom
The easiest way is to download and install the update through the settings app then BEFORE you reboot open Magisk, click install then install to second slot.
No flash or worrying
sarthak kumar said:
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
Click to expand...
Click to collapse
Download the ota.zip, reboot to TWRP, flash ota, flash TWRP.zip, reboot to OS, reboot to recovery again if you want magisk and install magisk zip. Done. No data loss or changing settings.
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.
Sorry, its been quite a while since ive rooted and im new to Magisk. Im currently on November .a1 update. I followed the below tutorial
If starting fresh from November (.A1.) Update
Install November update
Download latest Magisk Beta (17.3) and move it to the internal storage of the device
Reboot to bootloader
Download the .img version of TWRP for "crosshatch"
In the location of downloaded TWRP .img, open cmd and enter
Code:
fastboot boot twrp-3.2.3-1-crosshatch.img
Allow twrp to boot (this will take a minute or two)
Then go to install and install the Magisk zip
Reboot and find magisk manager and make sure it says you're rooted
Until there is an update to the patched_boot.imgs, dont follow the how to beyond this point. In fact I am hiding it for the time being.
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712#login
Click to expand...
Click to collapse
But I do not see the "MAGISKSU (topjohnwu)" at all. I feel like there's more to root than just installing Magisk from TWRP. I see an "Install" but am hesistant as I bricked my phone last time I tried this.
What am I missing?
JJT211 said:
Sorry, its been quite a while since ive rooted and im new to Magisk. Im currently on November .a1 update. I followed the below tutorial
But I do not see the "MAGISKSU (topjohnwu)" at all. I feel like there's more to root than just installing Magisk from TWRP. I see an "Install" but am hesistant as I bricked my phone last time I tried this.
What am I missing?
Click to expand...
Click to collapse
It is just flash the zip from TWRP. And based on that screenshot it looks like you are done. What happens when you try and do something that requires root?
TonikJDK said:
It is just flash the zip from TWRP. And based on that screenshot it looks like you are done. What happens when you try and do something that requires root?
Click to expand...
Click to collapse
I usually verify root by downloading root checker app. App says that I'm not rooted.
EDIT: Nevermind, I tried it again and now it says I'm rooted. Thanks!
So I have this TWRP backup that i restored through.
I install SUPERSU zip from TWRP, all the scripts run fine, no issues or interruptions.
However, once I boot up normally, go through the setup process of Android's first boot and install the Super User app, it does not detect root X(
I have tried flashing the latest BETA & stable SuperSU zips (2.82)
I have tried older SuperSU zips (2.79)
None of the above have worked for me,
I have a European HTC U11+
S-ON, Unlocked Bootloader, Build 1.24.400.3
Any help would be great
Found the FIX
So every guide i've tried for my u11+ has been leading me to a debacle.
However, after days of restoring and resetting and reflashing and backing up, I have finally got my phone to root properly
Turns out none of the latest or typical Supersu zips worked for me.
So I went to this thread : https://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Downloaded this supersu zip : https://devfiles.co/download/wJDOxFEm/SR3-SuperSU-v2.82-SR3-20170813133244.zip
DO NOT BOOT THE RECOVERY IN THE GIVEN LINK, just flash the supersu
I hope this helps out other people as well
usmantahir said:
So every guide i've tried for my u11+ has been leading me to a debacle.
However, after days of restoring and resetting and reflashing and backing up, I have finally got my phone to root properly
Turns out none of the latest or typical Supersu zips worked for me.
So I went to this thread : https://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Downloaded this supersu zip : https://devfiles.co/download/wJDOxFEm/SR3-SuperSU-v2.82-SR3-20170813133244.zip
DO NOT BOOT THE RECOVERY IN THE GIVEN LINK, just flash the supersu
I hope this helps out other people as well
Click to expand...
Click to collapse
Why you didn't just use magisk? It is so simple...
Because I'm facing another issue, whenever I go to recovery after i setup my phone through normal boot, the password works at twrp but when I try to boot up, the device decryption password turns up invalid and I lose access to everything. It's a vicious cycle ?
Maybe it's cz I flashed a different build onto my phone
(Originally: 1.24.401.12, flashed: 1.24.400.3)
usmantahir said:
Because I'm facing another issue, whenever I go to recovery after i setup my phone through normal boot, the password works at twrp but when I try to boot up, the device decryption password turns up invalid and I lose access to everything. It's a vicious cycle ?
Maybe it's cz I flashed a different build onto my phone
(Originally: 1.24.401.12, flashed: 1.24.400.3)
Click to expand...
Click to collapse
Try to flash 1.24.401.7 ruu via sdcard method and after that flash corresponding recovery. You can find it in recovery thread
skodann said:
Try to flash 1.24.401.7 ruu via sdcard method and after that flash corresponding recovery. You can find it in recovery thread
Click to expand...
Click to collapse
It won't flash.. shows some sort of incompatibility
Also, i tried flashing the system.img of 1.24.401.12, it still reads 1.24.401.3 when i boot up
usmantahir said:
It won't flash.. shows some sort of incompatibility
Also, i tried flashing the system.img of 1.24.401.12, it still reads 1.24.401.3 when i boot up
Click to expand...
Click to collapse
It wouldnt flash but it did successfully install the full RUU zip of 1.24.401.7 using the SDCard method
And later, I was able to take the OTA to the latest build 1.24.401.12