Hello
I have problems rooting Google Pixel running Android 7.1.2. I have no experience with this sort of thing, hope someone can see what I'm missing.
I have successfully unlocked the bootloader and flashed TWRP. SuperSU installation (used SuperSU-v2.79-201612051815.zip) did not produce any errors, however, it did not root the phone as expected. Re-reading the instructions [1], I realized I missed the step where I was supposed to remove fstab.sailfish file. So I renamed that file and re-installed SuperSU. Again, no errors were reported. I rebooted the phone (it rebooted just once - the instructions say it should be a couple of times) but root is still missing.
I'm not sure what to do at this point and I'm a little afraid to experiment on my own. Any guidance would be appreciated.
Thank you!
Marek
[1] androidexplained.com/pixel-root/
Google SuperSU v2.79 SR3 from January of this year.
roirraW "edor" ehT said:
Google SuperSU v2.79 SR3 from January of this year.
Click to expand...
Click to collapse
You are right sir. SR3 rooted my device successfully. Thank you.
Related
So I have been struggling the past few hours trying to get the Systemless root to work. I've followed all of the guides on this and the Magisk forum and yet the SafetyNet fails. Here are the steps I have taken:
Downloaded H830 10i ZIP
Downloaded Magisk v7 ZIP
Downloaded phh superuser magisk r259 ZIP
Boot into TWRP
Format Data
Flash the three ZIP files one at a time in the order mentioned
Flash no-veirfy
Reboot System
Step through setup page
Install Magisk Manager apk
Install phh SuperUser apk
Install SafetyNetHelper
The end result of all of that is a failed SafetyNet. Am I missing something? I would really appreciate any help. Thanks
SafetyNet has been undergoing an impressive number of revisions over the past few weeks. Most recently, this past weekend, it effectively shut out the majority of rooted users. There are reports of it shutting out folks purely for having an unlocked bootloader, particularly with the Nexus 6P.
Specifically for our G5, here's my history:
Magisk v7 and earlier was working well up until a few weeks ago. Safetynet was updated to detect Magisk in general. End of that chapter.
Chainfire and phhusson, the 2 main root leaders in Android, each came up with their own workarounds to evade SafetyNet. Chainfire came up with suhide, to be flashed after his supersu zip, and phhusson released his own version of phh root which also hid root from SafetyNet.
These worked for about a week until SafetyNet adapted. suhide was then updated with a manual script to run which evaded it again for several more days. This was working for me on Sunday morning. And then it didn't anymore. There were many variations people then advertised (using different root switch apps, etc), but none worked for me.
Magisk v8 was just released, which includes a setting to hide Magisk and root from SafetyNet. However, this does not work to fully evade Safetynet, and thus Android Pay won't start. It may be that SafetyNet is now looking at other things, such as unlocked bootloader status, and Magisk's presence is irrelevant.
Specifically, while working with these, I accidentally reset my G5 to near stock conditions (no root, encrypted data partition), except for the TWRP recovery and unlocked bootloader. Safetynet checker apps FAILED on this near pristine stock phone. This is disconcerting.
In short, there's no way I've found to get a SafetyNet pass since this past weekend. You could try returning completely to stock and relocking the bootloader, which will also probably wipe all your data, to test this theory, but not worth it in my book.
seconding what waylo said. i was trying all day to get safetynet to pass but i flashed the stock rom, did a factory reset, and still couldn't get safetynet to pass (all i had was unlocked bootloader + TWRP)
i think we just have to wait until we get a custom kernel with the boot verify checker that safetynet uses patched
Thanks for your help a few months ago. Given the time for Magisk to mature I was wondering if Magisk on the H830 is now possible. From reading throughout this forum, some users have had success but no one has an official guide. I just got a new LG G5 (gps issue) and I finally unlocked the bootloader and installed TWRP following the Noob Friendly Guide. Along the way I had to enter in the following code to keep my device from TWRP boot looping:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Once I got the 20a software version up and running I went ahead and flashed Magisk 12.0, went into the Magisk Manager Settings, turned on Busybox/Magisk Hide/Systemless Host, and performed a SafetyNet Check. The end result is a failed CTS Profile Mismatch. Did I miss something or did Google patch SafetyNet again?
SomeguynamedBentley said:
Thanks for your help a few months ago. Given the time for Magisk to mature I was wondering if Magisk on the H830 is now possible. From reading throughout this forum, some users have had success but no one has an official guide. I just got a new LG G5 (gps issue) and I finally unlocked the bootloader and installed TWRP following the Noob Friendly Guide. Along the way I had to enter in the following code to keep my device from TWRP boot looping:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Once I got the 20a software version up and running I went ahead and flashed Magisk 12.0, went into the Magisk Manager Settings, turned on Busybox/Magisk Hide/Systemless Host, and performed a SafetyNet Check. The end result is a failed CTS Profile Mismatch. Did I miss something or did Google patch SafetyNet again?
Click to expand...
Click to collapse
You need to install the latest v13 beta. It's on the magisk threads. Uninstall v12 with the magisk uninstaller and immediately install v13.
waylo said:
You need to install the latest v13 beta. It's on the magisk threads. Uninstall v12 with the magisk uninstaller and immediately install v13.
Click to expand...
Click to collapse
Awesome! Got it. Hopefully the learning curve from here on out as Google rolls out patches is not as steep so I can keep up!
A word to those reading this thread: you need to reboot after turning on Magisk Hide and Systemless Host in settings (as of 6/19/17).
(Not sure if it is better to make a new thread or ask in the SuperSU thread...)
Hey all. I had previously been running the 7.1 OTA build with SuperSU installed. It seemed fine and I had done OTA updates with it installed with little issue. This was pre-2.78 SR3 builds of SuperSU, so I was using the boot-to-root. One day, I inexplicably noticed that root was gone. App too. I was very confused because to the best of my knowledge no OTA updates or security updates happened since I last rooted.
With that, I decided to sideload update to NMF26Q, which apparently was released about 12 hours earlier, and install TWRP since it was needed for newer SuperSU. TWRP installed fine and worked, but SuperSU did not seem to work. In fact, every time I attempted to flash SuperSU 2.78 SR5, I noticed it would remove the SuperSU app if it was installed via the Play Store. Finally, I noticed that it was installing in System mode.
I attempted to override this by running `echo "SYSTEMLESS=true" >> /data/.supersu`, but nothing I did worked. It did the same exact thing. Looking through the shell script, I'm entirely unsure how it is possible that my override did not work. I also reflashed the stock boot image to both slots and then reinstalled TWRP. This had no effect on installing SuperSU.
I try to do due diligence before turning to the internet for help, but I don't have any clue what's going on here. Maybe it is best if i reflash the entire stock ROM, but I'd love to avoid that if possible, as everything else seems to work great, and I have no idea why this in particular would be an issue.
Use alpha 2 of twrp and ask will be well
Yep, that worked great. Cheers.
http://forum.xda-developers.com/showpost.php?p=69626115&postcount=2
I have the Droid Turbo xt1254 and have been running CrDroid. Today I tried to flash SuperSU 2.76 so I could access the app but I'm getting stuck with a bootloop at the Motorola Disclaimer page. I tried to enter TWRP through recovery and it gives me the splash screen and then goes into a Motorola Disclaimer bootloop. I'm pretty stuck here, as I can't event get into TWRP to reformat my phone. Any help would be greatly appreciated.
mbguitarman said:
I have the Droid Turbo xt1254 and have been running CrDroid. Today I tried to flash SuperSU 2.76 so I could access the app but I'm getting stuck with a bootloop at the Motorola Disclaimer page. I tried to enter TWRP through recovery and it gives me the splash screen and then goes into a Motorola Disclaimer bootloop. I'm pretty stuck here, as I can't event get into TWRP to reformat my phone. Any help would be greatly appreciated.
Click to expand...
Click to collapse
You can get into TWRP through ADB fastboot commands.
When you do so, you would want to flash the NEWEST SuperSu that is compatible with Nougat ROMs. 2.76 is OLD. That incompatible older version of SuperSU is most likely the cause of your problem...
ChazzMatt said:
You can get into TWRP through ADB fastboot commands.
When you do so, you would want to flash the NEWEST SuperSu that is compatible with Nougat ROMs. 2.76 is OLD. That incompatible older version of SuperSU is most likely the cause of your problem...
Click to expand...
Click to collapse
Not quite correct, the newer versions, 2.79 or 2.79 SR1, cause the same issue too.
mangojain said:
Not quite correct, the newer versions, 2.79 or 2.79 SR1, cause the same issue too.
Click to expand...
Click to collapse
Those are old also. Nougat is now on 7.1.2.
When I wrote that and even today, SuperSU-v2.79-SR3 is the newest. But I didn't want to list a specific version because 2 or 3 months from now it also maybe outdated.
Flash the newest SuperSu. That's what I said.
Is that so hard?
Why do you keep trying to flash older ones? Are you trying each one up the steps or something? Just jump to the newest and stop complaining.
Right now this is the newest...
SR3-SuperSU-v2.79-SR3-20170114223742.zip
But 2 or 3 months from now don't complain if it doesn't work. Go find the NEWEST.
Thanks a lot @ChazzMatt this really helped me to recover my phone, just downloaded the latest SuperSU (2.82 at this moment) flashed it and load the full system again.
Cj Marquez said:
Thanks a lot @ChazzMatt this really helped me to recover my phone, just downloaded the latest SuperSU (2.82 at this moment) flashed it and load the full system again.
Click to expand...
Click to collapse
You're welcome!
Super SuperSu 2.82 SR5 I think is the latest. But of course that will change again.
My Pixel's bootloader is unlocked, running Android v8.1.0. I am flashing SuperSu v2.82. zip from TWRP 3.2.1.0 booted over fastboot. The flashing succeeds. However, when I boot into Android, there's no SuperSU installed. If I install the same from Play Store, it does not detect root. Moreover, the installed SuperSU disappears in the next reboot. I have repeated the re-flash and re-boot cycle several times. The same takes place every time. Can anyone explain what's going on?
I need to use Magisk until SuperSU get updated.
Official SuperSU hasn't been updated since I think May, and doesn't seem likely SuperSU will ever be updated to work with 8.1. @Chainfire announced he is done making his unofficial builds such as 2.82 SR5, which worked on 8.0 but doesn't work on 8.1.
I'm using Magisk 14.2 since @Chainfire 's FlashFire app works with that version, but if you don't need FlashFire, just use the latest Magisk.
roirraW "edor" ehT said:
...@Chainfire announced he is done making his unofficial builds such as 2.82 SR5, which worked on 8.0 but doesn't work on 8.1.
Click to expand...
Click to collapse
Are you sure SuperSu v2.82-SR5 works with Android 8.0 on Pixel? I downgraded to 8.0 and tried flashing SuperSu v2.82-SR5 from TWRP v3.2.1. It fails to flash in my case.
Holmes.Sherlock said:
Are you sure SuperSu v2.82-SR5 works with Android 8.0 on Pixel? I downgraded to 8.0 and tried flashing SuperSu v2.82-SR5 from TWRP v3.2.1. It fails to flash in my case.
Click to expand...
Click to collapse
Yes, I'm sure. I never touched Magisk until 8.1 Final came out. I even tried to use the same SuperSU with 8.1 but obviously, it doesn't work. When you downgraded did you let it wipe your data or did you start completely fresh? When downgrading you need to start completely fresh, so let it wipe all your data after you backup all your stuff.
Is your download of SuperSU v2.82 SR5 corrupt?
---------- Post added at 02:19 PM ---------- Previous post was at 01:31 PM ----------
@Holmes.Sherlock I didn't notice for some reason, but question threads like this go in the Q&A section. Please report this to a moderator using the button in the lower left of your first post in this thread that, that's an exclamation point in a triangle /!\ and just ask them to please move the thread to Q&A.
Thank you.
roirraW "edor" ehT said:
Yes, I'm sure.
Click to expand...
Click to collapse
You are right. Something somewhere was screwed up. I did it afresh and now it works.
Out of curiosity, is it mentioned anywhere that SuperSU SR5 is not supported for Android v8.1.0? I wasted the whole day yesterday in trying it out. And how are these SR versions different from stable ones? Just that these support devices with A/B boot partitions?
Holmes.Sherlock said:
You are right. Something somewhere was screwed up. I did it afresh and now it works.
Out of curiosity, is it mentioned anywhere that SuperSU SR5 is not supported for Android v8.1.0? I wasted the whole day yesterday in trying it out. And how are these SR versions different from stable ones? Just that these support devices with A/B boot partitions?
Click to expand...
Click to collapse
Did you report this thread to have a moderator move it to Q&A?
Cool, glad it works. Yes, in the Updates thread in the Guide section, and a few other random threads it's been mentioned. Possibly also in the SuperSU thread, I don't recall. In all cases only reported by us users after finding it out for ourselves.
The SR versions are ones that @Chainfire developed. The "stable" versions are at least officially by the company he sold SuperSU to. @Chainfire announced the other month that he was done with any developing of SuperSU so it's all up to the company he sold it to, now, and they've been all quiet regarding any development since May 28, 2017, when v2.82 was released.
A link to the company's website/forum is in the Play Store entry for SuperSU, but I don't see any recent word there other than from users, and there are lots of suspicious posts about rooting phones that I wouldn't trust enough to look in the eyes. Once Chainfire stopped developing it, there's just no way to trust anything that comes out of that company, anyway.
v2.82 supported the Pixel with A/B partitions as well, just only works on Nougat, not on Oreo 8.0 which came out several months after v2.82 came out.
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
rcbjr2 said:
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
Click to expand...
Click to collapse
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Qnorsten said:
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Click to expand...
Click to collapse
I seem to have the Canary Update channel set already (I thought it was set to Stable, but I guess not). Doesn't that mean I already have the latest Canary build? Manager shows that latest is 6951d926 (21402) (16) but Installed shows 658d74e0 (21402) (16). I assume this means they are different? Install doesn't seem to update it. Maybe grab the latest APK from Github? Thanks.
Later: Can I install it on my phone by download Magisk v21.4 zip and changing extension to APK and installing it? I thought I read everything is now in the zip/apk? Thanks.
FINAL UPDATE: OK, I downloaded the latest MagiskManager, not the one from Canary. I was then able to patch the boot file. The phone rebooted, but it's not working just right yet. None of my icons show up on my home screen, although if I press the recent apps list, it shows a bunch of apps, although selecting one doesn't do anything. I might have to put the original boot image back on just to get it to boot and worry about rooting later. Sigh. It's always something.
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
You did not have to uninstall Magisk. When you would complete the OTA, instead of rebooting you should go into Magisk and select install to inactive slot. As you uninstalled magisk, you're not getting this option. Uninstalling magisk is different from disabling the modules.
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
alanzaki073 said:
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
Click to expand...
Click to collapse
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Qnorsten said:
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
Click to expand...
Click to collapse
I was looking at a different guide, but will try the one you recommend. I'm aware there is no TWRP for the 8T. I did use that method for my prior OP6. I did patch and flash the patched boot image, but none of my apps appeared on my home page so I flashed the unrooted boot image so I could at least use the phone. Thanks.
rcbjr2 said:
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Click to expand...
Click to collapse
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Kollachi said:
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Click to expand...
Click to collapse
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
rcbjr2 said:
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
Click to expand...
Click to collapse
Nope i mean "fastboot boot xxxxx.img"
Kollachi said:
Nope i mean "fastboot boot xxxxx.img"
Click to expand...
Click to collapse
I figured out that's what you meant when I followed the instructions linked in another message. I had never booted that way previously. Thanks!
I am about to root my 8t using the guide someone linked above. My question is.. I'm on ver. 11.0.5.6.KB05AA will I still be able to root if I update or will it take away the ability to root.. also, will it affect the quality of the root ? Thanks in Advance.