Develop Bugs

any marshmellow roms?

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.

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.

Does rooting require you to wipe your phone? (and other basic rooting questions)

The last time I rooted a phone was with a GS3 to install CyanogenMod. I've recently picked up a Pixel 2 XL, and I had some fairly noob-esque questions:
1. Do I have to wipe my phone to root it? That is, there is no "in-place" rooting?
1a. Are there any good methods to make a full backup *without* root before rooting it, and then restore it after I root?
2. Does rooting my phone make future OS updates more difficult/impossible? Ie: Will I still get OS updates, or will I have unroot my phone to get updates, then reroot it, possibly wiping everything?
3. What's the best method to go about doing this now? Googling around, and looking around here, I see a few different, but similar methods. I also see references to a "critical unlock," but no matter how many guides I read, I don't understand it. I'm starting to feel like I don't understand enough anymore to root my phone :-/
I really want to just be able to get back hosts-file based ad blocking again, and maybe a few other tweaks.

1, 1a: Go here and start reading, if you haven't already done so. To root requires unlocking the bootloader, which will cause the device to be wiped. It's best not to put anything important on the device until afterward.
2: OTAs must be applied manually. See the link I provided for instructions.
3: The P2XL is apparently unique in having two unlock commands. The non-critical unlock unlocks the bootloader while still providing some protection. The critical unlock strips all protections from the bootloader. To be on the safe side, execute both commands as mentioned in the link I provided.

Strephon Alkhalikoi said:
2: OTAs must be applied manually. See the link I provided for instructions.
Click to expand...
Click to collapse
Does that require re-wiping the device? Will I still get notified of updates, or will I have to keep track of new releases on my own?

The linked thread specifically says that OTAs do not require a device wipe. You should still get notifications.

Strephon Alkhalikoi said:
The linked thread specifically says that OTAs do not require a device wipe. You should still get notifications.
Click to expand...
Click to collapse
Sorry, I must have missed that. Thanks for pointing me to an answer! I appreciate all your help.

LucentPhoenix said:
Sorry, I must have missed that. Thanks for pointing me to an answer! I appreciate all your help.
Click to expand...
Click to collapse
Seems daunting. But read and ask till your comfortable. Lots of really helpful and Patient people on this lovely site. Stock + Root is the ish.
G

Ok, another question.... I'm looking to try out Android P. Will I be able to upgrade to that without wiping my phone?

LucentPhoenix said:
Ok, another question.... I'm looking to try out Android P. Will I be able to upgrade to that without wiping my phone?
Click to expand...
Click to collapse
Some have "dirty flashed" P over oreo with removing the -w flag from flash-all.bat script in the P factory image with mixed results. Your best bet is to clean flash the P build with fastboot to avoid any potential problems. However, yes, it will wipe your phone

Drat. Restoring apps and settings is far less painful than it used to be, but re-enabling all my 2FA is a pain in the ass.
If I do a clean flash of P, will I be able to upgrade P as new releases come out, or will I have to clean flash every time there's a new release, until it goes public?

LucentPhoenix said:
Drat. Restoring apps and settings is far less painful than it used to be, but re-enabling all my 2FA is a pain in the ass.
If I do a clean flash of P, will I be able to upgrade P as new releases come out, or will I have to clean flash every time there's a new release, until it goes public?
Click to expand...
Click to collapse
Yes you would be able to upgrade to the beta releases. However, you'd likely have to go back to Oreo, which would require a full wipe and clean flash, then upgrade to the betas. The first beta release is due out this month according to all the scuttlebutt I've read, so I think your best bet is just to wait a little longer. Here's a thread on the PDP1 that several folks are using :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/android-9-0-developer-preview-1-t3757268

Just bought a xiaomi mi 10t lite. Some questions...

Hello!!
As the title says, I have just bought a xaomi MI 10t lite. Absolutely wonderful phone in my opinion.
Always root my phones but simply consider skipping it this time.
But if I would like to do it anyway, I have some questions.
1. Is it difficult to root this device?
2. Which rum would you recommend? I want a fast phone that works well to play with. It does not matter if it takes a lot of batteries.
3. Read a bit and saw there were lots of tools. Which tools are best to use, it does not happen that xiaomi has been so forward-thinking that they create their own software to do this?
Have a good night my fellow geeks!
//knorrigbollen Sweden
Edit: sorry haven't learned to write on the phone yet so had to edit some spelling screw ups.

