any marshmellow roms? - Google Pixel XL Questions & Answers

i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything

ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Edit: Opps sorry thought was OP3 thread :laugh:

ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
This phone launched with nougat. You can't run marshmallow on it.

liam_davenport said:
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Click to expand...
Click to collapse
where do i find those? (i have searched but can only find cm14 for pixel?
toknitup420 said:
This phone launched with nougat. You can't run marshmallow on it.
Click to expand...
Click to collapse
this is what i was afraid of....

ncsuwolfs said:
where do i find those? (i have searched but can only find cm14 for pixel?
this is what i was afraid of....
Click to expand...
Click to collapse
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.

toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.

There are no Marshmallow ROM's anywhere for this phone.
Never was, never will be.
Magisk isn't an Xposed replacement.
There is no replacement for Xposed.
Dammit, I miss my ~17 Xposed modules.
Most of which gave me options that you won't find on any custom Nougat ROM.

toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
It's a root option. As in you can run SuperSU or Magisk. Magisk has mods that can accomplish certain things that Xposed did but the majority of them don't work with the pixel so don't count on a suitable replacement.
jhs39 said:
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
Click to expand...
Click to collapse
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
CZ Eddie said:
Magisk isn't an Xposed replacement.
Click to expand...
Click to collapse
This isn't completely true. There are Magisk mods that overlap things that Xposed was capable of. So depending on what you are trying to do and IF mods even worked for the pixel. It could be a replacement for some.

The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.

jhs39 said:
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
Click to expand...
Click to collapse
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.

pcriz said:
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
Click to expand...
Click to collapse
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.

jhs39 said:
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
Click to expand...
Click to collapse
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.

Yeah for the pixel it's pretty straight forward, if you want to root use chainfire's zip it's 2.79 SR3, you're even advised on 2.82 that pixel users will not want to upgrade.
As far as the may bootloader situation, flash the april bootloader and you don't need to bother with the signing zip. Besides, I think dealing with knox was much worse

pcriz said:
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Click to expand...
Click to collapse
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.

jhs39 said:
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
Click to expand...
Click to collapse
You went from saying "Magisk and SuperSU don't install properly or don't keep root" to talking about the changes to boot signing on newer bootloaders.
If you are going to share information at least try to be accurate. There is a whole slew of users in the development section running rooted ROMs just fine but if a new user reads your posts they will assume root is broken and flashing the pixel leads to boot loops.
You don't want to deal with the verified boot signer all you need to do is flash the april bootloader and reboot. It happens once. If that is too difficult then maybe those same people shouldn't bother flashing anything period.
No one said flashing and modding would be easy but flashing a bootloader ain't hard.

You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.

jhs39 said:
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
Click to expand...
Click to collapse
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.

pcriz said:
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. QUOTE]
I answer these questions a lot and that is most certainly true.
Click to expand...
Click to collapse

pcriz said:
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
Click to expand...
Click to collapse
Actually that's absolutely not true. I came from a Nexus 6P. On the XDA threads for that phone there is an accurate, clear, up to date step by step guide on how to flash anything with that phone, including separate instructions for how to root, install a custom recovery, how to install a custom Rom and how to go back to stock. On the Pixels the threads are a complete free for all filled with confusing, contradictory and inaccurate information. I just read posts from earlier today from someone who is getting boot loops when flashing SuperSu. Not a single person responded by suggesting that he use the April bootloader. The suggested solution (which didn't work) was to flash the boot sig zip. How exactly is somebody supposed to research flashing on the Pixel when the XDA threads for this phone are a complete shambles? And since you are supposedly such an expert at flashing on this phone why don't you do something useful and help other people who are having problems instead of wasting everybody's time with your utterly pointless posts about how easy it is to flash on this phone and how people having trouble are idiots who didn't do their own research? You aren't simply part of the problem, dude--you are literally the personification of everything that is wrong with XDA.

jhs39 said:
.
Click to expand...
Click to collapse
This discussion ain't worth reading whatever it is you typed dude. I'm going to agree to disagree.
Sorry stable root is an unattainable unicorn for you. Sorry you're having such a difficult time. Sorry that making excuses for false information is a priority over finding out how it's actually done.
Happy flashing, best of luck to you sport.

Related

google pixel xl build #NKG47L

