I've been away from the scene for about 8 months, so pardon my ignorance.
I know that both TWRP and Magisk had issues with the new Android 10 towards the end of 2019 with the Pixel 3XL.
Is this still a limitation, is twrp flashing not achievable on Pixel 3XL with Android 10 and is it the same with Magisk?
Essentially I'm looking for root on the Pixel 3XL with Android 10.
Thanks
still met the same issues as used to be, but luckily Magisk is still the only way to get Root on Android 10.
Yeah got it all sorted now, had to patch the boot.img with magisk and flash it, can't flash zip via TWRP like I used to with the Pixel 2XL.
Have AdBlocker and Gpay all setup now with root.
Happy that I have root again. Life is just not the same without it.
Shame that I can not flash LineageOS though.
No it does not work on Android 10. The developer claims that he's working on it and you can follow his project on GitHub where he posts the change logs. Apparently the TWRP thread doesn't get updated on XDA.
They released a statement last month saying that it works for any phone that does not ship with Android 10 but that is not true at all. So keep your fingers crossed and next time you buy a phone don't buy one made by Google and their dual partition crap.
Related
So I just got the pixel xl 128 gb from Google because my nexus 6p had the battery issue. Just got this sucker turned on and I realized it is still on April security patch with 7.1.2. Now I am Verizon but didn't get it from a Verizon store so this should be unlockable correct? Where is the easiest method to unlock and flash twrp? I used magisk systemless on the 6p. Noticed pixel is a different beast. Can someone help me or at least guide me to the correct places since everything is so buried now with android O out and stuff. Thank you!
https://forum.xda-developers.com/pixel-xl/help/6p-refuge-pixel-xl-mail-t3670556/page2
Refugees over here.
https://forum.xda-developers.com/pixel-xl/help/6p-refuge-pixel-xl-mail-t3670556/page2
You should be ok with unlocked device from Google.
Magisk method doesn't work yet on PixeXL...coming soon.
We also don't have a flashable TWRP for Oreo. Guess we have to fastboot into it.
There seem to be 2 threads in this Guide form detailing unlock/root for Oreo. Haven't figured out which one to use yet.
akenis said:
https://forum.xda-developers.com/pixel-xl/help/6p-refuge-pixel-xl-mail-t3670556/page2
Refugees over here.
https://forum.xda-developers.com/pixel-xl/help/6p-refuge-pixel-xl-mail-t3670556/page2
You should be ok with unlocked device from Google.
Magisk method doesn't work yet on PixeXL...coming soon.
We also don't have a flashable TWRP for Oreo. Guess we have to fastboot into it.
There seem to be 2 threads in this Guide form detailing unlock/root for Oreo. Haven't figured out which one to use yet.
Click to expand...
Click to collapse
Ya everything is much different. I'm avoiding the update as I hope I can unlock the bootloader and root on 7.1.2 thank you though!
theDK10 said:
Ya everything is much different. I'm avoiding the update as I hope I can unlock the bootloader and root on 7.1.2 thank you though!
Click to expand...
Click to collapse
Just throw the switch and then do what you want. The update has nothing to do with it.
Sent from my Pixel using XDA-Developers Legacy app
theDK10 said:
So I just got the pixel xl 128 gb from Google because my nexus 6p had the battery issue. Just got this sucker turned on and I realized it is still on April security patch with 7.1.2. Now I am Verizon but didn't get it from a Verizon store so this should be unlockable correct? Where is the easiest method to unlock and flash twrp? I used magisk systemless on the 6p. Noticed pixel is a different beast. Can someone help me or at least guide me to the correct places since everything is so buried now with android O out and stuff. Thank you!
Click to expand...
Click to collapse
This guide is the easiest to follow.
I am in the same boat as you and after some researching it's fairly straight forward. Don't root or flash a kernel via fastboot, that is the outdated method, use TWRP.
Follow the guide. The biggest thing is flashing RC2. Magisk isn't working, don't even bother with it until it's updated, use SuperSU for the time being. From what I've read Magisk is close to being done.
When flashing ROMs or anything via twrp, keep an eye on which slot is active (go to reboot in twrp, it will tell you which slot is active) If you flash something and it boots back to twrp, reboot into the other slot and try restarting the system.
The biggest thing is to not mess with installing/flashing stuff when you're not around a computer you can use fastboot on. You might get stuck with a non-booting phone or not have TWRP to boot into and would need to fastboot into the RC1.img
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
You can use Android Pay with Magisk I believe. Magisk passes saftey net checks.
byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
Those downsides are enough for some, but the biggest PITA is if you didn't unlock your bootloader then you have to factory wipe when you unlock.
Tb0n3 said:
Those downsides are enough for some, but the biggest PITA is if you didn't unlock your bootloader then you have to factory wipe when you unlock.
Click to expand...
Click to collapse
well google backsup your app, mms, sms etc and the way you have your phone set up. Easy to restore and takes 30 mins depending on your connection.... I say go for it!
byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
for some it is android pay
but for others
they don't need it anymore
stock rom nowadays give us most of the options that we needed to root for back in the day
i used the pixel 2 without root for 1 week (before it came out )
and the only thing i need it for was adaway and custom kernels
i used non-root adblocker and it's actually worked fine
so if i am stuck with a phone with no root i can live with it
I always root, but the big downsides are around OTAs and needing to jump through hoops from time to time to update.
Finally it's a security issue, particularly a unlocked bootloader, it's super easy to erase pin or pattern locks from twrp. Also malware in a root app could be devastating to any info you access via phone.
byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
Because some security flaws that come along and some malicious apps expose the fact that you have root to be more effective.
If a good and stable rom like Pure Nexus that passes safety net works flawlessly on the Pixel XL 2 then that would probably be enough for me not to root. That would provide enough features and excitement to the already great experience that stock android now provides. Right now, i enjoy root in order to apply adaway and delete system apps if i so choose. Also nice to be able to use different color profiles. I am one of those that loves to be able to use Android Pay while rooted.
elreydenj said:
If a good and stable rom like Pure Nexus that passes safety net works flawlessly on the Pixel XL 2 then that would probably be enough for me not to root. That would provide enough features and excitement to the already great experience that stock android now provides. Right now, i enjoy root in order to apply adaway and delete system apps if i so choose. Also nice to be able to use different color profiles. I am one of those that loves to be able to use Android Pay while rooted.
Click to expand...
Click to collapse
I'm just here praying they're working on Resurrection Remix.
I was on PureNexus and decided what the hell and tried RR and it has everything PureNexus has and more.
DevanteWeary said:
I'm just here praying they're working on Resurrection Remix.
I was on PureNexus and decided what the hell and tried RR and it has everything PureNexus has and more.
Click to expand...
Click to collapse
Ill keep that in mind. Did RR pass safety net out of the box on the pixel XL?
elreydenj said:
Ill keep that in mind. Did RR pass safety net out of the box on the pixel XL?
Click to expand...
Click to collapse
I don't remember. Sorry. :/
I used to be an avid rooter and custom rom user. For me, I'm contempt with the stock factory images. May give PureNexus a shot if it comes around.
Besides, I had an incident with Chase Bank once where I was having trouble getting text alerts. After an hour on the phone with support, they noticed and mentioned I had a "tampered" device. Not that my problem had anything to do with my device being tampered with (rooted), and not that I had any modifications which could cause harm to my banking information, but in the long shot case something did ever happen with your money, I'm sure the banks would have no problem pointing their fingers at your phone.
So if a company like Chase scans to see if your device is rooted, I'm sure most app developers do without telling you.
If someone wants to chime in, not exactly sure how apps see it if you have a rom like Resurrection Remix, or PureNexus, and actually dont root it. I wonder if the apps still consider the device tampered with if there is no root access
byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
You can MOST definitely have Android pay with Root in Pixel. That is the beauty of dual partition setup. Have one partition rooted and other non-rooted, with both sharing the same data partition.
I had done this for the past year on the OG Pixel XL. The only time I would need non-root would be for Android pay - I would just boot to the other slot. Use Android pay and then reboot to the previously active slot after finished.
As for Custom ROM - I'm hoping against hope. Hard to imagine life without the features of PN or RR. However, it is not encouraging given that there is no a single OREO based Custom ROM yet for the OG Pixel XL. Who knows how many developers actually end up getting the Pixel 2 XL - which is more expensive. That is the only reason I'm still waiting with bated breath until my return period for Pixel 2 XL expires. Luckily, the One Plus 5t launches on Nov 16th and the reviews would be out soon. I know OP5 has RR custom ROM which is a big deal..
abogrhen said:
for some it is android pay
but for others
they don't need it anymore
stock rom nowadays give us most of the options that we needed to root for back in the day
i used the pixel 2 without root for 1 week (before it came out )
and the only thing i need it for was adaway and custom kernels
i used non-root adblocker and it's actually worked fine
so if i am stuck with a phone with no root i can live with it
Click to expand...
Click to collapse
Yes to all this. I haven't rooted since my Galaxy S5. I was perfectly fine with my Nexus 5X stock and do use Android Pay often enough to want to remain unrooted. I actually used to root and install stock-like ROMs so now that I've been getting Google phones, I have no need.
Sent from my Pixel 2 XL using Tapatalk
Hi guys, I finally decided to replace my good old Galaxy S7 edge and I came to the conclusion that I wanted, after using Samsung, OnePlus and Sony phones for years, the most streamlined Android experience possible without having to deal with OEM bloat, delayed updates, etc. anymore.
Result: I made the most obvious choice and I got an unlocked white 128GB Pixel 2 XL from the Google Store directly (I can't wait to receive it!).
I have a few questions though...
1) Will unlocking the bootloader alone (without actually rooting the phone) cause OTA updates to fail?
2) It's now possible to root your phone with Magisk without installing a custom Recovery (TWRP). Once installed, Magisk allows you to temporarily restore the stock, unrooted "boot.img". Is it enough for OTA updates to install properly or will they fail as soon as Magisk has been installed, even if the stock boot.img has been restored?
3) Does the Pixel 2 have an "e-fuse" that will get triggered once the bootloader is unlocked that will cause features to not work properly anymore, like on Samsung phones?
4) Any other recommendations or things I should be aware of?
Thanks guys
Only other thing I would read up on is how to work around the whole dual slots "feature" that these Pixel phones have. The last couple times I've tried to update to the latest security update, I get a "your device is corrupt and cannot be trusted" message and the phone won't boot. I end up have to scramble to flash stock boot.img to both slots A and B, flash the factory image to both slots, and hold my breath as to whether or not it's going to work. I wish there was an idiot's guide to updating firmware for this phone. Everyone that posts on this subject has a different opinion on how to do it properly. Going form any given security update rooted with Magisk, how does one update to the next month's firmware, without temporarily bricking the phone or wiping data? I've been unlocking phones and flashing custom roms since before Android was even invented. So I'm no stranger to this stuff, but it has become quite a production to keep up to date with this stuff.
Phazonclash said:
Hi guys, I finally decided to replace my good old Galaxy S7 edge and I came to the conclusion that I wanted, after using Samsung, OnePlus and Sony phones for years, the most streamlined Android experience possible without having to deal with OEM bloat, delayed updates, etc. anymore.
Result: I made the most obvious choice and I got an unlocked white 128GB Pixel 2 XL from the Google Store directly (I can't wait to receive it!).
I have a few questions though...
1) Will unlocking the bootloader alone (without actually rooting the phone) cause OTA updates to fail?
2) It's now possible to root your phone with Magisk without installing a custom Recovery (TWRP). Once installed, Magisk allows you to temporarily restore the stock, unrooted "boot.img". Is it enough for OTA updates to install properly or will they fail as soon as Magisk has been installed, even if the stock boot.img has been restored?
3) Does the Pixel 2 have an "e-fuse" that will get triggered once the bootloader is unlocked that will cause features to not work properly anymore, like on Samsung phones?
3) Any other recommendations or things I should be aware of?
Thanks guys
Click to expand...
Click to collapse
To answer your questions.....
1. No
2. Yes. But you'll have to unroot and completely uninstall magisk to take the OTA.
3. No
4. There are several guides to explain how to unlock the bootloader, install twrp, kernels, and root. Let me know if you'd like links, or you can search on your own if you'd like. Welcome to the P2XL. We hope you enjoy your stay ??
Hi all,
I know this may seem like a n00b question, but I hope you can point me in the right direction. I have a A320FL with Android 6.0.1 - build june 28 2017, and I blocked the auto update feature, because back then I read about the advanced locking technique and want to root my phone. Since then I looked at these forums, but found it quite difficult to gather all the information to get confident enough to flash/root my phone. In the past I rooted/flashed my Sony Z1c regularly and that was easy. But for some reason flashing the A320 seems much more difficult, with more chances for it to go wrong.
I'd like to have the following:
- Android Oreo stock, twrp, rooted and Xposed (optional if possible)
I found this thread about rooting and twrp and xposed, but it's an older manual for Android 7 and I don't know if it will also work with Oreo.
Other threads talk about unlock and the security path, but I'm not sure if it applies to my situation, or not? (since I have an older installation, perhaps the advanced locking technique isn't implemented)
Any help is appreciated. Thanks.
hatsikidee said:
Hi all,
I know this may seem like a n00b question, but I hope you can point me in the right direction. I have a A320FL with Android 6.0.1 - build june 28 2017, and I blocked the auto update feature, because back then I read about the advanced locking technique and want to root my phone. Since then I looked at these forums, but found it quite difficult to gather all the information to get confident enough to flash/root my phone. In the past I rooted/flashed my Sony Z1c regularly and that was easy. But for some reason flashing the A320 seems much more difficult, with more chances for it to go wrong.
I'd like to have the following:
- Android Oreo stock, twrp, rooted and Xposed (optional if possible)
I found this thread about rooting and twrp and xposed, but it's an older manual for Android 7 and I don't know if it will also work with Oreo.
Other threads talk about unlock and the security path, but I'm not sure if it applies to my situation, or not? (since I have an older installation, perhaps the advanced locking technique isn't implemented)
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
You should just be able to enable OEM unlock, flash TWRP, format data in TWRP, flash no-verity- noencrypt zip, and you should be fine I think.
Okay, and then flash the last stock rom and then Magisk for root?
hatsikidee said:
Okay, and then flash the last stock rom and then Magisk for root?
Click to expand...
Click to collapse
If you want to be on the latest update, then do it before you root. But yes, then you flash magisk after the rom after you got TWRP.. Make sure you boot up once or more before you flash magisk.
Longtime OnePlus owner (3T and then 5). The 5 is still a great device for me overall but I've never been thrilled with the camera (no OIS) or the intermittent GPS Lock issues I've had.
The 7T is on sale though it may be a bit large for me. The 4A looks like it will be very cheap and have a good camera.
Anyway, I know that devices that ship with Android 10 don't yet have TWRP so this would apply to both devices, but I've never rooted without it. I've seen the instructions using the patched boot image method. It seems straight-forward, but also risky.
Any thoughts from those of you who've always used TWRP and are now unlocking the bootloader, rooting with Magisk, and installing Edxposed without TWRP? Do you find that to be overly risky for a daily driver, or just fine if you follow instructions?
It's been good for me personally on my 7t, as I follow instructions. I sim unlocked mine within 3 days, bootloader unlocked within a week, converted to international firmware and then to a custom rom and I've landed on msm extended. You generally extract a bin file with python to get the fastboot files for a custom rom, and then flash them in fastboot or some roms have fastboot files with a bat file for windows that's super easy to use, just one click to install like in msm extended vs extracting files and then manually flashing like in omni.
Aside from my ramblings root is really easy to get, you generally(not always it depends on the rom I think) boot the patched boot img and then direct install in magisk manager. So fastboot boot \magisk.img ( or whatever file path and img name) or you can direct install to the inactive slot if you took an update(depends on rom I think) So basically take the boot.img from the rom or update, patch in magisk manager, boot it from your pc, and then direct install or to the inactive slot.
TLDR: it is safe if you follow instructions and can read.
Side notes, xposed is generally a privacy risk and threat so I wouldn't use that. Mods like xprivacylua are crap and don't actually work, use Blocker for trackers and analytics blocking.
And twrp is not too far off at this point, they've been slowly developing it and the chinese already have a full functioning one for the 7t(don't use it, not open source)
Grin59 said:
Side notes, xposed is generally a privacy risk and threat so I wouldn't use that. Mods like xprivacylua are crap and don't actually work, use Blocker for trackers and analytics blocking.
And twrp is not too far off at this point, they've been slowly developing it and the chinese already have a full functioning one for the 7t(don't use it, not open source)
Click to expand...
Click to collapse
Thanks, I might just wait for the non-Chinese TWRP before jumping in. TWRP has saved me from a few mis-steps along the way.
EdXposed - Yes, there are security issues with it and it's a hassle getting the correct variant these days, but I use GravityBox which requires EdXposed.
digger16309 said:
Thanks, I might just wait for the non-Chinese TWRP before jumping in. TWRP has saved me from a few mis-steps along the way.
EdXposed - Yes, there are security issues with it and it's a hassle getting the correct variant these days, but I use GravityBox which requires EdXposed.
Click to expand...
Click to collapse
We just got another twrp update for thee 7t, not perfect yet but better than the first version.
digger16309 said:
Longtime OnePlus owner (3T and then 5). The 5 is still a great device for me overall but I've never been thrilled with the camera (no OIS) or the intermittent GPS Lock issues I've had.
The 7T is on sale though it may be a bit large for me. The 4A looks like it will be very cheap and have a good camera.
Anyway, I know that devices that ship with Android 10 don't yet have TWRP so this would apply to both devices, but I've never rooted without it. I've seen the instructions using the patched boot image method. It seems straight-forward, but also risky.
Any thoughts from those of you who've always used TWRP and are now unlocking the bootloader, rooting with Magisk, and installing Edxposed without TWRP? Do you find that to be overly risky for a daily driver, or just fine if you follow instructions?
Click to expand...
Click to collapse
This is my first one plus device coming from a pixel 2 XL which I honestly loved so much like the way it just felt and I never rooted or messed with things like that since my Motorola nexus 6 lol I was a bit nervous but followed the steps and instructions and I'm rooted latest stock oos with blu_spark kernel and yet to run into any issues yet so if I can you would be able to aswell as long as you follow all steps on whatever it is you want to do your good.