I haven't looked into rooting this device yet. I don't know how many rom's are currently developed for this phone but I would recommend xiaomi.eu stable rom.
The only hurdle is unlocking the bootloader, you need to use unlock tool provided by Xiaomi. The unlock tool comes with a wait time, I had to wait for about ~2 weeks before I could unlock but wait time can vary. After unlocking the bootloader it's pretty much basic adb procedures and install script's to flash a rom.
I'm just starting to look into TWRP for this device, looks like it's still being developed but should be ready to use.
Just check out the guide's you can find online during your unlock waiting time and you should be golden. Greetings from your neighbor ~FIN

Root only if its absolutely necessary
No rom for this device has been cooked yet, even in the future stick to stock rom for stablity and relaiblity.
Tools to use?
check XiaoMiTool & XiaomiADBFastbootTools

@Knorrigbollen
1. easy to root, just unlock the bootloader, patch stock boot.img from Magisk Manager and flash it in fastboot. No TWRP required (even if it's available).
2. stock ROM is nice, once you remove/block most of MIUI apps. No ads, no tracking, responsive, next to no bugs. Personally I see absolutely no reason to switch to another ROM, I appreciate included Google apps.
3. you need to use Xiaomi tool to unlock the bootloader (where you need to wait 2 weeks to be able to do that). You can use this nice GUI to "debloat" MIUI apps https://github.com/Szaki/XiaomiADBFastbootTools, but standard Android fastboot/adb tools work very well.

Personally I'm loving the MIUI, it has some great features, they thought of a lot of little things. I too always root my devices but this time I have not. I would only do a basic root using Magisk/TWRP official when/if it comes out so that I can mod my apps/games and block ads etc.

Yes I agree you. I will also wait until Magisk or TWRP is released. In my case I want to get rid of some pre-installed system apps.

Z3RO2K said:
Personally I'm loving the MIUI, it has some great features, they thought of a lot of little things. I too always root my devices but this time I have not. I would only do a basic root using Magisk/TWRP official when/if it comes out so that I can mod my apps/games and block ads etc.
Click to expand...
Click to collapse

Francescohub said:
Yes I agree you. I will also wait until Magisk or TWRP is released. In my case I want to get rid of some pre-installed system apps.
Click to expand...
Click to collapse
Magisk is working on this device since release of the phone and TWRP has been released a couple of weeks ago as well. There is not much left to wait for..

_mysiak_ said:
Magisk is working on this device since release of the phone and TWRP has been released a couple of weeks ago as well. There is not much left to wait for..
Click to expand...
Click to collapse
oh that is really good to hear!
Well I am back into android now for 1 month, I used to root back in 2017 my Huawei p9 lite and in 2015 my Samsung Galaxy S3. Now I dont know how to start with, cause my last phone was iPhone 7 (yea, shame on me; Jailbreak is nothing to compare with root). Is there a good step by step instruction of how to root my phone?
Thanks in advance; greetings from Germany and sorry for mistkaes in spelling.
Francesco

Francescohub said:
oh that is really good to hear!
Well I am back into android now for 1 month, I used to root back in 2017 my Huawei p9 lite and in 2015 my Samsung Galaxy S3. Now I dont know how to start with, cause my last phone was iPhone 7 (yea, shame on me; Jailbreak is nothing to compare with root). Is there a good step by step instruction of how to root my phone?
Thanks in advance; greetings from Germany and sorry for mistkaes in spelling.
Francesco
Click to expand...
Click to collapse
My preferred way:
1. unlock the bootloader
2. patch your own boot.img (or use one from this topic https://forum.xda-developers.com/t/root-stock-and-magisk-patched-boot-images.4201597/)
3. hotboot patched boot.img and install Magisk from Magisk manager (this will create a backup of stock boot image, which will come in handy for OTA updates)
4. that's it
P.S. you will have two weeks waiting period for the bootloader unlocking, so plenty of time to read how Magisk/systemless mods work now

_mysiak_ said:
My preferred way:
1. unlock the bootloader
2. patch your own boot.img (or use one from this topic https://forum.xda-developers.com/t/root-stock-and-magisk-patched-boot-images.4201597/)
3. hotboot patched boot.img and install Magisk from Magisk manager (this will create a backup of stock boot image, which will come in handy for OTA updates)
4. that's it
P.S. you will have two weeks waiting period for the bootloader unlocking, so plenty of time to read how Magisk/systemless mods work now
Click to expand...
Click to collapse
thank you very much. I think I ll start now with unlocking my bootloader.

_mysiak_ said:
Magisk is working on this device since release of the phone and TWRP has been released a couple of weeks ago as well. There is not much left to wait for..
Click to expand...
Click to collapse
Not officially it's not. Until I see it listed as supported here: https://twrp.me/Devices/Xiaomi/ with reports of it being functional I'm not touching unofficial. I see reports on that one posted with various issues.

Z3RO2K said:
Not officially it's not. Until I see it listed as supported here: https://twrp.me/Devices/Xiaomi/ with reports of it being functional I'm not touching unofficial. I see reports on that one posted with various issues.
Click to expand...
Click to collapse
That's of course completely up to you. On my previous phones I had issues even with "official" TWRP which never got fixed. Unofficial or custom builds were usually more stable for me and obviously available much faster than the official build.
Anyway, the fact is, that Magisk is out since day 1 and TWRP was released unofficially recently, so anyone who want's to do some modding is free to go. TWRP for rooting is optional and I personally don't use it at all.

Z3RO2K said:
Not officially it's not. Until I see it listed as supported here: https://twrp.me/Devices/Xiaomi/ with reports of it being functional I'm not touching unofficial. I see reports on that one posted with various issues.
Click to expand...
Click to collapse
The TWRP looks weird but it's completely fine, used unofficial builds on most of my devices and they've been better than official ones. I get your point though

it should be official now..
I am in kind of same situation. I bought a mi10t lite from amazon, once it arrived home I noticed that it is vodafone brand with old miu and security version update..
I want an official europe version and block again the phone in order to have everything like original.
I applied for the xiaomi official unlock but it will take at least a week..
Any way to do it NOW ?
Thanks,
D.

the incredible said:
it should be official now..
I am in kind of same situation. I bought a mi10t lite from amazon, once it arrived home I noticed that it is vodafone brand with old miu and security version update..
I want an official europe version and block again the phone in order to have everything like original.
I applied for the xiaomi official unlock but it will take at least a week..
Any way to do it NOW ?
Thanks,
D.
Click to expand...
Click to collapse
Nope, none of the methods/tips for quick unlock are working, you just have to wait. Also I would advise to use the phone a little during the waiting time to avoid further delay in unlocking (I read many reports mentioning longer waiting times when they kept their phone in the drawer for the whole week).

Question All in one tool in the works?

I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!

CacheOnlyPlease said:
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
Click to expand...
Click to collapse
As far as I know, only the original Pixel 1 has an all-in-one tool* ("click button, wait, have fun - even though the P1 tool only came years after release!"), it has always been the culmination of a couple ADB steps/commands in a certain order, plus some manual flashing/magisk file creation incl. copying a couple files from your phone to your PC or vice versa.
Especially since Google changed alot of stuff with Android 11 and Android 12, it's a bit more complicated to root since the days of the original Pixel.
That doesn't mean that there can be no all-in-one root tool here, but as of now we have none and I don't see how one could be created in the foreseeable future.
*https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730227/

Morgrain said:
As far as I know, only the original Pixel 1 has an all-in-one tool* ("click button, wait, have fun - even though the P1 tool only came years after release!"), it has always been the culmination of a couple ADB steps/commands in a certain order, plus some manual flashing/magisk file creation incl. copying a couple files from your phone to your PC or vice versa.
Especially since Google changed alot of stuff with Android 11 and Android 12, it's a bit more complicated to root since the days of the original Pixel.
That doesn't mean that there can be no all-in-one root tool here, but as of now we have none and I don't see how one could be created in the foreseeable future.
*https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730227/
Click to expand...
Click to collapse
For sure, that's actually the All in One tool that I remember using with my Oneplus 7 Pro. This is my first Pixel phone (does the Nexus 6P count?) so I wasn't sure if developers would be all over it, or if Google has made things more complicated over the past couple of years. Either way I appreciate the reply and will probably dive into unlocking/rooting over the holiday weekend.

CacheOnlyPlease said:
For sure, that's actually the All in One tool that I remember using with my Oneplus 7 Pro. This is my first Pixel phone (does the Nexus 6P count?) so I wasn't sure if developers would be all over it, or if Google has made things more complicated over the past couple of years. Either way I appreciate the reply and will probably dive into unlocking/rooting over the holiday weekend.
Click to expand...
Click to collapse
If you want to read a bit about complication, take a search engine and find out what
Android 11 scoped storage
Android 12 Dm-verity (device-mapper-verity)*
Android 12 Vbmeta verification**
SafetyNet Android
Android Hardware Attestation
means.
*is a method by which an image on block devices (the underlying storage layer of the file system) can be checked to determine if it matches an expected configuration, using a cryptographic hash tree. If the hash doesn't match, dm-verity prevents the stored code from loading.
**is the other half of this - it provides a cryptographically signed reference hash which is used to verify the integrity of /boot, /system, and /vendor partitions. The vbmeta image is only used to verify /boot, while vbmeta-system is used to verify /system.
Click to expand...
Click to collapse
Google has been actively working - for a couple of years now - at making the modding/rooting communities life harder. We have always found a workaround, some require work (spoofing device ID, forcing software attestation, et cetera) or don't work that well at all, but it's a constant struggle.
Every firmware update is a small struggle and you got to pray to the man above that your device will still boot up, even if you have those pesky magisk modules disabled.

Morgrain said:
Google has been actively working - for a couple of years now - at making the modding/rooting communities life harder. We have always found a workaround, some require work (spoofing device ID, forcing software attestation, et cetera) or don't work that well at all, but it's a constant struggle.
Click to expand...
Click to collapse
I think Google's goal was to make our devices more secure, not making modding/rooting harder.

CacheOnlyPlease said:
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
Click to expand...
Click to collapse
Not sure if this fits the bill of what you're looking for
Android Flash Tool

Perhaps this
Android Dollhouse (Flashtool) | TESTERS REQUIRED
Android Dollhouse The Definitive Android Flashtool. This is the support thread for Pixel 6 Pro. If you have another device, please check the other threads: Pixel 2XL: Support Thread Pixel 6: Support Thread I'm releasing the first user-facing...
forum.xda-developers.com

Az Biker said:
Not sure if this fits the bill of what you're looking for
Android Flash Tool
Click to expand...
Click to collapse
Sort of. Like I mentioned, I haven't dove into the details yet of rooting my Pixel 6 Pro yet, however can this tool you linked get me out of a potentially sticky situation if I ever need to load the stock firmware (ROM) onto it? That's really my biggest concern is messing something up. If I have a tool handy to get me back to stock, even if it wipes the whole phone, then I'm much more likely to dive in, you know.

For an all-in-one tool... what's wrong with fastboot?

CacheOnlyPlease said:
Sort of. Like I mentioned, I haven't dove into the details yet of rooting my Pixel 6 Pro yet, however can this tool you linked get me out of a potentially sticky situation if I ever need to load the stock firmware (ROM) onto it? That's really my biggest concern is messing something up. If I have a tool handy to get me back to stock, even if it wipes the whole phone, then I'm much more likely to dive in, you know.
Click to expand...
Click to collapse
If you haven't already looked them over, check the 6 PRO link in my sig, Step by step directions, pretty much each and every detail to make it easy for people like me who aren't rooting gurus.
Fastboot is the tool to pull you back from the abyss should you screw the pooch. Plenty of places you can find commands to help you out in a pinch, usually bringing you back to a factory fresh image.
Fastboot, update, and root a few times and it'll become much less concerning and tedious.