HI,
I purchased a google pixel xl, the bootloader is currently locked I would like to unlock and root if possible. the phone is running android 7.1.2 build NKG47L. Ive searched youtube, and xda for means of rooting, etc but im not having any luck on finding what would help me.. so some help would be greatly appreciated
https://forum.xda-developers.com/pixel-xl/how-to/index-google-pixel-xl-t3466185
Hopefully you don't have the Verizon version of the Pixel XL.. If you do unlocking the bootloader is impossible. If you don't then flashing and rooting the Pixel XL is possible but unusually difficult. The instructions seem to change from month to month and you need to use a specially modified version of Magisk because the official one doesn't work on the Pixel. If you go the SuperSu route they do have an official version for the Pixel. I've been flashing for years and it pretty much took me an entire day to successfully flash a custom recovery, a custom rom, a custom kernel, root with Magisk and get the phone to pass safety net. I've never owned a phone that was such a headache to flash on. Good luck.
jhs39 said:
Hopefully you don't have the Verizon version of the Pixel XL.. If you do unlocking the bootloader is impossible. If you don't then flashing and rooting the Pixel XL is possible but unusually difficult. The instructions seem to change from month to month and you need to use a specially modified version of Magisk because the official one doesn't work on the Pixel. If you go the SuperSu route they do have an official version for the Pixel. I've been flashing for years and it pretty much took me an entire day to successfully flash a custom recovery, a custom rom, a custom kernel, root with Magisk and get the phone to pass safety net. I've never owned a phone that was such a headache to flash on. Good luck.
Click to expand...
Click to collapse
Because you are having a hard time doesn't mean everyone will. Literally every chance you get you have to post the exact same narrative about how hard this is. It's like you are trying to poison other people's experiences because you find this so difficult. Let OP form their own opinion because frankly there are tons of users having zero issues rooting romming and etc..
Good Lord.
pcriz said:
Because you are having a hard time doesn't mean everyone will. Literally every chance you get you have to post the exact same narrative about how hard this is. It's like you are trying to poison other people's experiences because you find this so difficult. Let OP form their own opinion because frankly there are tons of users having zero issues rooting romming and etc..
Good Lord.
Click to expand...
Click to collapse
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would​ logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
jhs39 said:
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would​ logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
Click to expand...
Click to collapse
Not claiming it's easy. Just saying it gets repetitive to see you in how many threads griping about how this is such an insurmountable task.
And of course you see people with issues. Why do I need to comment that I'm not having issues. Heck when someone does comment that they aren't having issues you refute that because you are having a hard time.
You say I should be more constructive, lol please please please read my post history and maybe you will see how many people I have made efforts to help. I've been helping people in the forum, I've been helping people on Reddit, I've been helping people on discord, irc, etc etc. I've turned down money for helping people. How many people have you helped? How have you paid forward any help you have gotten on the pixel? Hell I even told you why you couldn't flash twrp after you downgraded from the O beta. So please don't tell me about being constructive bro.
"Flashing on Android for years" means nil my friend. Maybe if you took the time to understand the device it wouldn't be so difficult.
Do you even know why you couldn't flash twrp? It's because the OTAs flash to the opposite slot so when you got the ota for Android N from O N flashed in the other slot.
TWRP patches both boot.imgs but now your inactive boot.img is incompatible with twrp so it hangs up.
Super simple fix, now that you know there are two slots. You figure out how to swap slots at the bootloader. Then you learn how to flash all and flash all in both slots
Then you get a light that goes off because you took the time to read how twrp works in it's thread and realize you don't even need to flash all. You could simply flash the boot img in both slots. Because if you know what twrp patches then you know exactly what files you need.
I've been flashing for years also but I'm humble enough to know I should read before crying to people that are doing it without issue.
As far as the magisk "issue", well if anyone took the time to go to the magisk thread they would see the device isn't officially supported. Who's fault is it you didn't do that?
What was stopping you from searching the magisk thread before you started? I mean obviously you ignored where it stated it's not supported.
You can lead a horse to water my man. Can't make him drink.
jhs39 said:
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would​ logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
Click to expand...
Click to collapse
It's "extremely easy" to flash on this phone. It's the hacking and deving thats hard. Give me a zip that works and a functioning Twrp, it will be like taking candy from a baby. Yeah, and Google's not helping any of us.
Well THAT escalated quickly...
Sent from my SM-N910V using Tapatalk
Thanks for the help. I have been able to get the phone rooted, etc but I can't get TWRP recovery to stick. But do I have to reflash TWRP recovery after I flash SU files for root?
yamaha_wins said:
Thanks for the help. I have been able to get the phone rooted, etc but I can't get TWRP recovery to stick. But do I have to reflash TWRP recovery after I flash SU files for root?
Click to expand...
Click to collapse
I had to boot into my rom once, go back into fastboot TWRP and then flash the TWRP zip again in order to get it to stick.
@jhs39 and @pcriz, you're both correct in this matter and hopefully you all can just agree to disagree. I agree with you both, if you're a flasher like most of us and I too have been flashing for years. In fact about 90% of the phones I've owned have all been flashed and I average about two phones per year. That said I'm not expert and do find some things harder here and there but I'm techie enough to work through it with help from members of this forum. @pcriz I've used many of your instructions and assistants on this thread so thank you! I too believe flashing on the pixel has been very difficult mainly because the device changed the way things usually worked (slots etc.). I can't remember the last time it took me hours to flash a simple ROM. After I learned a little bit of what was going on with TWRP and the whole slot A/B configurations I was able to at least troubleshoot my own issues and get things working a little better. I would say anyone having issues need to take the time to really read and understand the device because they don't function the say as before. The instructions do change because Google changes things up. Manufactures don't want us flashing any more and with security being a top priority flashing is quickly being discouraged.
I've gotten to the point now where I just want to get my pixel which is no longer my daily driver (my S8 plus is) to stock but even that isn't working. I've tried numerous times to flash an image and it fails every single time. Why????? I have come to love a stock experience even though I still love the customization you get with a custom ROM. If I were to pick right now I'll just stick with stock; if I can ever get the phone to flash the stupid image so I can try Android O lol.

