yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] Born<ICs:
It wasn't just Oreo hampering development. Even on Nougat it was a long effort just to dev recovery and root due to new system (A/B partitions) and security.

Stock Oreo is so solid no real need for ROM. It's enough to root and do a few tweaks or install kernel or run root apps. Even on 7.1 the custom roms offer very little over stock to bother with them.
[Google Pixel XL Guides, News, & Discussion] snoprosledneck88:
So like I said I'm new to the pixel. What is the hot kernel? I know elemental is always a solid choice but I loved [MENTION=2682771]TheFL[/MENTION]ash kernel on my Nexus 6p. What are you guys running for some additional battery life?
[Google Pixel XL Guides, News, & Discussion] willyumlu:
using kirisakura right now https://xdaforums.com/pixel-xl/development/kernel-kirisakura-kernel-0-1-t3554330 dev is active and always updates every month
[Google Pixel XL Guides, News, & Discussion] ithehappy:
Most use the Elemental X. There was also Franco, but no Oreo compatibility yet.
[Google Pixel XL Guides, News, & Discussion] tdct12:
I think it has a lot to do with how smooth the software is by default and how much Android has evolved. We can now theme are phones without root on stock roms, use picture in picture, split screen apps. Battery life is good, bloat is minimal. I'm running out of reasons to install a rom, there really is no longer a bit performance jump. The only rom I'm really interested in is Paranoid Android when it's Oreo release drops. They offer some very cool features that makes it just worth the effort such as the PIE wheel.
[Google Pixel XL Guides, News, & Discussion] loeffler23:
[MENTION=4345642]snoprosledneck88[/MENTION] May I ask how you got a pixel for nothing? Been trying to get one for development/app development but don't feel like spending hundreds when I have a perfectly good phone right now.
[Google Pixel XL Guides, News, & Discussion] snoprosledneck88:
It was a replacement phone for a Nexus 6p that had a bad battery.
[Google Pixel XL Guides, News, & Discussion] harihacker:
For me, it has to do with how smooth the phone is out of the box and the evolution of Substratum to enable theming which completes my needs.
[Google Pixel XL Guides, News, & Discussion] snoprosledneck88:
That's true. If I was on a "stable build" I would root and use it. (I'm on the Android beta program) I know you can do it without root but you need to buy another app so for right now it's a no-go.
[Google Pixel XL Guides, News, & Discussion] veskostoev:
You can root 8.1 beta no problem.
[Google Pixel XL Guides, News, & Discussion] snoprosledneck88:
I know you can. Maybe a little lazy haha. How often does android release a new beta? This is my first time being on it, always have flashed roms.
[Google Pixel XL Guides, News, & Discussion] mostyle:
I gotta say I do miss the tons of options that come with custom roms.. Little things like the speed meter in the status bar, customizing the buttons, hardware volume keys to audio skip, etc.

Sure they aren't functional necessities but damn nice amenities once you get used to them. Does there exist something to add these kinds of features to 8.x?
[Google Pixel XL Guides, News, & Discussion] Nil253259:
Since Oreo release i don't flash Custom ROMs anymore. too much effort for me and i can spend that time on something productive ? .. I'm not missing any feature either. Skip playlist with volume button can be done with tasker, for data speed on status bar I'm using an app. For missing tiles in the extended notification panel, I'm using"tiles" app.

Right now on 8.1 beta. There will be another DP coming this month and then final launch in December I guess. Most stable DP1 I've even used so far
[Google Pixel XL Guides, News, & Discussion] dictionary:
Dp1 with root has been amazing. Incredible fluidity and insane battery. Zero complaints. Miss some small tweaks, and would love always on display, but we've come a long way from donut and eclair
[Google Pixel XL Guides, News, & Discussion] HACK3DANDR0ID:
I did a warranty exchange on my 32GB Verizon Pixel XL and they sent me a brand new 128GB Version. I booted it the 1st time with my TMO SIM and been happy ever since :):):) Bootloader UNLOCKED, Rooted, etc. There is however a lack of development compared to the Nexus 6, but flashing on the Pixel is like no other device. I'm new to the community and was confused as hell with the A Partion and B Partion flashing. Never ran into this before the Pixel, but im getting the hang of it...
[Google Pixel XL Guides, News, & Discussion] FUZER384:
When you say they sent you a Verizon PXL, how would you confirm that? Because there's ALOT of debate of what determines a phone having the ability to unlock a bootloader. In lots of instances people are getting Google phones on 7.1.2 without putting any sim card in and still seeing a bootloader that isn't unlockable. Like in my case. I hear it's a mixed bag rather you will get a Verizon or Google phone from Google.
[Google Pixel XL Guides, News, & Discussion] HACK3DANDR0ID:
My Pixel came with a Verizon SIM card.
[Google Pixel XL Guides, News, & Discussion] FUZER384:
Yeah I'm not sure that qualifies it
[Google Pixel XL Guides, News, & Discussion] HACK3DANDR0ID:
The purchase order also showed a (Verizon) unit being sent back and a (Verizon) being sent to me (For a 2nd time)...
[Google Pixel XL Guides, News, & Discussion] FUZER384:
I'm not sure but going thru all the pages in the two threads about Verizon bootloader there's ALOT of debate about this and I haven't heard of PO or sim being a qualifer
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
Not sure I would call it a debate. It's misinformation and/or confusion caused by Google incorrectly shipping phones and/or Google misentering the IMEI in their database.

It unlocks by phoning home to Google to see if the IMEI is in the database to be allowed to unlock. One guy was kind enough to packet capture his phone on first boot. It made a call to a previously unknown Google server and blammo the slider was free.

Google has made a lot of mistakes with this system. It is really bad over on the Pixel 2 forums. Boatloads of Google phones not entered in the database correctly...and not unlocking. Google is making good on it
[Google Pixel XL Guides, News, & Discussion] FUZER384:
Funny, when I RMA'd my first Verizon phone to Google and got it back and suggested the IMEI was the key I got shot down
[Google Pixel XL Guides, News, & Discussion] HikingMoose:
Snowpro buddy! Nice to see ya. Do you find it odd that Google apologized for breaking their USCC APNs, a couple builds ago, and say they're trying to fix it, yet the keep releasing builds with the same bad APNs? Especially when the 8.1 beta from last month has working APNs, yet the official builds still don't have data. I can never figure out the Google developers. They move backwards more often then they move forward.
[ZTE Axon 7 Questions & Answers] spriteboost:
I'm not sure why it happens but sometimes my phone what seems at random just decides to go to loud. I hate hearing the noises of phones idk they annoy me lol so i set it always to vibrate and like said before it goes to loud. It seems to do it when plugging in and just random times not sure I don't want the phone to decide when to go to loud especially if i'm in class or something.

