[GUIDE] Unlock/Flash/Root for the Pixel 2 XL (taimen)

Search This thread

simplepinoi177

Senior Member
Apr 29, 2012
647
316
Bay Area, California
Magisk should be fine with latest. You could save a lot of trouble with Deuces script.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Thanks! But that appears to be a script to fix bootloops?
My issue is I'm not able to boot or run the patched boot.img from magisk, I don't mind doing things manually actually prefer that but for sure cool with other methods

Any ideas why the patched kernel won't boot?

While Deuce's script does help fix bootloops, I believe what @srqrob was meaning for the advice is that you mentioned that you manually fastboot commanded each and all the image files individually; which is basically what Deuce's script does -- individually and manually fastboot flashes all the image files. So, to save yourself a lot of time and typing/cutting/pasting, this is a good suggestion and what I/srqrob suggests for people who wish for it to not be flashed all in bulk...

As per your original issue, you most likely are having issues because the method you are choosing is one of the easiest to get messed up (manually patching the boot image [.img]) -- whether by the person or simply whatever bugs/glitches are in the coding -- and especially since you are installing TWRP, you would be better served flashing Magisk/obtaining root using TWRP to "Install" Magisk by its installation .zip file. In this way, all the "flashing" and "patching" will be done on a code level where everything that needs to be mounted or "called" upon will be, obtaining proper permissions, and re-inserted back into the boot partition correctly versus a virtual cut-and-paste that is done outside of use of the installation file.