Debating on rooting my Pixel 2XL, looking for seasoned android user's advice.

Hi all,
I am possibly interested in rooting my device. I have been rooting/rom'ing since back on my HTC Hero forever ago. Made a brief trip to iOS, and got into jailbreaking, but always missed the Android atmosphere. I am having issues with the battery on my device, and have debated factory resetting the device, and came across the forums about rooting.
I would just run a stock rom, with root, to be able to use Gravity box and Xposed. I am not super familiar with terminal/command line, so that part worries me a bit.
Anyone that is rooted, how does your device's battery last? Any major issues you notice? I use my camera for pictures of my family everyday, and don't want to risk anything that could compromise this feature.
Thanks in advance
Rooting doesn't hinder or damage or affect your battery directly
If you have enough reasons to root just root
I have plenty reasons to root that's why i did
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
I've had lots of Android phones and tablets over the years, and every one was rooted at some point. Imo, rooting is not as critical as it used to be. Back in the early days of Android, rooting was the only way to get certain features that were later incorporated into Android. As Android matured, rooting became less important unless you needed a specific function or app. Rooting is still required for stuff like Titanium Backup, AdAway, Viper4Android, etc, because those need access to system-level files, which is impossible without root permissions.
Ask yourself what do you plan to do with root access? If you have a specific need for root, then go for it. Obviously you are not new to the game, and the procedure for rooting Pixel 2 is brain-dead simple compared to what you did for HTC Hero. However, if you don't have a specific need or plan, then it is not worth messing with imo. The Pixel 2 is an absolute beast out of the box. Root tweaks won't get you significantly better performance. I am rooted and use Sysconfig patcher (a Magisk module) to allow doze for Google Play Services for a very small gain in battery life. But I wouldn't root just for that. Monthly updates are a little more hassle if you are rooted, but if you get that far then you should be able to flash updates too.
AwkwardUberHero said:
Hi all,
I am possibly interested in rooting my device. I have been rooting/rom'ing since back on my HTC Hero forever ago. Made a brief trip to iOS, and got into jailbreaking, but always missed the Android atmosphere. I am having issues with the battery on my device, and have debated factory resetting the device, and came across the forums about rooting.
I would just run a stock rom, with root, to be able to use Gravity box and Xposed. I am not super familiar with terminal/command line, so that part worries me a bit.
Anyone that is rooted, how does your device's battery last? Any major issues you notice? I use my camera for pictures of my family everyday, and don't want to risk anything that could compromise this feature.
Thanks in advance
Click to expand...
Click to collapse
I too am a stock rom + root user. My battery life is outstanding for my usage patterns, usually 8-12 hours of SOT. As far as rooting, only you can answer that. Personally, I love it!! I like using dark themes, AdAway, TiBu, and the ability to use custom kernel tweaks. Having said all that, I haven't noticed any decrease in performance with day to day usage that you would likely use. So, if you ask me....root that sucker! ????
Badger50 said:
I too am a stock rom + root user. My battery life is outstanding for my usage patterns, usually 8-12 hours of SOT. As far as rooting, only you can answer that. Personally, I love it!! I like using dark themes, AdAway, TiBu, and the ability to use custom kernel tweaks. Having said all that, I haven't noticed any decrease in performance with day to day usage that you would likely use. So, if you ask me....root that sucker!
Click to expand...
Click to collapse
Seeing your input on this, Badger, makes me want to do it. Granted, not having rooted in over four years or so, I feel like I am missing a wealth of knowledge on this subject. I may give it a shot later today and see what happens. The only thing that worries me is installing the updates that come out each month. Do you do those monthly?
AwkwardUberHero said:
Seeing your input on this, Badger, makes me want to do it. Granted, not having rooted in over four years or so, I feel like I am missing a wealth of knowledge on this subject. I may give it a shot later today and see what happens. The only thing that worries me is installing the updates that come out each month. Do you do those monthly?
Click to expand...
Click to collapse
Oh I absolutely do the monthly updates using fastboot to install the factory images. It's actually very easy once you get the hang of it. You can look over my personal guide if you'd like so you have an idea of what to do :good:
Here's some more info for you to read as well :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Badger50 said:
Oh I absolutely do the monthly updates using fastboot to install the factory images. It's actually very easy once you get the hang of it. You can look over my personal guide if you'd like so you have an idea of what to do :good:
Click to expand...
Click to collapse
Do you really need to remove the lock screen password? I flashed the OTA (using this method: https://forum.xda-developers.com/pixel-2-xl/how-to/how-to-applying-monthly-security-t3750234), and I had no issue entering the PIN from within TWRP (twrp-3.2.1-2).
And don't forget that rooting is a XDA rush!
uofirob said:
Do you really need to remove the lock screen password? I flashed the OTA (using this method: https://forum.xda-developers.com/pixel-2-xl/how-to/how-to-applying-monthly-security-t3750234), and I had no issue entering the PIN from within TWRP (twrp-3.2.1-2).
Click to expand...
Click to collapse
Just my personal preference really. I just don't take chances with twrp if I don't have to :good:
sublimaze said:
rooting Pixel 2 is brain-dead simple compared to what you did for HTC Hero.
Click to expand...
Click to collapse
I never rooted my Hero but did completely unlock my HTC 4G LTE(S-off???). Dear lord was that a nightmare. I think back then it actually required a tool(Dirty Racoon???), only certain ROM's would boot on certain bootloaders, etc. I don't miss those days lol.
AndrasLOHF said:
I never rooted my Hero but did completely unlock my HTC 4G LTE(S-off???). Dear lord was that a nightmare. I think back then it actually required a tool(Dirty Racoon???). I don't miss those days.
Click to expand...
Click to collapse
I did root the HTC Hermes (win5) which was a trip!
AwkwardUberHero said:
Seeing your input on this, Badger, makes me want to do it. Granted, not having rooted in over four years or so, I feel like I am missing a wealth of knowledge on this subject. I may give it a shot later today and see what happens. The only thing that worries me is installing the updates that come out each month. Do you do those monthly?
Click to expand...
Click to collapse
While the 2 XL is a great phone even without root, I think there is just too much fun, experimenting, and customization to miss if not rooted. But this is a personal choice and you have to decide if you really want a specific battery icon, or any other custom feature.
You been given links to some steps and guides which are very good references. Since you said it's been four years since you rooted, I'm throwing in my guide as well
I am not a technical kinda guy, and sometimes the little details are what trip me up, so I crafted this initially for myself needing to be reminded of each step.
It is very detailed, step by step with tips and links and everything needed in one place. It certainly isn't the final authority for sure, but I've used it dozen and dozens of times with no issues. You can always default to the guide or other references if something isn't clear.
Take the plunge, I think you'll be very glad you did. In my opinion, root makes a great device an excellent device
@Az Biker @Badger50 I will be trying this on a Mac. Anyone happen to have steps for a Mac?
Thanks again for everything!
Mac instructions are in the op of the thread badger posted#7
galaxys said:
Mac instructions are in the op of the thread badger posted#7
Click to expand...
Click to collapse
Thanks! Totally overlooked that.
Badger50 said:
Oh I absolutely do the monthly updates using fastboot to install the factory images. It's actually very easy once you get the hang of it. You can look over my personal guide if you'd like so you have an idea of what to do :good:
Click to expand...
Click to collapse
Hey badger, thanks for these steps. Debating on trying this tomorrow. Do you have the actual rooting directions as well for a Mac? Tried looking in YouTube but could only find windows.
Thanks again in advance.
AwkwardUberHero said:
Hey badger, thanks for these steps. Debating on trying this tomorrow. Do you have the actual rooting directions as well for a Mac? Tried looking in YouTube but could only find windows.
Thanks again in advance.
Click to expand...
Click to collapse
First you'll need to enable developer options by tapping on the build number 7 times in settings/system/about phone. Then enable OEM unlocking and USB debugging. You'll need adb/sdk installed on your Mac, then you'll need to unlock your bootloader with the follow fastboot commands..
fastboot flashing unlock....
And
fastboot flashing unlock_critical...
You have to have magisk 16.3 and the twrp installer zip in your internal storage.
Then you'll need to fastboot the twrp.img with the Mac specific prefix command (which I don't know), but the command is...fastboot boot twrpxxxx.img
That'll boot you into twrp, then hit install, and navigate to where your twrp installer and magisk zips are. Flash twrp, followed by magisk, reboot, and you should be rooted.
Badger50 said:
First you'll need to enable developer options by tapping on the build number 7 times in settings/system/about phone. Then enable OEM unlocking and USB debugging. You'll need adb/sdk installed on your Mac, then you'll need to unlock your bootloader with the follow fastboot commands..
fastboot flashing unlock....
And
fastboot flashing unlock_critical...
You have to have magisk 16.3 and the twrp installer zip in your internal storage.
Then you'll need to fastboot the twrp.img with the Mac specific prefix command (which I don't know), but the command is...fastboot boot twrpxxxx.img
That'll boot you into twrp, then hit install, and navigate to where your twrp installer and magisk zips are. Flash twrp, followed by magisk, reboot, and you should be rooted.
Click to expand...
Click to collapse
Awesome. Thank you. I was messing with adb a bit today, enabling immersive mode and what not. I think that I can follow these steps.

Not an easy root as advertised

I bought this phone based on the overall web's assurance that it was one of the easiest phones to root. I found a guide in XDA that I thought would run me through the whole thing without problems. At first, this was true but as I went along everything fell apart. The posts on the web made it sound like the unlock code the bootloader was all you would need. I knew better than that but I still expected the simplicity I would need as a noob. If there aren't any phones like that please tell me. Also in the meantime I may have bricked my brand new OnePlus 5T. Irritating to say the least. Any ideas?
Compared to my Verizon Galaxy Note 4 this thing is a breeze to root. Here's a link to an un-bricking tool: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
This thread pretty much has all instructions for unlocking your bootloader and rooting your 5T: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
I haven't bricked my device yet so I can't speak for the first tool, but the guide is very well written.
Yeah.. it wasn't quite as bricked as I thought LOL. Just an anxious noob probably. However, I am now running into a situation where the phone will not accept Magisk 16.0 and I would really like to go systemless if possible. I have flashed twrp-3.2.1. I hope that was at least correct.
Flash either codeworkx or Blu spark twrp, then latest magisk version and you have root.
colossus1958 said:
Yeah.. it wasn't quite as bricked as I thought LOL. Just an anxious noob probably. However, I am now running into a situation where the phone will not accept Magisk 16.0 and I would really like to go systemless if possible. I have flashed twrp-3.2.1. I hope that was at least correct.
Click to expand...
Click to collapse
Had the same problem with Magisk 16 not booting the phone. Flash Magisk 15.3 from twrp and once boited update from the magisk manager. Worked for me..
Sent from my OnePlus 5T using XDA Labs
Is it possible to flash one custom recovery over the top of another or do I have to go back to my stock recovery first.
colossus1958 said:
Is it possible to flash one custom recovery over the top of another or do I have to go back to my stock recovery first.
Click to expand...
Click to collapse
Yes. Flash the new recovery through your old recovery and reboot.

