Database Develop

[Q] Interested in rooting and flashing a custom ROM for the LGOB. [Q]

Hello guys, as you can see I am new to the forum and new to android in general. [Used to be an iOS fanboy] I have recently acquired an LG Optimus Black but i'm unhappy with the stock ROM provided by LG.
I have a few questions:
1) What are my options for rooting the device?
2) Once rooted, what custom ROMs are currently available for the device?
3) If I flash a new ROM is it possible and what would I need to have/do to restore the device back to the stock ROM?
And lastly...
4) What is the chance of fully bricking the device and what are my options if the device gets bricked?
Thanks a lot, [Hope this was the right section and hasn't been asked before...]
TomByrne94

TomByrne94 said:
[Hope this was the right section and hasn't been asked before...]
Click to expand...
Click to collapse
All was asked and ANSWERED before. Move your a** and search for it.

I have searched actually. The questions that have been answered aren't specific to my situation and I know that small details are very important when flashing phones. If you aren't answering the question I guess what you posted would be considered spam?

Guys,
Please refrain from bickering, two ways this can be easily resolved:
1. Use google search with the word xda in it to find your answer
2. Rather than posting move your a** and find it, if you know the link or answer, why not help a brother out?
I will say no more on the matter, its that simple.
THanks.

TomByrne94 said:
Hello guys, as you can see I am new to the forum and new to android in general. [Used to be an iOS fanboy] I have recently acquired an LG Optimus Black but i'm unhappy with the stock ROM provided by LG.
I have a few questions:
1) What are my options for rooting the device?
2) Once rooted, what custom ROMs are currently available for the device?
3) If I flash a new ROM is it possible and what would I need to have/do to restore the device back to the stock ROM?
And lastly...
4) What is the chance of fully bricking the device and what are my options if the device gets bricked?
Thanks a lot, [Hope this was the right section and hasn't been asked before...]
TomByrne94
Click to expand...
Click to collapse
No point arguing..if you don't wanna help just ignore.
If you wanna reply, make sure it helps others.
1) What options? It's either you root or you don't. Either way, your phone works.
2) Currently there's only NOVA Rom by knzo.
3) Read this thread here.
4) Chances of bricking are slim if you read before attempting anything. If in any case your phone is bricked (boot loop), refer to the above.
Hope it helps.
Welcome to the Android community

Thank you very much for the very active response and information.... I am also studying these issues.

knoxious said:
No point arguing..if you don't wanna help just ignore.
If you wanna reply, make sure it helps others.
1) What options? It's either you root or you don't. Either way, your phone works.
2) Currently there's only NOVA Rom by knzo.
3) Read this thread here.
4) Chances of bricking are slim if you read before attempting anything. If in any case your phone is bricked (boot loop), refer to the above.
Hope it helps.
Welcome to the Android community
Click to expand...
Click to collapse
Exactly what I needed, thanks a lot!

I've heard a lot of the current roots don't work for the OB?
And is NOVA the ONLY ROM at the moment, I thought I heard about another one?

Older firmwares, you can use Gingerbreak. If it doesn't work, then most probably you're on the newer firmwares. Then use SuperOneClick.
The other one is Pays ROM. It's been abandoned.
It needs v10b Firmware to run. If you're not familiar, stick to Nova ROM.
Cyanogenmod is in progress (i hope so)

knoxious said:
Older firmwares, you can use Gingerbreak. If it doesn't work, then most probably you're on the newer firmwares. Then use SuperOneClick.
The other one is Pays ROM. It's been abandoned.
It needs v10b Firmware to run. If you're not familiar, stick to Nova ROM.
Cyanogenmod is in progress (i hope so)
Click to expand...
Click to collapse
Alright, thanks alot. I'm going to wait for cyanogen I think... [Lets hope they are progressing...]

[Q] Lost root after flashing Android 4.3

Hi guys, I know you have tons of rules here and I tried my best to respect all of then by searching for a thread containing info on what in looking for but I couldn't find one. I rooted my phone a couple of years back and have been flashing various ROMs since. About a week ago however I flashed an unofficial android 4.3 ROM by CyanogenMod and after that once I discovered how buggy it was (as per the developer's warning) I decided to flash something else. However I couldn't access my recovery menu no matter what I tried and it looks like I've list root but I can't be sure of that. Ask the root apps aren't working and I got a toast from one of them saying you need root access to use this. Right now what I want is a way to either reroot or maybe there's a simpler way of solving this problem. If I could access the recover mode menu I could use the conventional way of rooting but right now I can't even di that. I'd really appreciate a solution if any of you could take the time out to give me one. Thanks so much and I really hope to hear from you.

