Database Users

[prequisite] Anyone wanting Moto G XT1031 on Lollipop

K guys besides bootloader being LP ready here goes your solution(s)
after this any 5.0 or 5.1 [non gpe] Rom is doable
Anything Else, Lemme know ..
*twrp should be used first, Til the Stock 5.02 laid out in linked thread is Established..
Then whichever recovery can be used to replace it if you want instead
PLUS I dont remember if PhilZ has sideload enabled or only twrp , plz check before proceeding ,, if you intend on doing the full deal. And prefer cmw based.
-Here is a sideload thread and you WILL be doing it from recovery http://forum.xda-developers.com/showthread.php?t=2318497
Just rename the zip to the one stock debloated after all else formats + script last etc
* remember you must use fastboot devices command to make sure device is shown initially before loading sideload not adb devices & no need full sdk either way onlyminimal adb 1.4.2
and/or Moto-Gtools (moto drivers from it)
It is really good to setup your motoG with stock 5.0 Lollipop first anyways if coming from Kit Kat not gpe or anything

The above was mainly for anyone having problems getting lollipop update on xt1028/xt1031 CDMA Moto G 'Falcon'
*This does not include instructions for loading a 41.18/41.19 Bootloader onto your phone your are on your own there if you need to mine was included and factory unlocked
**SEE NOTE AFTER STEP 3**
1.) Move/copy ALL of your info you have on your phone off of it to your pc which means if you have a zero folder visible use a root file manager and move those to the main one too the one seeable by your pc
*you can make a folder called backup 2015 or something,include your titanium backups pics music notes etc if you want also your rom backup(s) you had saved
2.) Delete that zero folder from within twrp
3.) Get your files ready on your pc which are adb & The moto driver pack I have included both here please uninstall any old adb driverpacks off of your pc for your moto G, install these and reboot your pc
*After driver install reboot before doing anything with your phone make sure usb debugging enabled and plug your phone in once or twice to make sure the right driver is loaded and ready
-When plugged in during fastboot it is Motorola adb interface in device man
-When Plugged in during normal power up/adb it is shown as something else - change it to Moto Adb
4.) Find your adb folder & Place 2.8.6.0 Twrp img /PhilZ LPK / Falcon_debloated stock rom into the adb folder itself to get ready for recovery flash & sideload of stock lollipop
5.)Do the wipes I listed on the other thread advanced wipe user data/media f2s format and data format f2fs (click change format type just to be sure) REBOOT RECOVERY
6.) If not on the recovery already I listed Flash your twrp recovery from adb while your phone is in bootloader window fastboot -fastboot flash recovery yourrecoverynamehere.img
**To use the adb I included once in your adb folder SHIFT+RIGHT-CLICK anywhere blank inside the folder and 'open command prompt here' - IMPORTANT --> After flashing recovery gracefully volume down to recovery from bootloader , unplug your usb cable after about ten seconds and reboot recovery once at least to initiate it. If it powers down boot into bootloader flash again optionally and boot into recovery manually if it powers down again
7.) Manually format each dalvik-art / cache / system then do the standard factory reset format ...
**Make sure this file is in your adb folder Along with the Debloated Rom
8.) Reboot Into recovery Plug USB cable enter advanced/Adb Sideload and Swipe to begin // Go to adb folder SHIFT + open terminal Window command prompt here and type
PHP:
adb sideload falcon_LP_partition_II.zip
9.) Wait Til It is Done and reboot into bootloader then choose recovery and repeat step 8 (close old window and open a NEW terminal window) with code
PHP:
adb sideload falcon_LP_debloated.zip
10.) Unplug The cable reboot system DO NOT Superuser root/ Do not allow twrp to install root . Wait approx ten minutes for first boot setup your phone
Do Not Install any gapps Though if you want I did use gapps-lp-20141212-signed.zip with success ,none other.
Do not install any kernels with this except ATTACKED KERNEL + Adiutor or synapse OR possibly aero kernel + aero tuner app & Do not install them until your phone is completely setup & stock backed up rebooted at least 2-3 times to settle.It is much better to just not worry about leftovers and flash a kernel to stock rom intact whenever not on over another.
When initiating WiFi exchange services crashes for some reason allow it to find open networks and have your location on and always on during sleep until signed into google initial sync is done etc etc , THEN you can turn location off & Switch it to only on while plugged in
Also on accounts main page top right uncheck sync for google services after initial sync and a rebbot or two.
*Battery Savers,bigtime.
Enable developer usb debugging and animation scales all to .5
Turn of motorola Privacy stuff they just want in your privacys lol
Turn WiFi off and enable mobile data get where a signal is good so you can get your data right .. I turned on automatic(not home) data roaming AND DO NOT TOUCH SUBSCRIPTION-your phone will cease to function if you switch it from NV
Edit your sounds volumes alarm ringer etc
Copy the latest SuperSu to your Moto G flash it in recovery
Reboot and settle , Plug it in to your pc and Place your tiBackup folder back onto phone where it was music pics you gotta have on it wallpapers etc.. . ..
Now flash This puppy here and reboot
I will update this thread shortly and put up a System Apps update zip from tiBackup of just ten apps.
And yes I uninstalled the stock Voicemail app thing with tibackup I' m pretty sure it is just a trial and It is not your carrier's built in vm service.
When I used the gapps to see if exchange services issue would straighten out I also uninstalled play games books tv and YouTube. I used OGyoutube instead.
Exchange Services hardly ever does the thingie, and Ogyoutube doesn't allow sign-in YET, but plays in background..
Ds battery I used Profile strong / Fix is set at 256 but IG 512 is fine too / Yes only use trimmer once a month or so / Yeah moto G multi seem worked enable both click aww yea/
Wakeblock Only One I used was WiFi Full/
Here is the update 15 Moto G apps
update Chrome Opt Out of Ads ,Update Gallery idk what else . Only thing I can think of it may 'need standard' that is missing is ,adway or replace chrome with #noChromo x32 . .You have a choice of two launchers only for fact I included Stained icons pack it looks nice with this..
Uninstall if you see fit.
Here is an excellent Material Wallpapers Pack
EDIT:Aero Kernel Didnt work til I reflashed stock boost 5.02 kernel for falcon and had to sideload it. Me no likey that I advise skip it ,use attacked if you want one.
Or maybe it is just that I needed to disable the battery saver, Wakelock App, and Turn off Moto Multitasker before installing a new kernel idk right now..
Good Chance of It, I did however wipe dalvik & cache pre-kernel update.