Trying to keep root features without root. (Hotspot)

When going to Android 11 I'd like to keep my device unrooted.
The only things I want to keep is vanced (will install the version w/I magisk) and my Hotspot. I know there's some play store Hotspot apks but I can never get them to work.
Last update the build.prop edit no longer worked, but i found a zip that enabled it from XDA. Believe it needed to be flashed in magisk but not sure.
I intend to try and flash the 11 OTA and just remove -w, hoping I'll keep the Hotspot modification.
If it matters, my SO wanted me to get back into pokemon go and I can't play on a rooted device. Tried magisk hide but that didn't work.
Any advice would be appreciated, cheers.
AlPoo said:
When going to Android 11 I'd like to keep my device unrooted.
The only things I want to keep is vanced (will install the version w/I magisk) and my Hotspot. I know there's some play store Hotspot apks but I can never get them to work.
Last update the build.prop edit no longer worked, but i found a zip that enabled it from XDA. Believe it needed to be flashed in magisk but not sure.
I intend to try and flash the 11 OTA and just remove -w, hoping I'll keep the Hotspot modification.
If it matters, my SO wanted me to get back into pokemon go and I can't play on a rooted device. Tried magisk hide but that didn't work.
Any advice would be appreciated, cheers.
Click to expand...
Click to collapse
You won't be able to keep any Magisk modifications without magisk. The way Magisk works is systemless so it needs to have the Magisk installed to mount the modules over the necessary directories. Also, for Pixels on Android Q and Android R you can't mount the system partitions to even modify them in the first place, so even if Magisk did directly modify the partitions they wouldn't work for devices with our logical partitions.
Pretty sure the way PoGo detects root is by searching for files/folders in your install storage called Magisk, twrp, or various other root names. So I'd suggest making sure those kinds of folders are cleaned out or renamed to something unrelated to root.
Also, Magisk doesn't support R yet so you won't be able to root yet even if you wanted to.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
You won't be able to keep any Magisk modifications without magisk. The way Magisk works is systemless so it needs to have the Magisk installed to mount the modules over the necessary directories. Also, for Pixels on Android Q and Android R you can't mount the system partitions to even modify them in the first place, so even if Magisk did directly modify the partitions they wouldn't work for devices with our logical partitions.
Pretty sure the way PoGo detects root is by searching for files/folders in your install storage called Magisk, twrp, or various other root names. So I'd suggest making sure those kinds of folders are cleaned out or renamed to something unrelated to root.
Also, Magisk doesn't support R yet so you won't be able to root yet even if you wanted to.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Ah. So maybe I should keep the -w in the OTA to make sure to clean out some folder/files.
Didnt know R wasn't supported yet, kinda figured it wouldn't be since it just came out, but thanks for saving the hassle of finding out the hard way.
I've read going through threads here and saw that some people had lost root but kept some modifications after updating. Hoped that would have worked or there'd be able way without root out there that I was unaware of.
Anyway, thanks for the response!
AlPoo said:
Ah. So maybe I should keep the -w in the OTA to make sure to clean out some folder/files.
Didnt know R wasn't supported yet, kinda figured it wouldn't be since it just came out, but thanks for saving the hassle of finding out the hard way.
I've read going through threads here and saw that some people had lost root but kept some modifications after updating. Hoped that would have worked or there'd be able way without root out there that I was unaware of.
Anyway, thanks for the response!
Click to expand...
Click to collapse
Well I just installed PoGo real quick after checking my internal storage and renaming any file/folder with Magisk in the name to remove Magisk, and with Magisk hidden with a random package name and app name and PoGo hidden in magisk hide I was able to successfully log in without it detecting anything. So if you do wish to have modifications once Magisk supports R just make sure to keep an eye on your files/folder names and you should be all good :good:
As for the threads you've been reading, that's definitely curious. Do you know if they were pixel users? Or just people using a GSI or something?
Sent from my Pixel 3a XL using XDA Labs
AlPoo said:
Ah. So maybe I should keep the -w in the OTA to make sure to clean out some folder/files.
Didnt know R wasn't supported yet, kinda figured it wouldn't be since it just came out, but thanks for saving the hassle of finding out the hard way.
I've read going through threads here and saw that some people had lost root but kept some modifications after updating. Hoped that would have worked or there'd be able way without root out there that I was unaware of.
Anyway, thanks for the response!
Click to expand...
Click to collapse
OTA will not wipe your phone. I updated this way last night from Q, not rooted.
Just realize that the Android 11 developer release is not designed to be run as a "daily driver". It's a first alpha release and it is going to be full of bugs and incompatibilities.
There is zero reason to install this on anything but a spare phone that you develop on.
sic0048 said:
Just realize that the Android 11 developer release is not designed to be run as a "daily driver". It's a first alpha release and it is going to be full of bugs and incompatibilities.
There is zero reason to install this on anything but a spare phone that you develop on.
Click to expand...
Click to collapse
24 hours in. Absolutely zero issues so far.
poncespr said:
24 hours in. Absolutely zero issues so far.
Click to expand...
Click to collapse
Thanks for the progress report....
My comment was directed mainly at the OP. Somehow I don't think he is Google's target audience for the developer build and I am afraid he will be the type that complains or begs for help when things don't work right.
That being said, I am also surprised that the release is running so well......
sic0048 said:
Thanks for the progress report....
My comment was directed mainly at the OP. Somehow I don't think he is Google's target audience for the developer build and I am afraid he will be the type that complains or begs for help when things don't work right.
That being said, I am also surprised that the release is running so well......
Click to expand...
Click to collapse
No disrespect. Just commenting on my experience.
I am also surprised. Only weird thing was asking to register my sim. I'm guessing it was looking for an esim. Other than that, not a single force close or slow down. But to be honest it doesn't look like a big update as the version number suggest. Feels more like a little spit and polish. Like this should be Android Q 10.1.
I myself gave up rooting. The only two reasons I was rooting were adaway and viper.
poncespr said:
.But to be honest it doesn't look like a big update as the version number suggest. Feels more like a little spit and polish. Like this should be Android Q 10.1.
Click to expand...
Click to collapse
As with most major android updates since Oreo. Most visible changes now are slight UI revisions and some new features.
However, there are a load of under the hood changes being made. Some for the better, some for the worse.
Sent from my Pixel 3a XL using XDA Labs
Not to thread hijack, (which is what i am going to do anyway, but being POLITE about it ?), can anyone point me to a Hotspot solution for Sprint, without root? All the other various methods/tricks i used in the past that worked, like manually editing the LTE APN etc, just aren't working on this 3aXL.