I assume you flashed Chas' rom. If you could just read the op.... Chas gave everyone a soultion on a silver plate..

er.sorry
Abagnale said:
I assume you flashed Chas' rom. If you could just read the op.... Chas gave everyone a soultion on a silver plate..
Click to expand...
Click to collapse
To be really honest I'm not sure whether it was his ROM or not since I got it from a YouTube instructional video. There was a direct download link. Do you think you could please do me a favor and point me in the right direction to the solution? Losing my mind here since it's so buggy

prada_at_home said:
To be really honest I'm not sure whether it was his ROM or not since I got it from a YouTube instructional video. There was a direct download link. Do you think you could please do me a favor and point me in the right direction to the solution? Losing my mind here since it's so buggy
Click to expand...
Click to collapse
Go to Chas' Asylum thread in Android development, and use the search option. He gave the solution on 8th of August.
Sent from my GT-N7000 using xda app-developers app

At me it worked.
And saw it posted in a 4.3 thread/post
You have to disable and re enable it in developers option in settings.
And then try root privilege using apps to check if it worked like type su in terminal
Sent from my GT-N7000

[Q] HTC One (M7) Bluetooth audio issue other end cannot hear

Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede

Bob the Swede said:
Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Click to expand...
Click to collapse
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.

Thank you!
alray said:
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.
Click to expand...
Click to collapse
Thank you so much! Now I get what is what I might need help finding the right place or thread showing me how to flash the ROM etc. I will look around too of course now that I know what the problem is.

I need help...
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.

Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
The link posted by @alray above comes with the download and instructions for flashing TWRP. And the second link takes you directly to the rom.
The only way it could be easier is if he comes to your house and flashes it all for you

Hahaha, I'm sorry, that's embarrassing.

Bob the Swede said:
Hahaha, I'm sorry, that's embarrassing.
Click to expand...
Click to collapse
just take your time and read a lot ..it's all pretty simple once you get a grasp on whats going on

Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
you will first need to upgrade your firmware like said in the rom thread. Click on the link in that thread "Latest Radios and Firmware are REQUIRED and can be found here"
follow instruction to flash the latest firmware in that thread
then flash twrp 2.8.0.1 (also linked in the rom thread just above "Latest Radios and Firmware..." link.
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
then push the rom to your phone (either using adb push/adb sideload/usb otg) and install it using twrp.
like cisa said above, if you follow the instructions in that thread andtake your time, everything will be good.

THANK YOU!!!
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.

Bob the Swede said:
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.
Click to expand...
Click to collapse
:highfive:

Twrp heads up Safeguard yourself Use Correct twrp

I know TWRP topic has been live I'm just adding this info as a Safeguard heads up for using the Correct twrp for those that never flashed before .
Just wanted to post for those realizing twrp is available to Not flash the wrong one .
Zerofltespr.img is INCORRECT for tmobile s6.I say this because there are 4 to choose from when u use the links to it
It a just a heads up cause that file falls next to the Tmobile version if you are looking for the Tmo.
Make sure to choose 2.8.6.0 zeroflte.img it is 25.2mb
Not 2.8.6.0 zerofltespr.img.
It will not allow you to navigate thru twrp or reboot.
I did this by mistake
If you do by mistake JUST CF AUTO ROOT again and it will restore stock recovery
Sent from my SM-G920T using XDA Free mobile app

Not sure if we need a whole thread on this. People should just read and pay attention before they flash stuff to their phone
Period.

This isn't a New wide spread topic it's a small WARNING tutorial TO save people from a very easily made mistake .I expected this type of response. But the greater number of considerate people would appreciated such a small but usefully tip expecially when you could see this mistake easily being made .
It's a necessary sub topic in regards to 920t TWRP recovery.
Sent from my SM-G920T using XDA Free mobile app

It all good man. Just would be more appropriate to put that info here http://forum.xda-developers.com/showthread.php?t=3080833 where everyone else is talking about recovery flashing. We don't need a whole thread on this.

This is a good warning. I'm pretty experienced with these thing and am careful. I used Flashify to install TWRP because I'm at work. I selected S6 zeroflte and it gave me two options 2.8.6.0 and 2.8.6.0. So I selected the first one and installed it. Had I paid closer attention, after you select the one you want, it confirms the image name and sure enough, the first option turned out to be the Sprint version. So I had to do it again to flash the right one. I by chance stumbled across this thread just an hour prior to running into this issue, so I figured I flashed the wrong recovery. All is well now!

Thanks man for the appreciation. .I'm glad u seen it how i did .All I did was catch hell with this tip
Sent from my SM-G920T using XDA Free mobile app

Thanks for the warning. My cp is down at the moment so I'm in a holding pattern....

Wow thanks for this warning. I've been thinking of flashing TWRP for a while now and this really helped me get it done properly. Used Flashify as well and checked to make sure it was working fine.

Barging in.
Any rom developers out there, should I make zerofltetmo version of TWRP? Basically updating the default.prop to only flash versions for zerofltetmo, or do you all want to use zeroflte?

bigbiff said:
Barging in.
Any rom developers out there, should I make zerofltetmo version of TWRP? Basically updating the default.prop to only flash versions for zerofltetmo, or do you all want to use zeroflte?
Click to expand...
Click to collapse
zeroflte is fine, unless you foresee a reason we should have our own?

@bigbiff Great to see you stop by! So as long as this works for us I don't see anything wrong with just keeping it simple. Is it just the cdma and gsm variants that are different? Just trying to understand this so that I can say I learned something new today! Lol I will say that I am thrilled that you and the TWRP team work so fast and have made huge developments in device recoveries. I thank you for the work that you have done here! Much respect....

shojus said:
@bigbiff Great to see you stop by! So as long as this works for us I don't see anything wrong with just keeping it simple. Is it just the cdma and gsm variants that are different? Just trying to understand this so that I can say I learned something new today! Lol I will say that I am thrilled that you and the TWRP team work so fast and have made huge developments in device recoveries. I thank you for the work that you have done here! Much respect....
Click to expand...
Click to collapse
So far Edge is different between CDMA and GSM, and non-edge CDMA and GSM. So really 4 variants. But one of the big issues seems to be the disparate firmware or OEO issues that people are having flashing the versions I have released. It's hard to get a straight story between real issues and OEO.

bigbiff said:
So far Edge is different between CDMA and GSM, and non-edge CDMA and GSM. So really 4 variants. But one of the big issues seems to be the disparate firmware or OEO issues that people are having flashing the versions I have released. It's hard to get a straight story between real issues and OEO.
Click to expand...
Click to collapse
Well, I have not really had much time to flash anything on this new device but everything that I have has been fine. I will keep you posted in your main thread if I run into any issues but thanks for the response!

How to root Pixel / XL on 7.1?

I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.

sturmeh said:
I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.
Click to expand...
Click to collapse
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220

mattzeller said:
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220
Click to expand...
Click to collapse
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.

sturmeh said:
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.
Click to expand...
Click to collapse
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out

eatsleep said:
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out
Click to expand...
Click to collapse
Buy it directly from Google and the bootloader won't be locked, only if you buy it through a carrier like Verizon will the bootloader be locked
Sent from my SCH-R220

This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.

Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done

fkofilee said:
Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done
Click to expand...
Click to collapse
The worst possible thing you could write...

ldeveraux said:
The worst possible thing you could write...
Click to expand...
Click to collapse
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it

fkofilee said:
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it
Click to expand...
Click to collapse
If your intent was truly altruistic, you wouldn't feel the "burden" of stating it publicly. So no, it doesn't matter.

Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Confirmation number: 57C48888US937054E

Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Appreciate all you do Chainfire, seriously. Can't wait for you to work your magic

Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.

Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...

hutzdani said:
Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.
Click to expand...
Click to collapse
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Ker~Man said:
Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...
Click to expand...
Click to collapse
Totally agree. Thanks for speaking up!

Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Sent from my Pixel XL using Tapatalk

tveith said:
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Totally agree. Thanks for speaking up!
Click to expand...
Click to collapse
What ever but tour the same guys who's going to be asking for OTAs and asking devs to do this that and the other as fast as humanly possible.
If you want it that bad do it your self or sit and wait like a good little child.
No dev is going to rush something because of some people in a forum get a grip, like I said it's their time and it will be ready when it's ready.
You might think I'm going off on one but read the rules page for Christ's sakes.

sionicion said:
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Click to expand...
Click to collapse
The chance you'll have to erase is always present when rooting. Even when your device is fully prepared something may go wrong. At least you have already unlocked your bootloader, which reduces that chance.
File-based encryption will probably not be a reason to for wiping, though. It works fine in the dev version of SuperSU with Android 7.0 on a 5X.

Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app

mrnovanova said:
Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks interesting, but without twrp you sure are taking a big chance if something goes wrong.
Sent from my Pixel using Tapatalk