Stock VM isn't a trial... Just wanted to add my 2 cents.
Sent from my xt1031

[REF] [ROOT] [RECOVERY] [BOOT LOADER] Metro PCS LG K7 LGMS330 [Guide For Dummies]

I have not been on this site since posting my guide, i do want to let any future people reading this know that, I am not a professional. everything in this guide is using stuff from other peoples threads.... this thread is just step by step directions on how i rooted (and installed TWRP on) MY lg k7 (MetroPCs). Also i had to root before i unlocked the boot loader. Which is not safe, you should probably unlock the boot loader before you root, but i couldn't figure out how to unlock it without root access.
I AM NOT RESPONSIBLE FOR ANY THING THAT HAPPENS TO YOUR DEVICE!
YOU AND ONLY YOU CAN BE HELD RESPONSIBLE​
~BACK UP FILES ON PC, YOUR PHONE WILL BE RESET TO FACTORY SETTINGS DURING THIS TUTORIAL~
Step One: Enable Dev Options
A) open settings>about phone>software info then tap "Build Number" really fast about 10 times
B) open settings>Developer Options, then check the box labeled "Enable OEM Unlock", and the box Labeled "USB Debugging"
Step Two: Install Android SDK/ADB/USB drivers
A) go to http://developer.android.com/sdk/index.html in your browser, and click download...
B) go to https://www.microsoft.com/net/default.aspx in your browser, and click the big blue button that says .NET
Framework 4.6.1 or X.X.X depending on when your reading this...
C) go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html scroll down until you get to the first box, labeled Java SE Development Kit 8u91 or XuXX Depending on when your reading this, then find your OS (ex: Windows x86, Mac OS, Linux, Etc..), then select the download link
Step Three: Installing LG K7's USB Driver's
A) unlock your phone
B) plug your phone into you Computer via USB
C) pull down your notifications, Tap on the USB icon which should be labeled "Media Device (MTP)," "Send Images (PTP)," or "Charge Phone"
D) if a dialogue box pops up asking to install drivers tap install, if not proceed to step E
1) Your PC should ask you if you want to auto run, Either auto run or open the folder and run LG_PC_Programs.exe then proceed to Step Four
E) select "Media Device (PTP)," if not already selected
1) click the three vertical dots next to the magnify glass in the upper right hand corner, select install pc drivers, then tap install
Step Four: Installing Java SE
A) return to the folder where you downloaded the files in step two, install the file which contains the word java in it
Step Five: Installing Microsoft .NET 4 Framework
A) now in the same folder as step four, install the with the name "NDP461-KB3102438-Web," the name might be different then mine depending on when you are reading this
B) if it is already installed it will notify you and you can proceed to the next step
Step Six: Installing Android Studio 2.0 (SDK/ADB Drivers)
A) in the download folder from step four & five, double click the remaining file, the name should contain the words "android", and "studio" in it
B) when the dialogue box opens requesting admin rights, select allow
C) click next
D) click next
E) make sure all boxes are checked and click next
F) read the license agreement, (unless your the 99.9% that doesn't) click i agree
G) you may click next or choose where you'd like to install android studio, and where you'd like to install SDK, for this tutorial i will change make a new folder in my docs named SDK then change the SDK install dir to My Docs
H) click next
I) it will take a moment to install so just wait
(note: the progress bar will fill up, then reset, as it is installing in two separate locations)
J) when finished, click next
K) uncheck the box and click finish
Step Seven: Root your device
(Note: I rooted before i unlocked my boat loader, as i could not get it to boot into boot loader mode until i rooted it)
A) go to http://www.kingroot.net/wap on your android device and download the apk file
B) go to settings>security and check the box labeled "Unknown Sources"
C) install the apk
Video tutorial for king root here: https://www.youtube.com/watch?v=tG_ruuTPVpU
(Not my channel or video)
D) open the king root app
E) make sure you have a charged battery or your phone is plugged in as the rooting process time may vary (better safe then sorry)
F) swipe up until you see a "TRY IT" button click it
G) under "Root Access not available" tap "Get Now
H) do not turn off your phone
I) when it is done you can tap optimize now if you wish, otherwise close the app
Step Eight: Replacing KingRoot with SuperSU ~ W0lfDroid Method
A) go to http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
B) scroll down until you see the word "download:" (should be right above the related posts
C) click on the "new link" next to "Replace_Kingroot_With_SuperSU.zip"
D) extract the .zip so that the "MRW" folder is on your internal storage
(Easiest way is to download it on PC and open up your k7 in "my computer" and select internal storage and drag the MRW folder inside the .zip there)
E) go to google play and search "terminal emulator for android" or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
F) install the first one, or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
G) open terminal emulator
H) type "su" without the quotations
(everything typed in the terminal is case sensative)
I) type "sh /sdcard/mrw/root.sh" without the quotations
J) you might see a few errors, that is fine
K) wait until it says finished
L) when SU opens, select "update" "install" or what ever pops up
M) when it asks to uninstall, uninstall it, it is not uninstalling SuperSU it is uninstalling Kingroot,
O) if 30 minutes pass and it is still uninstalling then exit the app and then reboot the phone
DO NOT STOP HERE ~ YOU HAVE TO UNLOCK THE BOOTLOADER, and OPTIONALLY FLASH TWRP
Step Nine: Unlocking The Bootloader
A) refer to step one and double check the OEM unlock is enabled and USB debugging is turned on
(If not then please enable them)
B) search quick boot on the google play store download the first app it should be a circle with a lightening bolt
C) open quick boot
D) when asked to "allow root access?" tap allow
E) if an add pops up close it with the ex in one of the corners
F) tap on the word boot loader
G) at the top of your phone you should see " * Welcome To Fast Boot Mode : "
H) now go to your SDK dir, in my case it is C:\Users\USER\Documents\SDK
I) hold shift, then right click on the "platform-tools" folder, then select "open command window here"
J) in the CMD window type "fastboot devices" - without quotations
(everything is case sensative)
K) then type "fastboot oem unlock" - without quotations
L) then type "fastboot getvar unlocked" if that doesn't work try "fastboot getvar" or "fastboot getvar unlock" to confirm if it is unlocked
(if non of the getvar commands work you did something wrong, and i wont be able to help you, but if you followed the tutorial you shouldn't have any issues as these are the exact steps i took)
M) then type "fastboot reboot"
LEAVE THE CMD OPEN OR YOU WILL HAVE TO REPEAT steps H-I
Step Ten: Flashing TWRP
A) go to http://forum.xda-developers.com/general/general/qa-metro-pcs-lg-k7-lgms330-t3331678 and click on the latest download for twrp for me it is BETA1
if the links on that page dont work then use the links here http://forum.xda-developers.com/showpost.php?p=66282525&postcount=42
B) extract the download into your SDK folder on your PC
C) in the sdk CMD window from Step nine
D) type "fastboot devices" - without qoutation
E) ~optional, HIGHLY RECOMENDED~
1)type fastboot "boot twrp-image-3.img" - this will boot up twrp WITHOUT flashing it, just so you can make sure everything is working right
in my case it was twrp-image-3.img check your twrp file name and replace fastboot boot twrp-image-3.img with
fastboot boot INSERT YOUR FILE NAME HERE.img
2)in twrp tap reboot>bootloader
F) when bootloader mode opens back up
G) type "fastboot flash twrp-image-3.img" or "fastboot boot INSERT FILE NAME HERE.img" depending on your file name
H) when finished flashing type "fastboot reboot"
Step eleven
A) follow instructions on step one
B) the reason you must do this is because when you flash TWRP it erases your entire phone and resets it
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7