this last part annoyances with the phone but love it overall may have to going back to my addiction with roming it lol. Vibrate when inputing things all the time and camera motor vibrating (think there may be a solution for that haven't seen it in a while tho so may be fixed on latest os rom, battery dieing sort of fast some days. that's it i love the phone otherwise I've gotten out of phones so its been perfect otherwise. thanks for anyones help
[ZTE Axon 7 Questions & Answers] William Guo:
[MENTION=4988729]spriteboost[/MENTION], which kind of ZTE phone are you have, A2017G or A2017U? Could you tell us your phone's IMEI?
[ZTE Axon 7 Questions & Answers] spriteboost:
I have the a2017u and yeah my imei I will not post that anywhere thank you very much don't need that cloned for someone else's uses.
[ZTE Axon 7 Questions & Answers] charliemarie:
Do you have any automatic rules set up in your sound profile?

settings -> sound & notification -> do not disturb -> rules

This wouldn't explain why the volume is switching on when you plug it in, but worth checking anyway
[LG K7 Questions & Answers] charsta:
Hello all,

I have this LG K7 X210 variant that belongs to my niece. Because the phone was quite slow and almost full their parents decided to factory reset it.

However now at the initial setup after the reset, it always asks for the previous Google Account that was on the phone. The problem is that they don't know/remember neither the email nor the password!

I tried to factory reset it as well by booting into recovery but the same results. The reset finishes without errors however it still needs a Google Account that was previously used in the phone!

How can I bypass that? Is there any way to flash again the stock rom? I can't find anything for this variant online. :confused:

It's been over a month that phone is in this state!

Thank you!
[LG K7 Questions & Answers] NonStickAtom785:
Hey your phone FRP Locked by Google. You can bypass it by watching some tutorials or by using LG Up to restore again. There's a guy with a thread called LG Aristo 2 Tutorials by TeckNight and he has all the stock firmware and links to recover your phone.
[Google Pixel XL Questions & Answers] Scottay5150:
I am using WIn10 HP laptop.

I am getting the errors below. Are there other Android ABD's out there that can help me install 8.0 and soon 8.1?

Preparing to install archives

Downloading Android SDK Platform-tools, revision 26.0.2

Download finished with wrong checksum. Expected 98832431e339c82be1fe910a733a3782071200fd, got aa3ef6f18eff4b8f12dbdf980647a6ce6c2ebe8c.

Downloading Android SDK Build-tools, revision 27

Installing Android SDK Build-tools, revision 27

Installed Android SDK Build-tools, revision 27

Downloading SDK Platform Android 8.1.0, API 27, revision 1

Installing SDK Platform Android 8.1.0, API 27, revision 1

Installed SDK Platform Android 8.1.0, API 27, revision 1

Downloading Google USB Driver, revision 11

Installing Google USB Driver, revision 11

Installed Google USB Driver, revision 11

Skipping 'Android SDK Tools, revision 25.2.5'; it depends on 'Android SDK Platform-tools, revision 26.0.2' which was not installed.

Done. 3 packages installed.

Done loading packages.

Deleting 'Android SDK Tools, revision 24.4.1' (C:\Users\scott\AppData\Local\Android\android-sdk\tools)

Done

Done loading packages.

Preparing to install archives

Downloading Android SDK Platform-tools, revision 26.0.2

Download finished with wrong checksum. Expected 98832431e339c82be1fe910a733a3782071200fd, got aa3ef6f18eff4b8f12dbdf980647a6ce6c2ebe8c.

Skipping 'Android SDK Tools, revision 25.2.5'; it depends on 'Android SDK Platform-tools, revision 26.0.2' which was not installed.

Done. Nothing was installed.

Preparing to install archives

Downloading Android SDK Platform-tools, revision 26.0.2

Download interrupted: Connection reset

Skipping 'Android SDK Tools, revision 25.2.5'; it depends on 'Android SDK Platform-tools, revision 26.0.2' which was not installed.

Done. Nothing was installed.
[Google Pixel XL Questions & Answers] TonikJDK:
Grab just the platform tools.

https://developer.android.com/studio/releases/platform-tools.html
[Essential Phone Questions & Answers] Zorachus:
First off I am not criticizing the amazing XDA developers here, and all the people that help make root and ROM's happen.

This is aimed at Essential the company themselves

I was under the impression the Essential Phone was sort of like a Pixel, or Nexus, or OnePlus type of phone. Meaning running a near stock Android OS, an unlocked device, easily rooted. For example when a new OnePlus phone is released, root is out super fast. But the reason the Essential Phone has not been rooted yet is because of Essential holding back the factory images on us still. I guess I have to ask why would Essential do this ? I thought they touted this phone as a open platform, very similar in idea to the old Nexus line ?

The Essential Phone has been out 2 months now, and the important files for rooting still have not been officially released to the public yet ? What's up with Essential holding back so long ?
[Essential Phone Questions & Answers] Z-Fire821:
https://ibb.co/mgaVcb Mine ist rooted :)
[Essential Phone Questions & Answers] gk1984:
Last I read was the boot image that was pulled didn't enable root with magisk and hadn't seen anything more from it. Did you have to do anything specifically?
[Essential Phone Questions & Answers] Paddybecks87:
Interedasting.

It'd be great if you could provide further proof/instructions.

Thanks a bunch.
[Essential Phone Questions & Answers] kchino:
There was a thread about someone working on LOS earlier this week but now I don't see it. Can't remember the user's name but he said that he had TWRP (no touchscreen though) working on the ROM, and posted some screenies of it booted and invited anyone who wanted to develop to his Discord. The same person was over on the /essential thread too on reddit too but now I don't see that thread either.

The Essential staff did an AMA over there yesterday too but noone asked about releasing the source code to my knowledge. I'm not sure what's going on. They'd sell more phones if people knew they are ROM friendly.

*Found the thread here:

https://xdaforums.com/essential-phone/help/bootloader-root-t3695583
[Essential Phone Questions & Answers] Malacant:
Pretty sure the staff that did the AMA was just the design staff, not software staff. As soon as the files are released it will take about a day I bet for root. I remember seeing a thread on reddit that you are referring to as well. I think the people who can root it won't until the files are released. One **** up and they have a very expensive brick.
[Essential Phone Questions & Answers] Zorachus:
Thanks for the replies. So any idea as to when this source code image files will get released from Essential ? What's their holdup ?
[Essential Phone Questions & Answers] kchino:
Agreed, dicey proposition with no factory images.
[Essential Phone Questions & Answers] Tikerz:
We have devs working on it. Root has been achieved and there's a TWRP build but the touchscreen doesn't work you have to use a mouse to navigate. Also, there's no factory images yet to go back to stock in case of a problem. Once they iron out the issues I'm sure someone will release a guide.
[Essential Phone Questions & Answers] Zorachus:
Currently on the Nexus 6P, that's getting bad. I really want the Essential phone, but only if root comes out for sure, also ROM's would be great.

Otherwise I may just wait for the OnePlus 5T announcement, and if it's $500 go that route instead. At least the 5T will have good development
[Essential Phone Questions & Answers] shooterlgk:
Man how did u root?? I really wanna root
[Essential Phone Questions & Answers] Z-Fire821:
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
[Essential Phone Questions & Answers] drocny87:
Can you provide the file for TWRP and boot img?
[Essential Phone Questions & Answers] Z-Fire821:
Just join the Discord Server and load it from there.
[Essential Phone Questions & Answers] drocny87:
Thanks

---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------

What's the link to it?
[Essential Phone Questions & Answers] bmg1001:
ROOT

Guys, if you truly, truly want to root your device, follow these steps. Just remember, I am not responsible if you end up bricking your device (and neither are the main developers currently working on TWRP and Lineage). YOU ARE RESPONSIBLE FOR WHAT YOU DO ON YOUR OWN DEVICE! (also this probably voids warranty btw)

THESE INSTRUCTIONS ARE FOR NMJ20D.

Now, one more thing.

Remember, this TWRP build is very much in alpha stages and there are some major bugs with it, including no touch support and no crypto.

Also, when I rooted, I had to use my USB OTG Mouse in order to maneuver around TWRP, but with this method, hopefully anyone can do it, without the mouse. The boot.img I will provide is the NMJ20D boot.img with the patches that Magisk puts in when you install it, so it's not exactly stock. Also, you might need to factory reset your device via the stock recovery (and make sure not to boot it back up until after you flash Magisk) just in case, since TWRP is buggy with crypto atm.

You can find a dump of NMJ20D here, in case you need to fix a bootloop (due to a bad Substratum theme, etc...) -- (you'll likely need only boot_a.img and system_a.img (within the system_a.zip).

If you wish to return to stock in order to accept OTAs, feel free to flash the unofficial factory images here and, should OTAs still fail, you may be required to wipe your data, which can be done via "fastboot -w". (Side Note: I believe the script included within the unofficial factory images also flashes the firmware to both partitions, so if your fingerprint sensor is seemingly absent or not working, this might actually fix it, as it has for some custom ROMs on the Essential.

Anyways, lets get started!

Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course, your bootloader must be unlocked.

1. Reboot your Essential into fastboot mode. Once in fastboot mode, flash TWRP via

fastboot flash boot twrp-mata.img

2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type

adb shell twrp sideload

and then

adb sideload magisk.zip

3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command

fastboot flash boot boot_a.img

4. Now reboot! You should now have root and stuff via Magisk!
[Essential Phone Questions & Answers] Amd4life:
Appreciate the root guide, guess I can pick one of these up now to play around with. Awesome!!
[Essential Phone Questions & Answers] shooterlgk:
[

Anyways, lets get started!

Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course,

2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type and then

3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command

4. Now reboot! You should now have root and stuff via Magisk![/QUOTE]

I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..
[Essential Phone Questions & Answers] bmg1001:
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..[/QUOTE]

What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?
[Essential Phone Questions & Answers] shooterlgk:
What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?[/QUOTE]

I should of took a picture cuz I can't remember but it does give me an error tho ..I'm gonna retry when I get home from work but I literally sat there for almost 3 hours attempting to root to no success
[Essential Phone Questions & Answers] fbriolini:
I followed your instructions, and it worked like a charm. Thank you!

F.
[Essential Phone Questions & Answers] artiemon:
I was going to try this but am wondering why your are flashing twrp-mata.img to boot rather than recovery.
[Essential Phone Questions & Answers] DaveHTC200:
This was the way it was on the Pixel XL. Likely due to changes with A/B slots etc
[Essential Phone Questions & Answers] tribulationwolf:
not sure what i am doing wrong here but i know i screwed up somewhere cuz the very first command fails to transfer with an unknown error. Does it matter that I am using Minimal ADB and FastBoot to input my fastboot and adb commands instead of the full android sdk? My phone is unlocked and usb debugging is turned on but when i input the first command it says the following:

"target reported max download size of 536870912 bytes , sending 'boot_a' <23176 kb>... , FAILED <data transfer failure <Unknown error>> , Finished. total time: 30.108s
[Essential Phone Questions & Answers] bmg1001:
I used Minimal ADB and Fastboot myself, and it worked fine, so that shouldn't be the problem. From the error you received, I'm assuming that the image is having issues being transferred to the phone, not being flashed. Try redownloading the image or try "fastboot flash boot_a twrp-mata.img" It could also be the ADB and Fastboot drivers you have installed. I also heard it can be caused by the USB port. Try switching the USB Port and/or cable?
[Essential Phone Questions & Answers] mrcooter:
Would this process for root hinder the sideloading of future official updates? Just wanted to check considering we don't have full source yet..
[Essential Phone Questions & Answers] tribulationwolf:
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------

[/COLOR]

possible it is the drivers. I am using the google drivers for adb testing interface but for some reason it is listed under android device and not adb interface in my device manager. I tried uninstalling and reinstalling the drivers but it does the same thing? could this be the issue? If so, how would I fix it since reinstalling drivers didn't help
[Essential Phone Questions & Answers] bmg1001:
My drivers show up under "Android Device" as "Android ADB Interface" while in Fastboot. I used these drivers: https://xdaforums.com/essential-phone/how-to/unofficial-usb-drivers-essential-ph-1-t3678231
[Essential Phone Questions & Answers] tribulationwolf:
I got it to work. It was the driver i was using. Switched from Google ADB Testing Interface driver to

Composite ADB Interface driver

and everything worked like a charm.

---------- Post added at 09:23 PM ---------- Previous post was at 09:21 PM ----------

While I'm here is there a way to get rid of that annoying "Can't check for corruption" screen that comes up once the bootloader is unlocked?
[Essential Phone Questions & Answers] sakerhetz:
small problem overhere twrp mata works fine... but when i want to install magisk from sideload error message is "cannot read magisk.zip".

Update ADB gives message "No devices or Emulators found".
[Essential Phone Questions & Answers] drocny87:
How do you take an OTA after rooting with this method?
[Essential Phone Questions & Answers] chiefkrikor:
+1
[Essential Phone Questions & Answers] bmg1001:
You should be able to take OTAs again by flashing the stock boot and system images linked in the guide and then wiping data either via fastboot or stock recovery.
[Essential Phone Questions & Answers] prgopala:
Quick question, rooting using this method allows you to still use Android pay ?
[Essential Phone Questions & Answers] drocny87:
Thanks for the info. Wouldn't that unroot?
[Essential Phone Questions & Answers] bmg1001:
Yes, its Magisk, it has MagiskHide which allows SafetyNet to pass.

---------- Post added at 08:25 PM ---------- Previous post was at 08:23 PM ----------

Yes. I'm not sure there is a device out there that can take OTAs while maintaining root, but for this one, you'd have to re-root after the OTA, but I'd need to make an updated boot.img too.
[Essential Phone Questions & Answers] drocny87:
Thank you for the info. I appreciate the help