Question Struggling to root...

Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.
cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
RushPL said:
I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.
Click to expand...
Click to collapse
Sadly, that's the way XDA developed in the most recent years. A lot of developers have become "impatient", they rarely tolerate questions (which they consider unnecessary for reasons of their own) or consider everything that is not in their concise jargon offtopic and either ignore, flame or delete those.
The basics are not explained anymore, they expect everyone to work naturally with the tools at hand, most often or not "small" steps are left out (like clicking on something, or changing a menu), or they refer to "go look at that guide" - only then - that guide tells you (aswell) "for step 3, go look at that guide", because "everyone should know" - that way the rooting community is quite small and elitist; and it's hard for outsiders to come in (and potentially add something to the pool of stuff) simply because it's not a pleasant experience to "dive" into the world of Android customization. It's a sad development and only very few seem to be intend on breaking it.
Then we also have the problem of manufacturers trying to make this communities life harder, just take a look at Google and the constant war to have safetynet NOT trip, to give people the chance to use banking apps or GPay. It's a constant struggle and many "guides" get out of date pretty quickly - and most often or not, those are not kept up to date, or getting demolished by a mod team, so that also adds to the whole confusion, when people try to work with guides / community fixes that won't even work anymore.
cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...irmware-sd1a-210817-036.4353807/post-85857811
I followed the instruction from this post to restore my P6P to preinstalled October firmware, then updated with November firmware OTA, then unlocked bootloader and root again. My phone works much better now.
I made a mistake of flashing the vbmeta and boot imgs of October firmware for rooting after updating November firmware OTA. I experienced some strange issues with my phone until I restored it with Official Google Android Flash Tool and start the whole rooting process again with the correct version of vbmeta and boot imgs.
Pekempy said:
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?
RushPL said:
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?
Click to expand...
Click to collapse
No need but thank you for offering.
The vbmeta is also new to me. I want to be clear, I've mostly compiled others' instructions (credited in the post) with my own experience, and tried to make it as easy to follow as I can
I was able to root successfully with working Safety Net! Thank you @Pekempy

Categories

Resources