Well done, my friend. Well done indeed.

[QUOTE
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7[/QUOTE]
is this ok with the gapps 5.1 instsall .zip for twrp install or should i use a different? also, do you have a suggested camera app? awesome thread btw. Nevermind simple twrp install fixed everything.

I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?

Today backup important files you need!

Is this a real method BC everybody having problems rooting this device so I ask can u make a video and add screenshots
Sent from my LG-D800 using Tapatalk

I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info

While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?

zgauthier8286 said:
I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info
Click to expand...
Click to collapse
can you please help me i have 2 MS330 that are bricked

callihn said:
While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?
Click to expand...
Click to collapse
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution

zgauthier8286 said:
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution
Click to expand...
Click to collapse
Just reboots. Think we're going to have to change something? Boot image? Kernel?

callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it

Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk

callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
Of other interest 5.1 is very dendent on Google apps and move app updates to the system via TB or Link2SD fails more than it succeeds, shows they moved but app inaccessible afterwards hence brick. Mine went down trying to integrate play services and reinstalling from adb didn't help. FYI if you relock the BL it'll lock the phone with a security error too. Moving play services causes unending error screens so you can't really see if it's done moving, but I waited a good 5 minutes before reboot. Issue on fails could have been the system not being r/w. Needless to say backup, backup, backup as I hadn't because I've never had a serious issue doing that and considered it a trivial task. Anyone had good success with integrating updates and cache? Anyone restored from twrp yet?

JayCouture.com said:
Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk
Click to expand...
Click to collapse
Yes! Just follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=66456635&postcount=1

zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.

callihn said:
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.
Click to expand...
Click to collapse
If your rooted u can dl a reboot recovery app on the play store I have one that works like a charm. But im gonna take a look through Linux at the kernel options using make menu_config and see if there's anything I can see in there.

zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
im having a problem w the security 9 error boot loop. only seem to b able to get it into download mode , not bootloader or recovery. would your boot and recovery img's help me at all ya think ? thanks !

goitalone said:
I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?
Click to expand...
Click to collapse
Thanks again. For anyone that has a soft bricked LG K7 see this man! He brought my S#!? To life through teamveiwer. Thanks again. From my LG K7.

Maybe just my experience, but regarding step 10. I had to have the twrp image in SDK>platform tools, also when you get to fastboot flash twrp-image-3.img, I couldn't get it to work, until I typed it as fastboot flash recovery twrp-image-3.img. Hope this helps anyone else getting errors during this part. Thanks for the writeup.

[Guide] Stock MIUI (7/8): Official unlock, recovery, root, xposed, DPI & debloat

Please read this thread thoroughly and carefully. Do this at your own risk. The following had worked for two of the same devices. I've made this guide partly for my own notes and because other guides out there seemed incomplete.
Aim of this guide is to have an unlocked bootloader with a custom recovery for flashing root, Xposed and other things while possibly preserving the ability to get official OTA updates. The following is a summary of what this guide entails.
Official Mi FlashUnlock was used to unlock the bootloader. It will take 3-4 days before Xiaomi grants unlock permission on your account. This guide does not touch the emmc for unlocking since that method causes -2% or 50% battery bug. This is the same bug that most CM flashers are running into. In the meantime, prepare your computer and phone for when you do get permission.
Recovery TWRP Alka is a good recovery to use since it's already patched (boot.img) so that it can flash MIUI recovery ROMs (OTA) as well as CM based ROMs. It also has the ability to backup the entire phone (EFS partition). I would strongly suggest backing up all partitions and moving it to your computer or SD card after. You may choose Cofface TWRP if you're never going to try CM based ROMs. Helpful links from other guides will be posted at the end. I have yet to receive an OTA update yet so this part is not tested.
Root, Xposed and DPI instructions are all outlined below. Flash and configure these as you normally would.
Debloating is a big thing that I do to stock ROMs. This essentially prevents the ROM from running the apps, slimming the ROM and hopefully extending daily usage. There are few things that broke though. The only thing I could care about is that I'm not able to change the wallpaper via the Settings (lockscreen + homescreen) anymore. However, the rest that broke were the features that I don't use such as Cleaner (sponsored by Cheetah), dual apps and etc. Debloat accordingly. Be cautious, as I won't be necessarily explaining what each item does. ​
OTA updates does work. However, recovery, root, DPI, Xposed and debloat all needed to be done again.
Prep work
Sign up and login to all the neccessary accounts
Sign up for unlock: http://en.MIUI.com/unlock/, this will take 3-4 days.
Make sure you're also signed into your Mi account on your phone and that you can find your phone at http://i.mi.com/.
Prepare your computer for drivers and software
Enable Windows TESTSIGNING first: https://msdn.microsoft.com/en-us/library/windows/hardware/ff553484(v=vs.85).aspx
The TESTSIGNING boot configuration option is enabled or disabled through the BCDEdit command. To enable test-signing, use the following BCDEdit command:
Bcdedit.exe -set TESTSIGNING ON
To disable test-signing, use the following BCDEdit command:
Bcdedit.exe -set TESTSIGNING OFF​Restart your computer and then install the following:
Mi PC Suite (http://pcsuite.mi.com/)
Mi ROM Flashing Tool and drivers for fastboot & ADB (http://en.MIUI.com/a-234.html)
Mi FlashUnlock tool (http://en.MIUI.com/thread-202290-1-1.html)
Fastboot EDL, just in case (http://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718)
Prepare your device
Enable developer mode by going to Settings > About phone > Tap on MIUI Version repeatedly until you get a toast that Developer Mode is enabled
Go back to Settings and then tap on Additional Settings > Developer options
Enable Developer options
Enable OEM unlock
Enable USB debugging
Plugin your phone into your computer, it should now install all the drivers
Turn TESTSIGNING OFF and restart your computer
Signs of computer recoginizing your phone properly (for ADB, Fastboot and etc)
In Device Manager, you should see under Android Phone: Android Composite ADB Interface and Xiaomi Composite MDB Interface
You phone should have also asked you to allow debugging from your computer (check always allow)
Unlocking your phone
Log in from time to time to check your unlock permission from the MiFlash Unlock Tool. You'll just need to follow the instructions to unlock your bootloader.
Boot into fastboot by holding volume-down + power
Run MiFlash Unlock and follow the onscreen instructions
If you're curious to see if it's unlocked, boot back into fastboot and type fastboot oem device-info
Using MiFlash tool to flash another MIUI ROM (China to Global, skip if you already like your MIUI version)
Boot into fastboot by holding volume-down + power, you will get the fastboot bunny
Download your desired fastboot version: http://en.MIUI.com/a-234.html, you can check the changelog and description from here: http://en.MIUI.com/download-301.html
Or you can use MIUI 8 Global Beta: http://forum.xda-developers.com/redmi-note-3/development/MIUI-8-global-beta-redmi-note-3-t3417423
Extract the fastboot ROM (.tgz) twice, the first extract you'll be left with .tar file, the second should leave you with a directory of files
Place that directory in the root of your drive (or somewhere with a short location)
Launch the MiFlash tool, browse to your extracted fastboot ROM and click on refresh. You should now also see your device listed
Click on Flash All and click on refresh once more
Now flash your device, it should take upwards of 170s
Let your device boot, which should take 5m or longer. Set it up as you normally would and redo all the steps outlined in the "Prepare your device" section (don't need the TESTSIGNING part).
Flashing TWRP (Alka) & Root
Download the following files:
TWRP https://dl.twrp.me/kenzo/
Alka http://www.mediafire.com/download/febttn8piu0vfae/recovery+Alka+Update.zip
Universal Boot Img Patcher http://forum.xda-developers.com/redmi-note-3/how-to/modified-twrp-deleting-emmcappsboot-t3371667
SuperSU https://download.chainfire.eu/969/SuperSU/
You should now be working in an administrator command prompt in this directory: C:\Program Files (x86)\Xiaomi\MiPhone\Google\Android. Take this chance to extract fastboot-edl into this same directory. Also place twrp and alkarecoveryupdate img files into this directory. You should have the Universal Boot Img Patcher and SuperSU copied to your phone.
Follow these, don't reboot in between unless stated:
Enter fastboot (volume-down + power)
Type fastboot boot twrp.img
Swipe to allow modifications
Flash universal boot img patcher zip
Flash twrp.img by selecting "Select Image" option.
Select recovery partition & flash it
For some reason twrp has to be flashed this way or else recovery will be reverted to stock MIUI recovery. You can try Alka directly to see if it works for you.
Now reboot to recovery
Flash alkarecoveryupdate.img by selecting "Select Image" option.
Select recovery partition & flash it
Reboot to recovery
Flash SuperSU
Reboot system and let it boot MIUI, it may take longer than usual
You should now test root, configure SuperSU & install Busybox.
Flashing Xposed
Download the latest SolarWarez Xposed: http://forum.xda-developers.com/xposed/unofficial-xposed-MIUI-t3367634
Download Material Xposed Installer: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Download Xposed uninstaller, just in case: http://forum.xda-developers.com/showthread.php?t=3034811
A few posts suggests that the latest official Xposed v86 works with MIUI, but doesn't seem to be the case for me.
Install the Xposed Installer of your choice (apk install)
Enter recovery (volume-up + power)
Flash v86-sdk22-arm64 (LP, sdk23 is for MM)
Clear cache and dalvik
Reboot the phone, this should take 5m or longer since we wiped the cache
If you notice bootloops or crashing services, use the uninstaller. Worst case, flash it back to stock using MiFlash.
Xposed modules that I use:
App Settings
MIUI Brightness Fix
Mobile Radio Active Fix
Power Nap
Play Store Fixes
Spotify Skip
TextLinkify
WhatsApp Tuner
xMIUI
xInsta unfortunately does not work well.
Changing DPI
Using FX Explorer (Root access enabled) or any explorer you feel fit.
Go to system/ and edit build.prop
Add this line in between persist.hwc.downscale_threshold=1.15 & #ro.hdmi.enable=true
ro.sf.lcd_density=370​
Reboot your phone
You should be able to use a DPI changer such as texdrodier_dpi to change it to whatever you like after
ROM Debloating, should get around 1.8GB of free memory on boot
Using FX Explorer (Root access enabled) or any explorer you feel fit.
Create the backup location:
Create a folder in system named _backup
Create subfolders named app, data-app, priv, vendor
Debloat app folder as you wish but here's my list:
Go to system/app
Cut the following into system/_backup/app
AGPSTestMode
AmapITS
AnalyticsCore
AntHalService
BasicDreams
BrowserProviderProxy
BugReport
CalendarLocalAccount
CalendarWidget
CloudService
Drive
Email
FileExplorer
FM
Galaxy4
GuardProvider
HTMLViewer
HiddTestApp
HoloSpiralWallpaper
KSICibaEngine
KingSoftCleaner
LatinImeGoogle
LiveWallpapers
LiveWallpapersPicker
LunarInfoProvider
MiDiscover
MiLivetalk
MiuiVideoPlayer
MiWallpaper
MSDC_UI
NoiseField
Notes
OmaDownload
OmaDrmEngineApp
PartnerBookmarksProvider
PhaseBeam
PhotoTable
QtiBackupAgent
QtiFeedback
SampleAuthenticatorService
SapClientApp
SecureSampleAuthService
SoundRecorder
SecProtect
StaProxyService
StepsProvider
Stk
SystemAdSolution
TouchAssistant
TranslationService
Videos
VisualizationWallpapers
WAPPushManager
WfdClient
xdivert
fastdormancy
imstests
jjcontainer
jjhome
jjknowledge
jjstore
Go to system/data-app
Cut the following into system/_backup/data-app
Facebook
klobugreport
Go to system/priv
Cut the following into system/_backup/priv
AndroidForWork
AutoTest
BackupRestoreConfirmation
Browser
Calendar
CleanMaster
FM2
GoogleBackupTransport
GoogleFeedback
Mipub
Music
MusicFX
SpacesManagerService
SpacesTrustAgent
Velvet
xtra_t_app
Go to system/vendor
Cut the following into system/_backup/vendor
CTA
ChinaMobile
ChinaTelecom
ChinaUnicom
CmccPower
MPCS
app
Helpful posts if you have other issues
Flashing to CM: http://forum.xda-developers.com/redmi-note-3/how-to/guide-step-step-guide-flash-cm13-build-t3391839
TWRP Explained: http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Fastboot EDL for softbricked phones: http://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
IMEI Repair: http://en.MIUI.com/thread-245598-1-1.html
MIUI Unlock guide: http://en.MIUI.com/thread-202290-1-1.html

If using alka twrp and officially unlocked the bootloader, universal boot image patcher was not necessary for flashing any official miui rom.
Sent from my Redmi Note 3 using Tapatalk

timberwolf60 said:
If using alka twrp and officially unlocked the bootloader, universal boot image patcher was not necessary for flashing any official miui rom.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
i had to do what i did because the recovery wouldn't stay flashed. alka has the boot image built in anyways, so really it's the same thing.

I think DPI should be ro.sf.lcd ? you've written ro.sf.ldc??? Is that correct?

rayulove69 said:
I think DPI should be ro.sf.lcd ? you've written ro.sf.ldc??? Is that correct?
Click to expand...
Click to collapse
fixed. typo

What if i directly boot and flash alka recovery?
What if i directly boot or flash alka recovery? instead of first flashing twrp official and then flashing alka through it

RavdeepAurora said:
What if i directly boot or flash alka recovery? instead of first flashing twrp official and then flashing alka through it
Click to expand...
Click to collapse
try it. like i said in my post, i had to do what i did or else alka wouldn't stay flashed. if it stays flashed for you then great, you've saved 5 steps.

The only thing I could care about is that I'm not able to change the wallpaper via the Settings (lockscreen + homescreen) anymore
Click to expand...
Click to collapse
For what it's worth, I haven't done anything yet aside from bootloader, MIUI 8 and install nova launcher; the wallpaper/lock screen error only happens when I've got nova set as default. When I go back to the stock launcher, I can change both without error. Then I set nova back to default, I can still change wall/lock until I actually restart the phone.
So hopefully that might give you an idea as to what's going on and maybe it'll help.
Do appreciate the guide, something I'll have to do eventually when CM13 works out the kinks.

Thanks the dpi edit works great.

capitak said:
For what it's worth, I haven't done anything yet aside from bootloader, MIUI 8 and install nova launcher; the wallpaper/lock screen error only happens when I've got nova set as default. When I go back to the stock launcher, I can change both without error. Then I set nova back to default, I can still change wall/lock until I actually restart the phone.
So hopefully that might give you an idea as to what's going on and maybe it'll help.
Do appreciate the guide, something I'll have to do eventually when CM13 works out the kinks.
Click to expand...
Click to collapse
Thanks! Good to know it wasn't from the debloating.

I just want to have "write access" to my MicroSD card, so I plan to unlock/root my device.
If I follow the guide just to unlock, is all my personal data/setting/profiles/installed apps still be there after unlock?
Pls advice.

Just waiting on my RN3 to arrive, so this post is perfect timing.
I'll report back once I've followed your steps.

should i install SolarWarez Xposed and Material Xposed Installer or just one of them?

same240 said:
I just want to have "write access" to my MicroSD card, so I plan to unlock/root my device.
If I follow the guide just to unlock, is all my personal data/setting/profiles/installed apps still be there after unlock?
Pls advice.
Click to expand...
Click to collapse
Don't know. Unlocking bootloader usually wipes the device.
doganmanis said:
should i install SolarWarez Xposed and Material Xposed Installer or just one of them?
Click to expand...
Click to collapse
You need both, as usual.

I'm getting this problem in cmd prep work
Bcdedit.exe -set TESTSIGNING ON
AN error has occured setting the element data.
The value is protected by Secure Boot policy and cannot be modified or deleted.

RexMi6 said:
I'm getting this problem in cmd prep work
Bcdedit.exe -set TESTSIGNING ON
AN error has occured setting the element data.
The value is protected by Secure Boot policy and cannot be modified or deleted.
Click to expand...
Click to collapse
You may need to disable driver signing instead. Google that for your windows 8 or 10 machine. My method ensures it's disabled.

I used your guide.
Thank you!
everything is working, on stable-globe rom.
I'm using Titanium backup to uninstall system apps

I'm using the official MIUI Global Stable 7.5.3.0 and have unlocked the bootloader using the official way as well. I just now installed alka recovery directly using fastboot commands and it seems to work fine. It's still there after rebooting a couple of times and I already took a full backup of the phone. Haven't tried restoring it yet, which I will probably do later and post the results, but I guess that will work as well.
Edit: I tried to restore a backup just now, but I got an error when it tried to restore the firmware partition. The error was "extractTarFork() process ended with error : 255" if I'm not mistaken. Still everything seems to be working fine regardless of that error.

Thanks !!! Amazing post!!! Helped me a lot !
I have a Note 3 Pro , couldn't unlock the Phone with Global Version (even with permission) always stoping in 50%, tried to change to Chinese Version, but I couldn't, so I tested with Global Developer Version (Miui 8) and I got the unlock

I'm doing same process you said after unlocking boot loader officially. I'm trying to flash mokee rom and open gapps pico arm 64. After booting rom is crashing saying com.android.phone is stopped and when i check for oem device info it is locked. plz help where am I going wrong

[Guide] Pixel XL Android 7(Nougat) Unlock/Install Stock Images + Kernels/Recovery +

[Guide] Pixel XL Android 7.1.2 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2017 Security Patch​
Intro
This thread is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel/Pixel XL'.
It also works for Pixel owners: If, they download the correct files for their Pixel.
This Guide is not for use with the Second Generation Pixel 2 or Pixel 2 XL devices.
Update(s):
Other - Added 'Other' after 'Prerequisites'
Disclaimers:
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Google Pixel XL or Verizon Pixel XL phone with an unlockable Bootloader, ([How-to] Unlock bootloader on Verizon Pixel/XL by burduli) - The unlock method was discovered by: Qu3ntin0), and the latest 7.1.2 August 2017, Factory Image (NHG47Q - Verizon; NKG47S - T-Mobile, Fi carriers, and Rogers; NZH54D - Deutsche Telekom; NJH47F - all other carriers).
Note: If you want the latest OTA or Binaries. Tap the Menu icon (upper left corner) then tap Full OTA Images or Driver Binaries
PC - With the latest Android SDK or SDK Platform tools installed.
Important: Update Android SDK or Platform Tools, regularly, for optimal performance.
Need help installing Android SDK or SDK Platform Tools
How to Install ADB & Fastboot on Mac, Linux & Windows-(Method 1)
Easiest-way-to-install-androids-adb-and-fastboot
Other
Pixel XL Guides: Android 9.0.0 (Pie)Android 8.1.0 (Oreo), Android 8.0.0 (Oreo)
Pixel 3 XL Guide: Android 9.0.0 (Pie)
Credit/Thanks/Recognitions
TWRP
TWRP for Google Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone
SuperSU
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
Magisk/MagiskManager
[Unofficial] Google Pixel family support by goodwin_c
Custom Kernels
ElementalX kernel
Franco's Kernel
Busybox/Busybox Checker
[MODS] Android Oreo Aroma installer misc. Mods by Tulsadiver
UPDATE-Busybox.Installer.v1.26.2-ALL-signed.zip
meekfik, download from PlayStore
Busybox Free (Stericson), download from PlayStore
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] by osm0sis
UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip
Busybox Checker, download from PlayStore
Other
pcriz -Fastboot Slot Commands, Custom ROM installion help, Magisk help, and help on many many other subjects.
Those I may have inadvertently forgotten.
Index
Open Command Prompt/ Boot Bootloader/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type 'cmd' and press enter.
Note: If your computer only has 'open powershell here' in the context menu and you do not want to change it or add open 'command prompt here' use use option 2.
Boot Bootloader:
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Press volume Up/Down button until you see Recovery Mode > Press Power button.
Testing ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt and press enter to test ADB.
Code:
adb version
It should return a version number for ADB.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot bootloader.
Connect your phone to your computer with a USB cable.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock Your Bootloader
Backup your data and Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Build Number. Tap Build Number until you see you're a Developer. Tap back > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot Bootloader
Connect your phone to your computer via USB cable.
Open a Command Prompt on your computer.
Type the following at the prompt and press enter:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to make your selection.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll be greeted with a warning that says Your device software can't be checked for corruption. Please lock the bootloader everytime you reboot. It's ok, as long as your bootloader is unlocked it will stay there.
Important: do not repeat do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see 9 of this guide for instructions on how to return to stock and lock the boot loader.
Install Factory Image and wipe data
Backup your data and Internal storage
Download the factory image for your phone and carrier.
Unzip factory Image
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install Factory Image and keep data
Backup your data and Internal storage
Download the factory image for your phone and carrier.
Unzip factory Image
Edit flash-all.bat: Remove -w
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install A Custom Recovery and Root with SuperSU
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Backup your data and Internal storage
Download files:
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone.
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release to your phone.
Copy the following file to the platform-tools folder: twrp-3.0.2-0-RC1-fastboot-marlin.img rename it twrp.img
Boot Bootloader
Connect device/phone to computer
Open a Command Prompt on your computer.
Type the following at the Prompt.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
Tap Add more ZIPs button, select SuperSU-v2.82-201705271822.zip
Swipe the slider to install.
Reboot system
Install A Custom Recovery and Root with Magisk (Clean Install)
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Note:[Substratum] theme Spectrum does not work with Magisk root.
Backup your data and Internal storage
Download the following files:
ElementalX-P-1.14.zip for Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img
twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Magisk-v13.3-Pixel-b4.zip
MagiskManager-5_1_1.apk
Magisk-uninstaller-20170720.zip
Flash Boot.img - If you have TWRP, SuperSU, or a custom kernel installed.
Extract the contents of your factory image and open the folder it creates. From there, extract the second archive (image-marlin-aaa99a.zip)
Then open that folder and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the phone to your computer
Open a Command Prompt on your computer.
Type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
When it finishes, leave the command prompt window open, your phone in bootloader mode and connected to your computer.
Install TWRP
Place twrp-3.0.2-0-RC1-fastboot-marlin.img in your platform-tools folder and Rename it twrp.img
Type the following command at the prompt:
Code:
fastboot boot twrp.img
When TWRP boots, tap the Install button and select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe the slider to install
Press the back button until you are on TWRP's main menu select Reboot > Recovery.
Flash the ZIPs
Disconnect your phone from your Computer.
Tap the Install button, then navigate to the files you downloaded.
Select the Magisk Uninstaller.zip, tap the Add more ZIPs button.
Select the twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install
Reboot Recovery
Tap the Install button select a Custom Kernel: ElementalX-P-1.1x.zip or Franco's Kernel-r1x.zip.
Tap Add more ZIPs button select Magisk-v13.3-Pixel-b4.zip, tap the Add more ZIPs button and select: twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe to install
Note: During the Installation of ElementalX, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and press Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and Finish. After, the other ZIPs are installed.
Reboot System
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Install MagiskManager
Install Magisk Manager (5.1.1.apk)
Wipe data on Magisk Manager
Enable Magisk Hide
Enable Core Only Mode
Toggle on and off systemless hosts
Reboot system
Check for Latest Version, Root, and Saftey Net.
Update Magisk Dirty Flash
Download file:
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip
Flash the ZIPs
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip, tap the Add more ZIPs button.
Select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install.
Reboot system
Check for Latest Version, Root, and Saftey Net.
Custom ROMs for Pixel/Pixel XL
[ROM][Pixel-XL][7.1.2_r24]★ Pure Nexus ★ Substratum | Fi | WiFi Calling ★[07/25/17] by BeansTown106
[ROM][Pixel-XL][7.1.2_r33][OMS] Pixel Dust for marlin [FINAL][2017/08/22] by spezi77
[ROM][Resurrection Remix v5.8.3][Android Nougat 7.1.2][OMS][07/24/17] by BDogg718
[ROM][UNOFFICIAL] LineageOS 14.1 Nightlies for the Google Pixel (marlin/sailfish) by invisiblek
Paranoid Android 7.2.1 - AOSPA - Pixel XL by freak_97
ROM][7/21/17][Marlin][7.1.2][WEEKLY]Team OctOs Oct-N by cjkacz
SCREW'D ROM
Install Custom Kernel
Franco's Kernel - SuperSu
Download file:
The latest Franco's kernel for Pixel/Pixel XL
Boot into TWRP
Press Install button select the file you downloaded
Swipe slider to install
Reboot System
ElementalX-PXL-1.xx by flar2 Kernel - SuperSU
Download files:
ElementalX kernel
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release
Flash ElementalX zip in TWRP recovery (do not flash SuperSU-v2.82-201705271822.zip again if you're already rooted).
During the Installation, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and tap Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and then Finish.
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Franco's Kernel or ElementalX-PXL-1.xx by flar2 Kernel - Magisk
See [Unofficial] Google Pixel family support by goodwin_c for Installation Instructions.
Install Substratum Theme
SuperSU Root
Install Substratum Theme Engine from the play store.
Install [Substratum] Spectrum theme from the play store. Note: I used Substratum theme Spectrum to test the installation of Substratum with SuperSU root..
Magisk Root
Researching Information
Return to Stock and Lock Bootloader
Return to Stock
Backup your data and Internal storage
Download the appropriate factory image for your phone and carrier.
Unzip factory Image
Copy the following files to the platform-tools folder on your Computer
flash-all.bat
Verify -w is present in flash-all.bat. Example: fastboot -w update image-marlin-aaa9.999999.999.zip
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following command at the prompt.
Code:
flash-all
Lock Bootloader
Phone
Boot Bootloader
Connect your phone to your Computer with USB cable.
Computer
Open a Command Prompt on your computer.
Type the following at the prompt:
Code:
fastboot flashing lock
When it finishes the bootloader is locked.
The next step won't be needed if your Pixel XL reboots into system after bootloader relock.
You need to boot into system now, either press Power button to reboot OR issue the following command:
Code:
fastboot reboot
When your phone reboots disconnect your usb cable.
Audio Mod
Weta Audio Mod

we already have guides though

flex360 said:
we already have guides though
Click to expand...
Click to collapse
can't hurt to have an updated guide for those too lazy to read.. so many posts about "this guide is out of date" or "i dont have time to read 6 pages about other people's experiences"

Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.

jrhatfield said:
Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.
Click to expand...
Click to collapse

It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.

JimSmith94 said:
It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.
Click to expand...
Click to collapse
I'll research it and make changes if needed.

Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.

iamjimmy said:
Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
¯\_(ツ)_/¯

About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?

Avasta said:
About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?
Click to expand...
Click to collapse
2. Install Factory Image and wipe Data
Code:
fastboot -w update image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
fastboot update image-marlin-aaa99a.zip

Homeboy76 said:
2. Install Factory Image and wipe Data
Code:
update -w image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
update image-marlin-aaa99a.zip
Click to expand...
Click to collapse
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.

Avasta said:
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.
Click to expand...
Click to collapse
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?

Homeboy76 said:
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?
Click to expand...
Click to collapse
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.

I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!

parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
When you flash a factory image, flash it in both slots.
Flash all once
Boot into the bootloader again
Swap slots in bootloader
Flash all again

(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)

pcriz said:
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.
Click to expand...
Click to collapse
Ok.

parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
If you follow the instructions above you should not have to worry about slot a/b. The firmware will put it in the correct slot.
If you are installing Custom ROM this thread is not for you. You, should follow the installation instructions of the Custom ROM you want to install.

parano666 said:
(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)
Click to expand...
Click to collapse
You're welcome!

Tutorial to Flash Lineage on Oneplus8t with magisk. Works with devices with originally locked bootloader (tmobile locked models)

READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down) Recommended to use Command Prompt commands instead of powershell (type cmd in platform-tools directory) https://developer.android.com/studio/releases/platform-tools
Unlock oem bootloader
Enable developer options (click build number several times)(make sure you’re connected to internet)
Enable oem unlocking, advanced reboot, usb debugging
Reboot to bootloader/fastboot
fastboot oem unlock
Unlock bootloader
Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding volume down while
booting)
Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
fastboot flash boot (path to boot.img)
fastboot flash dtbo (path to dtbo.img)
fastboot flash recovery (path to recovery.img)
Download firmware (https://kremowka.xyz/files/8fw/)
Enter recovery mode, enter fastbootd
Advanced > enter fastboot
Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload
LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in
there somewhere
Open notepad, copy commands from lineage, save as (file name).bat, drag into powershell from file explorer
(flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
adb devices (to confirm phone is connected properly and device drivers are configured properly)
adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are
too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
Reboot recovery?
adb sideload (path to copy partitions .zip)
Back > Reboot system now
It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have
data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done
that before this step (do it in fastboot, search up adb shell pull)
If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something
happened.
OPTIONAL (if you want magisk/root)
Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
Search in settings for “advanced”, click “advanced restart” and enable
Hold power button, restart, recovery
Apply update > apply from adb
adb devices
adb sideload (path to magisk .apk)
Signature verification failed, install anyway
Volume up to go to back arrow, reboot system now
Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file
transfer is on
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
What I use: Safetynet universal fix and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
Install from storage
Order I did it in was safetynet then raven, rebooting between each one but I'm not sure if it matters
Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click
google play services, google play store, and carrier services (the square check box next to the name, make sure
every check below when you open it as a dropdown menu is checked
Reboot phone
Now you can download whatever you want
If you install twrp, make sure you are using android 12 version and not android 11, android 11 twrp will destroy
your recovery if you try to use it on android 12.
Add on: If your phone is not detected by your pc, or is detected as “MTP” with an exclamation mark, you do not
have the right drivers. There are plenty of resources online to fix this, but one that I had trouble with was that I
was on windows 10 N instead of whatever the other version is, which doesn’t come with “mediafeaturepack.”
You need to install that on your own from https://www.microsoft.com/en-us/software
download/mediafeaturepack, or, if your device isn’t listed, go to windows application “optional features” and
add it from there.
If your computer won’t download qdloader 9008 qualcomm drivers through device manager, there are a few
things i’ve tried to fix it. Make sure you have correct drivers
from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
“The system cannot find the file specified”
Open command prompt as administrator
Type DISM /Online /Add-Package /PackagePath:"Full path of .cab file"
I put mine in C: drive folder but I'm not sure it matters
Also I'm not sure which one of the three I downloaded from the website. Did not cause any issue downloading
and trying to install all three, let me know if you figure out which one works. Maybe you need all three, I don’t
know.
If that doesn’t work, do sfc /scannow
Open windows update, make sure all updates are applied and restart windows (make sure you go to optional
updates and select qualcomm drivers)
Fastboot won’t connect
Make sure you’re using a usb 2.0 port instead of a usb 3.0 port, and make sure your usb cable is a data cable.
Google the difference if you don’t know what it is. Download usb drivers
from https://developer.android.com/studio/run/win-usb, open device manager, see if anything is there, if it
shows something in “other devices” click on it, click update drivers, browse my computer, let me pick, have disk,
and then browse to android_winusb.inf and click update, click bootloader interface. If you get “error 10 device
won’t start” when installing bootloader interface, one possible solution is to disable driver signing.
Open command prompt as an administrator (doesn’t have to be in platform tools directory)
bcedit /set testsigning on
Reboot, try to install driver again.
If your device is bootlooping, and you enter fastboot after updating to a12 firmware AND you have magisk\
modules downloaded AND you have twrp installed, do not press the up volume button, only cycle through
options with volume down, because it may enter an option cycle and you won’t be able to do anything unless
you fastboot flash boot twrp.img.
It’s recommended that as soon as you root, you backup persist.img, which contains imei info (you don’t want
that to get destroyed) I am unsure if there’s anything else device specific you need to backup, I've heard
vendor_image may be but it’d not as important as persist.
To backup persist.img, put phone in recovery, type in command prompt or powershell
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
adb pull /tmp/persist.img persist.img
This should save persist.img to your computer. Back it up somewhere you keep important things. Also don’t
give it out at random as it contains your imei number, not sure what the consequences of that could be but
nothing good is likely to come of it.
Important shortcuts:
Power + vol up – boot into system
Power + vol down – boot into fastboot
Power + vol up + vol down – boot into edl
IF DEVICE IS BOOTLOOPING AND YOU CAN’T ENTER ANY DIFFERENT MODES, CONTINUE HOLDING POWER +
VOL DOWN IN RANDOM PATTERNS. IT HAS TAKEN ME 20 MINUTES OF RANDOM BUTTON COMBINATIONS TO
GET INTO FASTBOOT FROM A BOOTLOOP. YOU WILL ALWAYS BE ABLE TO EXIT A BOOTLOOP IF YOUR PHONE
IS PHYSICALLY UNDAMAGED.
If VoWifi doesn’t work, pixelify dialer can get it working. Probably also just any custom dialer, but I like Google
dialer. Wait for the interface to change slightly, don’t clear data until you’ve waited at least a minute or two and
closed and reopened it a few times, but if it doesn’t change after installing pixelify then force close, clear data,
and wait a minute or two, reopen, and then wait. If it continuously doesn’t change you can reflash pixelify.
Note – If using pixelify module, disable auto update for android system intelligence, it will break gboard
translate and possibly slow down device.
You can also use magisk module “mindetach” to detach com.google.android.as from play store, which will fix
any auto update bugs. Credit to vewu for showing me that
https://github.com/j-hc/mindetach-magisk
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community.
Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for formatting, this is copied from a word doc. Please feel free to indent and number list yourself and
send me a better version

Does the third option work?

INTseed said:
Does the third option work?
Click to expand...
Click to collapse
did you configure the denylist? try clearing cache and data for google play services, google play store, and carrier services and rebooting

Mrmcfeffers said:
READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down)
a. Unlock oem bootloader
i. Enable developer options (click build number several times)(make sure you’re connected to internet)
ii. Enable oem unlocking, advanced reboot, usb debugging
iii. Reboot to bootloader/fastboot
iv. .\fastboot oem unlock
v. Unlock bootloader
b. Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding
volume down while booting)
2. Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
a. .\fastboot flash boot (path to boot.img)
b. .\fastboot flash dtbo (path to dtbo.img)
c. .\fastboot flash recovery (path to recovery.img)
3. Download firmware (https://kremowka.xyz/files/8fw/)
4. Enter recovery mode, enter fastbootd
a. Advanced > enter fastboot
5. Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in there somewhere
a. Open notepad, copy commands from lineage, add .\ before each line, save as (file name).bat, drag into powershell from file explorer (flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
b. Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
c. Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
i. .\adb devices (to confirm phone is connected properly and device drivers are configured properly)
ii. .\adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
d. Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
i. .\adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
e. Reboot recovery?
i. .\adb sideload (path to copy partitions .zip)
6. Back > Reboot system now
a. It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done that before this step (do it in fastboot, search up adb shell pull)
7. If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something happened.
8. OPTIONAL (if you want magisk/root)
9. Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
a. Search in settings for “advanced”, click “advanced restart” and enable
b. Hold power button, restart, recovery
10. Apply update > apply from adb
a. .\adb devices
b. .\adb sideload (path to magisk .apk)
i. Signature verification failed, install anyway
ii. Volume up to go to back arrow, reboot system now
11. Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
a. Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file transfer is on
12. DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
a. What I use: Safetynet universal fix, disableflagsecure (lets you screenshot netflix lol), and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
i. Install from storage
ii. Order I did it in was safetynet, then raven, then flag secure rebooting between each one but I'm not sure if it matters
b. Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click google play services, google play store, and carrier services (the square check box next to the name, make sure every check below when you open it as a dropdown menu is checked
c. Reboot phone
13. Now you can download whatever you want
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
https://forum.xda-developers.com/t/disable-flag-secure-magisk-module-v3-0-by-mehedi-hjoy.4490475/
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community. Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for the ****ty formatting, i copied this from a word document. I don't know how to paste the indents.
Click to expand...
Click to collapse
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.

optimumpro said:
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.
Click to expand...
Click to collapse
modded msm tool allows bootloader unlocking

Mrmcfeffers said:
modded msm tool allows bootloader unlocking
Click to expand...
Click to collapse
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.

optimumpro said:
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.
Click to expand...
Click to collapse
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.

Mrmcfeffers said:
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.
Click to expand...
Click to collapse
It's just a decription in thread name that is a bit misleading.
At first it appears like it can be done on locked bootloader.
And it's obviously not, as stated in your instruction point #2.
Otherwise, nice tutorial.

Mrmcfeffers said:
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
Click to expand...
Click to collapse
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?

jinncarry said:
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?
Click to expand...
Click to collapse
Don't use acca from f-droid. Acc from the official GitHub (https://github.com/VR-25/acc) is fine and works perfectly