See if this works better for you (I'm willing to bet that it will), but if you still have issues afterwards, some things to consider; always install/flash Magisk as the LAST step -- install your custom kernel and everything else before Magisk as, even though the output of installing certain kernels claims that they can detect modified boot partitions and not mess things up, most of the time, the others don't "play" well with Magisk and it's just best to leave Magisk to have the "final say" as it were. Another thing to consider is to be sure that you are using the most latest up-to-date version of Magisk -- and even consider the "canary" beta versions, if need be -- as well as TWRP (and even the latest r29.0.1 platform tools) and whatever custom kernel you are considering...you'd be surprised how badly these things go and how much troubleshooting just to find that it's because one component or other isn't using the latest version...

Good luck to you and hope this helps...
 
  • Like
Reactions: demkantor

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,752
mpls
Good luck to you and hope this helps...


Thanks for that! I had tried flashing via recovery after flashing via bootloader didn't work, tried both methods twice and let it sit how 20min + each time with it not getting past the splash screen
I'm running the latest as far as I can tell, all images from latest (July I believe) from Android factory images (these work fine without root) and I believe twrp and magisk are both the latest, I'll attack a screenshot of magisk, want to say twrp was like 3.0.0 but I'll have to reboot and check

Original kernel always works fine, so after getting stuck just a quick flash of that and I'm up and running so not a lot of work needed for scripts but I get it

I just prefer manual, I'm old, scripts in Android at times haven't played well with me but I haven't done coding in years so don't know a ton of what's new

I'll retry everything again of course and see what's up, oh I guess I'm patching the factory boot.img, am I to be using a custom kernel? I was under the impression that factory one would work fine once patchex
 

Attachments

  • Screenshot_20190802-171244.png
    Screenshot_20190802-171244.png
    138.2 KB · Views: 108

CyberpodS2

Senior Member
Mar 27, 2012
2,809
1,236
NE Pennsylvania Boonies
Thanks! But that appears to be a script to fix bootloops?
My issue is I'm not able to boot or run the patched boot.img from magisk, I don't mind doing things manually actually prefer that but for sure cool with other methods

Any ideas why the patched kernel won't boot?

Why are you using the patched img method instead of just flashing the zip in TWRP?? Pretty much everyone gave up the patching over a year ago once the zips were created. It's pretty much a mindless install at this stage of the game.

Sent from my Pixel 2 XL using XDA Labs
 

demkantor

Inactive Recognized Contributor
Nov 10, 2011
6,858
3,752
mpls
Why are you using the patched img method instead of just flashing the zip in TWRP?? Pretty much everyone gave up the patching over a year ago once the zips were created. It's pretty much a mindless install at this stage of the game.

Well I tried both methods, originally tried flashing the patched image via fastboot, didn't work, tried via recovery, same issue, went back and tried both ways again
Each time I could recovery fine flashing factory image.img

A year ago would have been the last time I was here, I've been just running Android 8 until my camera decided to crap out on me, Google covered it which was great, but the new phone they gave me had updated software. Not a big deal, I like this, but no issues rooting prior where now I do
So not sure if it's android9 issue or latest magisk, hard to say as I only had a bit of time to dink about earlier

I'll try via recovery tonight again and hopefully that will work
 

Badger50

Forum Moderator
Staff member
Feb 27, 2011
11,764
11,385
61
Kansas City
Samsung Galaxy Tab 7.7
Thanks for that! I had tried flashing via recovery after flashing via bootloader didn't work, tried both methods twice and let it sit how 20min + each time with it not getting past the splash screen
I'm running the latest as far as I can tell, all images from latest (July I believe) from Android factory images (these work fine without root) and I believe twrp and magisk are both the latest, I'll attack a screenshot of magisk, want to say twrp was like 3.0.0 but I'll have to reboot and check

Original kernel always works fine, so after getting stuck just a quick flash of that and I'm up and running so not a lot of work needed for scripts but I get it

I just prefer manual, I'm old, scripts in Android at times haven't played well with me but I haven't done coding in years so don't know a ton of what's new

I'll retry everything again of course and see what's up, oh I guess I'm patching the factory boot.img, am I to be using a custom kernel? I was under the impression that factory one would work fine once patchex

Had a similar problem for the May and June updates that forced me to use magisk 18.1, but then was able to update magisk to 19.3 via the magisk app after the July update. So, I would try flashing 18.1 via twrp, let it boot up, hopefully with root, then try updating to 19.3 via the app. Best of luck to ya :good::cool:
 
Last edited:
  • Like
Reactions: demkantor

simplepinoi177

Senior Member
Apr 29, 2012
647
316
Bay Area, California
Thanks for that! I had tried flashing via recovery after flashing via bootloader didn't work, tried both methods twice and let it sit how 20min + each time with it not getting past the splash screen
I'm running the latest as far as I can tell, all images from latest (July I believe) from Android factory images (these work fine without root) and I believe twrp and magisk are both the latest, I'll attack a screenshot of magisk, want to say twrp was like 3.0.0 but I'll have to reboot and check

Original kernel always works fine, so after getting stuck just a quick flash of that and I'm up and running so not a lot of work needed for scripts but I get it

I just prefer manual, I'm old, scripts in Android at times haven't played well with me but I haven't done coding in years so don't know a ton of what's new

I'll retry everything again of course and see what's up, oh I guess I'm patching the factory boot.img, am I to be using a custom kernel? I was under the impression that factory one would work fine once patchex
NOTE: After I lost my initial response by accident, I clicked reply and walked away and only hours later (now) find that it ended in an error, so this is my original response, even though I see that there are additional replies...


Hmmmm....some output/logs would be helpful at this point (particularly the output when installing Magisk using the .zip file)...

But what I'm thinking is that you might be best served by resetting the boot partition. After all the flashing and re-flashing you've been doing, I'm concerned you might have a rather "buggy" boot partition and/or kernel. You could always do this manually by extracting the stock boot image and fastboot flash it, but you'd most likely be better served by merely running the flash-all on a Full Factory image to make sure everything is set properly (of course with "-w" removed).

After doing this, I suggest you keep it simple and direct; boot into TWRP (install it if you wish, but be sure to only use the installation .zip or "Advance" install it by pointing to a TWRP image. After, reboot to the bootloader before booting back into TWRP. Then, if you wish for a custom kernel, install that at this point. Afterwards, reboot to the bootloader then boot back into TWRP. On this (third) time, "Install" Magisk by its .zip file. Again, reboot to bootloader before booting into the system -- Apparently it is good practice and may resolve some issues by rebooting to the bootloader after each and every flash/install.
If anything, be sure to copy the output/logs so you can put it up here if need be...

Good luck!
 
  • Like
Reactions: demkantor

CyberpodS2

Senior Member
Mar 27, 2012
2,809
1,236
NE Pennsylvania Boonies
Had a similar problem for the May and June updates that forced me to use magisk 18.1, but then was able to update magisk to 19.1 via the magisk app after the July update. So, I would try flashing 18.1 via twrp, let it boot up, hopefully with root, then try updating to 19.3 via the app. Best of luck to ya :good::cool:

Hey bro where you been hiding? Lol

Sent from my Pixel 2 XL using XDA Labs
 

post-mortem

Senior Member
Oct 4, 2012
2,137
763
Thanks for that! I had tried flashing via recovery after flashing via bootloader didn't work, tried both methods twice and let it sit how 20min + each time with it not getting past the splash screen
I'm running the latest as far as I can tell, all images from latest (July I believe) from Android factory images (these work fine without root) and I believe twrp and magisk are both the latest, I'll attack a screenshot of magisk, want to say twrp was like 3.0.0 but I'll have to reboot and check...

Latest TWRP for taimen is 3.3.0-0.


... Another thing to consider is to be sure that you are using the most latest up-to-date version of Magisk -- and even consider the "canary" beta versions, if need be -- as well as TWRP (and even the latest r29.0.1 platform tools) ...

Latest platform-tools is 29.0.2.
 

Badger50

Forum Moderator
Staff member
Feb 27, 2011
11,764
11,385
61
Kansas City
Samsung Galaxy Tab 7.7
Hey bro where you been hiding? Lol

Hey bud. Life just got busy since the end of March. My mom passed away, so I had to do several road trips between KC and St. Louis to settle estate stuff. And now we babysit our 10 month old grandson 3 days a week. Not to mention that by the time I ever get on XDA anymore, you and all the others have got all the P2XL stuff handled :laugh::good:
 

Az Biker

Senior Moderator / RC- RT Committee / Semper Salty
Staff member
Hey bud. Life just got busy since the end of March. My mom passed away, so I had to do several road trips between KC and St. Louis to settle estate stuff. And now we babysit our 10 month old grandson 3 days a week. Not to mention that by the time I ever get on XDA anymore, you and all the others have got all the P2XL stuff handled :laugh::good:

Sorry to hear about your mom :crying:

Glad you get a little more grandkid time (mine live hours away)!

Good to see you in the threads again!
 
  • Like
Reactions: Badger50

CyberpodS2

Senior Member
Mar 27, 2012
2,809
1,236
NE Pennsylvania Boonies
Hey bud. Life just got busy since the end of March. My mom passed away, so I had to do several road trips between KC and St. Louis to settle estate stuff. And now we babysit our 10 month old grandson 3 days a week. Not to mention that by the time I ever get on XDA anymore, you and all the others have got all the P2XL stuff handled :laugh::good:

Hey bro sorry for your loss. We are getting to that age where the life stuff we dread is happening. As for Grand kids, I'm a new grand dad as of this week so looking forward to that chapter. At the end of the day, I'm very happy to see you know where you are needed first! Stay cool man.

Sent from my Pixel 2 XL using XDA Labs
 

Badger50

Forum Moderator
Staff member
Feb 27, 2011
11,764
11,385
61
Kansas City
Samsung Galaxy Tab 7.7
Hey bro sorry for your loss. We are getting to that age where the life stuff we dread is happening. As for Grand kids, I'm a new grand dad as of this week so looking forward to that chapter. At the end of the day, I'm very happy to see you know where you are needed first! Stay cool man.

Thank you brother! Appreciate the kind words. And many Congrats on your new grandbaby!! It's a blast! Tiring as all get out, but definitely a blast! :good::laugh:
 

johnlgalt

Senior Member
Nov 16, 2009
1,394
412
50
Atlanta
androidforums.com
Hey bud. Life just got busy since the end of March. My mom passed away, so I had to do several road trips between KC and St. Louis to settle estate stuff. And now we babysit our 10 month old grandson 3 days a week. Not to mention that by the time I ever get on XDA anymore, you and all the others have got all the P2XL stuff handled :laugh::good:

Sorry for your loss, man.
 
  • Like
Reactions: Badger50

Az Biker

Senior Moderator / RC- RT Committee / Semper Salty
Staff member
(Yeah, I'm spamming the threads lol - but this is the last one, I promise!)

Q ßeta 6 going live right now.

There was a day when I was all over these the second they came out.

I must be getting old, or lazy because now I'm perfectly content to wait for Google to drop the next OS before flashing it :p
 

Az Biker

Senior Moderator / RC- RT Committee / Semper Salty
Staff member
Lol - I'm still a crackflasher at heart. Plus, I beta test a lot of stuff, not just Android, but also on my desktops and laptops.

I enjoy living on the edge.

Sir, you may have my spot on the edge :p

After staring over that edge, looking at the bottom of the Android Grand Canyon for so long, I'm content to wait for the documentary now :D

Kudos to you who still man the edge, and chew through the betas!

We lazy folks salute you! :good:
 

bluey45

Senior Member
Jun 29, 2011
121
55
Sir, you may have my spot on the edge :p

After staring over that edge, looking at the bottom of the Android Grand Canyon for so long, I'm content to wait for the documentary now :D

Kudos to you who still man the edge, and chew through the betas!

We lazy folks salute you! :good:
Won't be long for you to wait for final Q haha
 

johnlgalt

Senior Member
Nov 16, 2009
1,394
412
50
Atlanta
androidforums.com
I'll say this - Q has brought (and taken away) more features than I can count - but tonight I was able to pin live scores from various NFL pre-season games as well as a baseball game. That and Dark mode (which I've been using since they gave it took it away gave it back sort of but not fully) really make this a nice overall OS.

Backend stuff, too, like more granular control over permissions, including location permissions only while the app is running, and a lot more stuff in DevOps - I'm digging this Q thing.

Now to wait for it to go final, and then to buy a new phone....
 

Top Liked Posts

  • There are no posts matching your filters.
  • 203
    Introduction

    Hello everyone, this is a guide to assist you with customizing your Pixel 2 XL! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to root. Please feel free to ask any questions if you need clarification. Enjoy!

    This information has been distilled from Google's official factory image site and the Magisk thread.


    Installing fastboot and adb

    Thankfully, Google has provided just adb, fastboot, and systrace as a simple zip file, making this process super easy. You MUST be on at LEAST 26.0.2 for the commands in this guide to work. When in doubt, grab the latest copy and install them using the following instructions.


    Windows:

    1. Unzip the folder somewhere on your hard drive.
    2. Go to the folder containing the adb and fastboot files and type "cmd" in the path bar at the top.
    3. A command prompt should open with the current folder showing on the prompt.
    4. Type the following commands:
      Code:
      adb --version
      fastboot --version
      You should see some information appear. If that is the case, you were successful!

    Mac/Linux:

    1. Unzip the folder somewhere on your hard drive.
    2. Navigate to that folder with your terminal.
    3. Run the following commands:
      Code:
      sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
      sudo mkdir -p /usr/local/lib64
      sudo install lib64/libc++.so /usr/local/lib64
    4. Type the following commands:
      Code:
      adb --version
      fastboot --version
      You should see the version information, along with telling you they are installed to /usr/local/bin. If so, you were successful!


    Unlocking the bootloader

    WARNING: This WILL wipe your entire phone. Please make copies or backups of any important data. This can also go wrong rendering your device inoperable. Proceed with caution.

    1. On your phone, open Settings, navigate to "System" then "About phone", and tap on the build number 7 times.
    2. Go one menu up, click on "Developer options", and turn on USB debugging and OEM unlocking.
    3. In your terminal, type the following command:
      Code:
      adb reboot bootloader
    4. Next, decide if you want to do a standard unlock or critical unlock. A critical unlock allows you to directly flash bootloader files, otherwise you will get an error when you try to do so.
    5. Depending on what you decided in the previous step, run the following commands:
      Code:
      fastboot flashing unlock
      (OPTIONAL)
      Code:
      fastboot flashing unlock_critical
    6. Follow the prompts on your device then reboot!


    Flashing factory images

    NOTE #1: If you have mounted /system as rw at any point (like in TWRP), you must upgrade using the factory image method. OTAs will fail because they cannot verify the integrity of the disk since its verity data has been changed.

    NOTE #2: Flashing the factory images requires an unlocked bootloader. Flashing the OTA zips does not (but if anything goes wrong, you may not be able to recover without an RMA).

    Updating to a new release (factory image):

    1. Download the latest factory image from Google's website.
    2. Reboot into the bootloader:
      Code:
      adb reboot bootloader
    3. Unzip the factory image.
    4. Inside you will see a bootloader image, a radio image, an image zip file, and a couple of flash scripts.
    5. If you are on Windows, open the "flash-all.bat" file in a text editor. If you are on Mac or Linux, open the "flash-all.sh" instead.
    6. Remove the "-w" flag before the fastboot command towards the end of the file. This will prevent fastboot from formatting your device.
    7. Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
      Windows:
      Code:
      flash-all
      Mac/Linux:
      Code:
      ./flash-all.sh
    8. Reboot once it is finished!
    Updating to a new release (OTA zip):

    1. Download the latest OTA zip from Google's website
    2. Reboot into recovery:
      Code:
      adb reboot recovery
    3. Hold down the power button and push volume up
    4. Select "Apply update from ADB"
    5. Run the following command from the folder containing the OTA zip:
      Code:
      adb sideload <zip_name>.zip
    6. Reboot once it is finished!
    Clean flashing a factory image (wipe everything):

    1. Download the latest factory image from Google's website
    2. Reboot into the bootloader:
      Code:
      adb reboot bootloader
    3. Unzip the factory image.
    4. Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
      Windows:
      Code:
      flash-all
      Mac/Linux:
      Code:
      ./flash-all.sh
    5. Reboot once it is finished!


    Rooting with Magisk

    NOTE #4: This section assumes you are not going to install TWRP. If you are, skip to the next section and just flash the latest Magisk zip after installing TWRP.

    1. Download the Magisk zip from the official thread and install the manager from the zip.
    2. Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
      Code:
      adb push <path_to_file> /sdcard/Download
    3. Open Magisk Manager and click the Install button.
    4. Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
    5. Select the boot image you want to patch and let Magisk Manager patch it.
    6. Pull it off your device:
      Code:
      adb pull /sdcard/MagiskManager/patched_boot.img
    7. Reboot into the bootloader:
      Code:
      adb reboot bootloader
    8. Flash the boot image and reboot.
      Code:
      fastboot flash boot patched_boot.img
      fastboot reboot
    9. Open Magisk Manager and you should be rooted!


    Installing TWRP

    NOTE #5: If you just want to temporarily boot TWRP to flash Magisk and your custom kernel, you can just skip flashing the installer zip in this process.

    NOTE #6: TWRP can be unstable at times given the way that security has been set up on this device (lack of decryption, failing to boot, etc).

    • Download both the TWRP image and zip installer from the official site.
    • Temporarily boot the TWRP image.
      Code:
      fastboot boot <path_to_twrp_image>
    • Flash the TWRP installer zip.
    • Reinstall Magisk and your custom kernel if you had them.
    • Reboot and profit!


    Common issues

    • Outdated fastboot/adb: This device requires the latest fastboot and adb binaries to work properly. A lot of common quick adb/fastboot installation guides link to installers that are old. Please manually install the latest using the information at the beginning of the thread!
    • Using a USB-3.0 or USB-C port: Some newer USB ports do not work with fastboot. Issues manifest as weird errors during a flash. Use a different USB cable/port.


    Closing statements

    If there are any procedures you would like to see added (like flashing a custom kernel or booting TWRP), I am happy to add them if requested. Also, when requesting help, please be as specific as possible where you get confused. I want this guide to be clear as possible.
    43
    Upgrade to 8.1, TWRP, Magisk, and Cust Kernel (easy steps)

    After running through a bunch of threads, this is how I just upgraded to 8.1 with no issues,and all the steps and links in one post :D Everything works.

    My Previous Setup:
    Bootloader (unlocked and critical_unlocked) (SEE OP FOR UNLOCKING BOOTLOADER INSTRUCTIONS)
    Nov 8.0 Google factory image
    Magisk 14.6
    TWRP 3.2.1.0

    prep work:
    -in developer option make sure OEM unlocking is ON
    -in developer options make sure USB Debugging is ON
    -have the latest SDK toolkit (download in OP)
    -have a 2.0 USB in case your 3.0 USB doesn't work properly
    -Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
    -make sure all the files you are going to fastboot are located IN the (platform tools folder that contains the fastboot application)

    * * * until TWRP fixes the security issue, REMOVE ALL SECURITY BEFORE USING TWRP, reactivate security after rebooting * * *

    *download Latest Google Taimen factory image
    follow Updating to a new release (factory image): in OP (DON'T perform flash-all yet, do that later)
    * put TWRP 3.2.1-2 IMG file IN the (platform tools folder that contains the fastboot application), for flashing in fastboot
    * put TWRP 3.2.1-2 ZIP in sdcard, for istalling in TWRP
    * put Flash's Cust 8.1.0 kernel 8.1 ZIP in sdcard for installing in TWRP *OPTIONAL*
    * put (Magisk latest version) in sdcard for installing in TWRP... Magisk Manager is built into latest Magisk version

    ***If you're planning on wiping your entire device (leaving the -w intact), put all the "sdcard files" on your PC, after first boot with fresh, factory image, use your favorite root explorer app and add a folder within the sdcard folder (I name mine TO BE FLASHED) and move all the 'sdcard files' files from your PC to here for flashing in TWRP ***

    Verify you're connected to PC and Fastboot:

    Open a COMMAND PROMPT (type CMD in the address bar) from the same platform tools folder on your PC where the fastboot application is located, and unzipped factory image files (including flash-all.bat) are located, do the following:

    type- fastboot devices (should see a serial number, this means you're good)

    type- flash-all (this flashes Latest Google Taimen factory image), let it do its thing... (removing the -w [see "updating a new release" in PREP above] stops this from wiping your phone, be sure to SAVE the file after removing the -w... leaving the -w in flash-all.bat, wipes entire device)

    -IF TWRP is NOT already installed:
    Boot into TWRP using fastboot
    (use TWRP IMG file placed in platform tools folder)
    fastboot boot <twrp filename.img >

    Permanently install TWRP OR to update latest TWRP .ZIP: ( Or SKIP this step if you do NOT want TWRP perm installed)
    flash TWRP zip
    (from within TWRP choose INSTALL and find the TWRP.ZIP file placed on your sdcard)

    reboot to TWRP
    (deselect install TWRP app, reboot back into TWRP)

    flash Flash kernel via TWRP
    (placed in sdcard, INSTALL in TWRP, be sure to use the ZIP version, if you use the IMG version you have to reinstall TWRP zip AFTER installing the kernel)

    flash Magisk zip via TWRP
    (placed in sdcard, and it will automatically install Magisk Manager)

    NOTE: Once Magisk is installed, install new versions by clicking INSTALL within Magisk Manager, use "DIRECT" method (for latest version switch channel in manager to BETA)

    reboot system
    profit!

    After reboot:

    If you get stuck at "G" screen at boot up, long press power button / hard reboot, should boot normal.

    When you see this message on boot up "The bootloader is unlocked and software integrity cannot be guaranteed..........." it is normal an has no effect on your device.

    SafetyNet PASSES
    15
    The two most tiring discussions to me are:

    1. Which or all of the unlock commands should I use?

    and

    2. How can I appease my ridiculous, pointless, almost hospital admittance worthy ocd of the absolutely insignificant vendor error pop-up message at boot that pops up only at reboot? because it causes me such distress that I will keep asking and discussing it ad nauseam since it's the most significant issue on our device right now. Please help


    1. Just run them all, in any order, fastboot will tell you if you need to run them in a certain order. And yes your data will be wiped, get over it and act like an adult.

    And

    2. stay on stock, please for the love of the android gods just please. I spend 5 hours trying to fix why sepolicy for taimen causes a kernel panic when trying to boot a custom rom. I get overcome with joy when I see the pop up because I know ive booted the rom. You popup-fear mongering folks offend me.

    Just I'm mostly kinda saying this in a light hearted, jestful manner, except for number 2.

    But seriously run all the unlock commands, Just unlock, unlock the crap out of it.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone