Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)
dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread
Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt
Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip
Related
Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Xdevillived666 said:
Hey guys, so I installed twrp and formatted data, rebooted, installed super su (sr version), and now my phone is decrypted and rooted on 7.1.1 Just passing this along if anyone needs it
Click to expand...
Click to collapse
Screenshots guys
I can confirm CF-Autoroot works without flaws!
I used the Nexus Root Toolkit and that worked a charm, got recovery and root installed easily.
What recovery are you guys using? latest 3.0.2-3?
Krenol said:
What recovery are you guys using? latest 3.0.2-3?
Click to expand...
Click to collapse
I'm using 3.0.2-1 but I have heard people say 3.0.2-2 works as well. Hope that helps
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
RonnellTapawan said:
does formatting the data is really needed? I tried to flash twrp with everything on stock (encrypted), it works on first boot of twrp but whenever I boot to system then try to boot to twrp, it gives 'No Command' and I have to reflash twrp again :silly:
Click to expand...
Click to collapse
It would seem so. Until I decrypted, I wasn't able to keep it permanently installed.
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Razeer123 said:
I can also say that Nexus Root Toolkit worked for me. That's a great app - I suggest using it and helping the developer!
Click to expand...
Click to collapse
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
I rooted at first with PHH suhide and the only thing I couldn't do was change system files, as expected. Flashed back to stock, updated to dev preview again (clean slate) and installed magisk v8 and root. Everything is working fine and dandy.
Xdevillived666 said:
Yeah, it is nice . I just like doing it myself ,though I used the app to flash stock recovery and get the ota.... Speaking of the ota , does anyone else have "android 7.1.1" under about phone ???
Click to expand...
Click to collapse
Yeah, I think everyone have this number. I suppose the x.x.1 means Security Patch number, but I'm not sure.
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
ToothTooth said:
I'm new to the beta program. What happens if I root and install a custom recovery in this beta version 7.1.1? I assume that I will no longer be able to get future incremental OTA beta updates?
Click to expand...
Click to collapse
You can. Just before installing , reinstall stock recovery and then install ota or use flash fire
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Morning all
Just checking in to say I've been running this 7.1.1 preview for over 24 hours, without so much as a slight hiccup. It's very smooth and fluid. I haven't bothered rooting or anything yet as the phone runs beautifully as is, but no doubt I will tinker when I get back from a short break. Only disappointing thing is android pay not working due to unlocked bootloader
Anyone has no-force decrypt boot img, coz seems like device is encrypted, as Im stuck with TWRP(3.0.2-1) logo
odunke01 said:
Have any of you been able to use SuHide?
Im just getting a constant bootlogo and no further.
Click to expand...
Click to collapse
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
odunke01 said:
My bad, didnt wait long enough.
Problem is though that we cant seem to keep changes to the /system file on the preview
https://www.reddit.com/r/Android/comments/58npsl/71_appears_to_aggressively_fix_errors_to_the/
Click to expand...
Click to collapse
What are you using su hide for?
It was for pokemon go.
Although I have reverted to PN on 7.0 as I was having other issues. Root (edit:and recovery) wasn't holding after reboot and my hosts file kept disappearing.
I also missed the night light.
Three again. Verizon, Dutsche and every one else. Flashing now.
So far full images only, no OTA.
OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?
sliding_billy said:
OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?
Click to expand...
Click to collapse
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
TonikJDK said:
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
Click to expand...
Click to collapse
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
sliding_billy said:
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
Click to expand...
Click to collapse
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
Kisakuku said:
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
Click to expand...
Click to collapse
Just was a gut feeling that whatever was going wrong in the developer build would somehow been implemented in the May build. I am sure they are unrelated, but that was why I asked before the OP was updated to include the SU break.
The VZ OTA will download if you set the date to May 4th.
just checked my phone and got Verizon update without changing date
My OTA for Verizon didn't hit yet. And moving the date forward didn't help. Hopefully soon.
what will happen to supersu if try to flash this full factory image via flashfire and
bush911 said:
what will happen to supersu if try to flash this full factory image via flashfire and
Click to expand...
Click to collapse
It will be gone.
Pixel users are reporting bootlooping on the May update after flashing TWRP only
https://forum.xda-developers.com/showthread.php?p=72121371
https://forum.xda-developers.com/showthread.php?p=72120712
What are the chances that this was done purposely? "Breaking root and twrp"
DR3W5K1 said:
What are the chances that this was done purposely? "Breaking root and twrp"
Click to expand...
Click to collapse
Anyone try Magisk? I imagine same result.
Sent from my Pixel XL using Tapatalk
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
itchy67x said:
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
Click to expand...
Click to collapse
Just use April's bootloader.
Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
thx that works
Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
Thanks, that works for the Pixel too. I flashed April's K bootloader on the May L version no problem. TWRP and SU work fine now.
dowlf said:
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
Click to expand...
Click to collapse
FWIW: sideload of n2g47o worked fine on my (stock) XL. Did you have any modifications?
PLEASE READ MY IMPORTANT NOTICE ABOUT 8.1 BELOW
See update as well!
Hey, guys! This is my first thread ever, so please give me some grace. (I do not know all the formatting stuff yet)
I decided that because I had to wipe my Pixel 2 XL twice in the process of trying to figure this out, I may as well write a quick tutorial on how to do this the easy (and mostly safe) way.
This is where they all insert the disclaimer:
Code:
This tutoial is based on software I did not write or contribute to in any way, If you have issues with it, contact their respective developers, Google can help with this. DO NOT blame me for your now-a-fancy-paperweight-pixel,
I have diplomatic immunity and will tell you to contact my lawyer who doesn't care. You risk what you risk, take responsibility for that.
Now for the meat....
What you need:
Unlocked bootloader with MAGISK ROOT (other root may work, only tested magisk beta)
The Latest OTA File from the official download page, saved to your device
The Flashfire App by one of the greatest XDA legends of all time, Chainfire
The flashable zips for Magisk and any other stuff you want installed (like a custom kernel) when the update gets flashed (typically magisk modules do not need to be reflashed, they stay installed)
Advisable: nothing that has modified your system partitions (only have systemless mods like magisk)
Now that you're all set:
Open Flashfire and grant it root permissions.
Tap through all the warnings
Hit the plus sign and hit "Flash ZIP or OTA"
Find your stored OTA file you downloaded from the Google OTA page.
Check all three available options, (Auto-mount, Mount system..., and Restore Boot and Recovery)
Repeat step #3 with your newfound ability to flash zips, add a kernel (I use Flash Kernel) and flash the newest official magisk beta the same way. NOTE: Check boxes for these shouldn't need to include "auto-mount" or "restore boot and recovery images"
DISABLE ever-root settings completely from the flash queue.
Click the red lightning button at the bottom left.
Give it up to 5 minutes to do its business.
Reboot and profit.
If that didn't make sense, watch my simple video!!
(there is one mistake in the video, on all other things than the OTA itself, DO NOT check the box for restoring stock boot and recovery)
NOTE: You are unable to flash recoveries through this method, I've tried it and so far no luck. We may be able to later when apps let us flash the boot partition properly but for now, it won't stick.
Credits:
Chainfire for his amazing flashfire app!
Team Pixel for their awesome phone.
XDA for all the years of being awesome.
topjohnwu for magisk badassery
If you should be credited, PM ME.
IMPORTANT NOTICE:
Magisk beta thread clearly states that currently (12/05/2017) Magisk 14.5 with official pixel support is only tested up to 8.0, NOT 8.1 yet. Due to this and the fact that aosp 8.1 is super duper new and most kernels likely don't have an 8.1 version, I'd recommend waiting till this post is updated to flash anything 8.1
UPDATE 12/29/2017: As of now flashfire works for some things on oreo, but Ill need to look into it after we get another Oreo update to see if it can be flashed from there, however this may become obsolete assuming you can just use magisk's new features to do updates the official way. (google it)
That's all, Folks!
If this helped you, SMASH that thanks button! Also, Please try to keep OT stuff to a minimum.
I'll be posting a video soon that shows the flashfire process in a little better detail. Posted it, in the instructions!!
Nice work man. Always nice seeing people share their processes.
Sent from my Pixel 2 XL using Tapatalk
I've done similar ota flash with Flashfire on other devices. Will try this on my Pixel XL 2 with the next ota! Kudos
This method should work to flash the DP2 OTA from november update right?
Triscuit said:
This method should work to flash the DP2 OTA from november update right?
Click to expand...
Click to collapse
As long as the update is a newer one than your current one, is NOT an 8.1 beta, and is a FULL Ota (as in, it's larger than 1gb file) then it should flash. Of note: these are NOT the factory images you find on a very close by page from Google, they have to be the OTA zips.
What do you need to do if you have TWRP installed already? Can you still use this method?
uofirob said:
What do you need to do if you have TWRP installed already? Can you still use this method?
Click to expand...
Click to collapse
From what I remember from my Nexus 6p, having TWRP or Stock recovery made no difference flashing the update in FlashFire. But if you want TWRP installed you'll have to flash it again after the OTA due to the OTA replacing it unless you chose "Restore boot and recovery" during the zip selection process. Eben then I am not 100% sure TWRP will remain.
Sent from my Pixel 2 XL using Tapatalk
Does the OTA with this method delete the userdata partition? Or does it keep personal data intact?
so the magisk "install to Second slot (After OTA)" doesnt work?
FlashFire has not been updated since the Pixel 2 was released. Is it really meant to work with the Pixel 2?
cb474 said:
FlashFire has not been updated since the Pixel 2 was released. Is it really meant to work with the Pixel 2?
Click to expand...
Click to collapse
This is what I'm thinking. I doubt this will work at all. Flashfire is finicky at best. Works great when it works. Has never been updated to work on our device.
rester555 said:
Does the OTA with this method delete the userdata partition? Or does it keep personal data intact?
Click to expand...
Click to collapse
Nope. It updates, just like the title says. No wiping your rear required. Just a clean plop.
JeffBea said:
This is what I'm thinking. I doubt this will work at all. Flashfire is finicky at best. Works great when it works. Has never been updated to work on our device.
Click to expand...
Click to collapse
It fully recognized my device as supported, and the update worked, I have tested it.
thomasamas said:
It fully recognized my device as supported, and the update worked, I have tested it.
Click to expand...
Click to collapse
I'll definitely try this then when December updated hits then. This was my preferred update method on my 6p.
JeffBea said:
I'll definitely try this then when December updated hits then. This was my preferred update method on my 6p.
Click to expand...
Click to collapse
Make sure to check for Magisk and your preferred kernel compatibility with the 8.1 update when it comes. Flashing Magisk when the OS doesn't yet work with it could cause some serious headaches, so check the Magisk thread. I'm sure you know what happens when you flash an incompatible kernel too....
In the case Magisk isn't compatible yet, you can always check for SUPERSU systemless compatibility, and do that instead of flashing Magisk.
linezero said:
so the magisk "install to Second slot (After OTA)" doesnt work?
Click to expand...
Click to collapse
This is what I would like to know as well
For those of us that were on the original pixel phone without a custom recovery, the blow method was always the fastest and easiest way to update without losing root. Anyone tried on the Dec update?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Just tried this method and worked flawlessly.. Thank you OP!
Sent from my Pixel 2 XL using Tapatalk
mrbracht said:
Just tried this method and worked flawlessly.. Thank you OP!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Did you use this process to upgrade to the release build of 8.1 (Dec update)?
Jexx11 said:
This is what I would like to know as well
Click to expand...
Click to collapse
As far as I know, Magisk 14.5 understands both partitions now, and will flash to BOTH a/b, if you check the script for it, that's what it does. If this isn't what you're looking for, please clarify!
The January updates are up.
OTA is live too. Just 50.8 MB for 1st Gen XL.
ylapas said:
OTA is live too. Just 50.8 MB for 1st Gen XL.
Click to expand...
Click to collapse
Installing now
ylapas said:
Installing now
Click to expand...
Click to collapse
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
sb1893 said:
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
Click to expand...
Click to collapse
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
TENN3R said:
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
Click to expand...
Click to collapse
I have always just booted TWRP - I never have flashed it. Sorry for the confusion.
Has anyone been able to root the January update with Magisk?
UPDATE:
I haven't had any boot loop issues after updating, flashing TWRP, and routing with Magisk, so I thought I would post my steps:
Note: My bootloader is unlocked.
Before updating, I flashed the Magisk Uninstaller zip.
Once completed, I rebooted to bootloader and flashed the January factory image (saving data) > booted TWRP > flashed TWRP > rebooted recovery > flashed Magisk 18.0 > rebooted.
I haven't had any boot loop issues.
Magisk is installed and passes Safety Net check, but I wasn't able to grant root privileges for apps right away. It took a while (5 minutes) to get the prompt to grant root privileges. Finally got the prompt and now everything seems to be working correctly.
I hope this helps someone!
Does anyone have the January pre-rooted boot.img?
BoboBrazil said:
Does anyone have the January pre-rooted boot.img?
Click to expand...
Click to collapse
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
sb1893 said:
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
Click to expand...
Click to collapse
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
^^^
This is a 1st.........never seen anyone ask for it........LoL
BoboBrazil said:
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
Click to expand...
Click to collapse
Sorry - my mistake - when you said "pre-rooted" I took that to mean "before rooted" - meaning the stock boot.img. Unfortunately, I do not have the Magisk rooted boot.img handy. But, it only takes a few minutes to root using the standard process with Magisk....might be quicker than waiting for a response to your request??? Just a thought...good luck...
crackerjack1957 said:
^^^
This is a 1st.........never seen anyone ask for it........LoL
Click to expand...
Click to collapse
Pretty common on the newer pixel and OnePlus forums. Someone usually shares it to save others some of the work
Currently out driving, but read that latest canary Verizon of magisk worked with android Q, so I went ahead and pulled the file to flash, no idea about the lastest TWRP but if you want to try ahere it is, obviously you can get it at the github repo also. Will try when I get home, please let me know
It will most probably not work:
https://twitter.com/topjohnwu/status/1105922417002799106
It was the aosp image should work fine if TWRP boots
Confirmed doesn't work manually patching boot image
I got a bootloop when I flashed via TWRP.
Sent from my Pixel 2 XL using XDA-Developers Legacy app
I was going to try, but I've been out and about all day - glad you all already tried.
I'm gonna remove root and play with Q for a while - maybe John will make some headway (or else that other dude that seems to have another way in can get it working).
pk92 said:
Confirmed doesn't work manually patching boot image
Click to expand...
Click to collapse
Mind sharing the patched boot image?
Subhojit said:
Mind sharing the patched boot image?
Click to expand...
Click to collapse
I said it didn't work; so I deleted the patched image. If you want I can create a new one?
bootloop just waiting
Maybe flashing the zip with a flasher like franco kernel manager or elementalx kernel manager while waiting for twrp?
TENN3R said:
Maybe flashing the zip with a flasher like franco kernel manager or elementalx kernel manager while waiting for twrp?
Click to expand...
Click to collapse
You'd need root to do that.
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
ANDR01DN00B said:
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
Click to expand...
Click to collapse
Does removing screen lock security work?
Will try latest canary when I get home, when I got twrp to work with Q I had done a fresh install no security. Will try in an hour
ANDR01DN00B said:
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
Click to expand...
Click to collapse
Thanks for the info - I'll try it right now.
ANDR01DN00B said:
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
Click to expand...
Click to collapse
Where did you read that?
Guys you should at least watch John Wu´s twitter. He is working on new biuld that will work, but its not out yet.
ANDR01DN00B said:
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
Click to expand...
Click to collapse
TWRP worked fine for me using my standard update procedure. I downloaded the ota, side loaded it with TWRP, reinstalled TWRP before rebooting and I can still decrypt with my swipe pattern by booting to recovery.
Mikulec said:
Guys you should at least watch John Wu´s twitter. He is working on new build that will work, but it's not out yet.
Click to expand...
Click to collapse
This. And reading is fundamental.