Database Users

[GUIDE][ROOT][BUMP][TWRP] ImageprepGUI: Auto-script GUI Root+Bump+TWRP for LG G3

OWNERS OF OTHER LG G3 VARIANTS ARE WELCOME TO TRY!
IMAGEPREPGUI: AUTO-SCRIPT (GUI) FOR LG G3
Tested on: LG G3 D858HK​
FEATURES:
1. Rooting of your LG G3
2. Automatic (no-touch) extraction of aboot.img and laf.img from your KDZ or TOT firmware via the KDZ and TOT Extractor Tool by @bullghost
3. Download and installation of "bump'd" TWRP custom recovery for certain LG G3 models/variants
4. Sharpening Mod Script of Skin1980 included (to be manually flashed upon reboot to TWRP Custom Recovery) - this will "bump" your Kernel (boot.img) and will apply your desired sharpening level of the LG G3's display
5. "Bump" your boot.img (as part of the TWRP installation process of ImageprepGUI)
6. (Experimental): optionally "bump" your "un-bump'd" TWRP custom recovery.img
REQUIREMENTS:
1. Installed LG G3 Drivers for your device
2. Enabled Developer Options and USB Debugging on your LG G3
3. Backed up all your important files to your external storage or computer
4. Downloaded a copy of your KITKAT Firmware (in KDZ or TOT format)
5. Your custom recovery (TWRP) for your respective LG G3 model (Imageprep has download feature but only for certain models)
DOWNLOAD LINK:
ImageprepGUI v2.6: "installer" format. Double-click it to run. It will detect any previous installations of ImageprepGUI and delete them (as in ALL files within).
Imageprep Folder in Google Drive: this contains sub-folders of various LG G3 variants/models where you can manually download aboot.img, laf.img, and "Bump'd" TWRP custom recovery (recovery.img). Users can also download previous versions from here as well as corresponding video tutorials.
Downloadable Video Tutorial
Video Tutorial on YouTube
HOW TO USE:
1. Navigate to C:\ImageprepGUI and you will see ImageprepGUIvx.x.exe (where x.x is the version number). Run this app. It is recommended that you create a shortcut to your desktop or Windows taskbar for easy access.
2. Follow the step-by-step instructions.
DETAILED STEP-BY-STEP (HOW TO USE):
At the first screen with selections (radio buttons):
1. Acquire aboot.img and laf.img: you can choose to...
a. download from my Google Drive, or
b. have the full KDZ or TOT firmware handy and let ImageprepGUI extract them for you, or
c. manually run the KDZ and TOT Extractor tool and manually extract them
IMPORTANT: DO NOT SKIP THIS STEP IF YOU'RE GOING TO INSTALL TWRP. YOU MUST MAKE A SELECTION. SKIPPING THIS STEP IS OKAY IF YOU ARE ONLY ROOTING THE DEVICE.
2. Acquire "Bump'd" TWRP (recovery.img): you can choose to...
a. download from my Google Drive, or
b. have your own "bump'd" TWRP (recovery.img) handy
IMPORTANT: DO NOT SKIP THIS STEP IF YOU'RE GOING TO INSTALL TWRP. YOU MUST MAKE A SELECTION. SKIPPING THIS STEP IS OKAY IF YOU ARE ONLY ROOTING THE DEVICE.
At the next page:
1. You can choose to...
a. root ONLY (there are 2 methods available), or
b. skip rooting (if you are already rooted prior) and then proceed to TWRP installation, or
c. root+install TWRP in one go (there are 2 methods available, since there are 2 ways to root)
What's new:
June 24, 2015:
1. Fixed: COM Port not detected completely (reported by @re_di)
2. Fixed: pushing of BusyBox and Sharpening Script Mod happens only if user selects rooting, so those who select to ONLY install TWRP will not get BusyBox and Sharpening Script Mod (and without BusyBox, boot.img will not be "bump'd")
Older versions:
June 10, 2015:
1. There's a new rooting method by @digital-bug. It's supposed to address an issue for newer Lollipop firmwares that don't work well with rooting methods that make use of a Linux Shell Script. The effect is the same though. As the author notes, if you are already rooted prior, please DO NOT re-root. If you want to try this new method of if you want to switch between rooting methods, please back up your files and re-flash your device.
2. ImageprepGUI version 2.5 already includes the new rooting method. Users now have two choices of rooting.
3. Re-enabled the option for users to try and "bump" their un-"bump'd" TWRP Custom Recovery (recovery.img). This is not a 100% guarantee, but choice is always good so I put it back there.
June 08, 2015:
1. GUI Enhancement: added "Select Options"
2. GUI Enhancement: search for file window (no longer need to navigate to Windows File Explorer to copy-paste Image Files)
3. Additional options for acquiring KITKAT Image Files (aboot.img, laf.img): users are not tied to only one method of acquiring these Image Files. They can choose to download them or use their own copy
4. Users can now open a new session of the KDZ and TOT Extractor Tool (for manual operation)
5. Users can select various options to manipulate how ImageprepGUI will behave to their liking, such as skipping certain sections of the process
June 01, 2015:
1. Changed the order of steps. Extraction of firmware (for aboot.img and laf.img) and recovery.img (TWRP "bump'd" custom recovery) come first before rooting and TWRP installation.
2. Put back "installer mode".
3. Pushing of files is in GUI mode. Only the actual booting to Download Mode and rooting are the ones that remain in DOS (command line) mode.
May 26, 2015:
1. Rooting portion of the script is non-GUI for the moment (GUI is not rooting the device properly and is currently being investigated)2. Disabled "installer" and delivering the file via "zip" file instead (after downloading, extract the entire "ImageprepGUI" folder to your Drive C:\)
2. Disabled "What do you want to do today?". This means that users will have to go through the entire "complete" process, start-to-finish
May 22, 2015: addressed (hopefully) an issue where the LG G3's COM port is not detected, causing ImageprepGUI to quit/exit. Please test and let me know if this release works now.
Update Notes:
June 10, 2015 Update: ImageprepGUI v2.5 Released
Thanks to @digital-bug for sharing the new method of rooting the LG G3. This new approach has the same end-result and effect as the existing methods. Where it's different is how it is being executed. Instead of a Linux Shell Script, it makes use of an "indirect" input (like "piping"), as if the user manually entered the command via a keyboard.
AS ALWAYS, BACK UP FIRST BEFORE TRYING!
Update Notes for Previous Versions:
June 08, 2015 Update: ImageprepGUI v2.4 Released
Thanks for all your feedback and support!
This new release has some GUI Enhancements as well as an added window: "Select Options". This way, users can now influence how they want ImageprepGUI to behave. For example, if users only want to root their device, they can simply select "Skip this step" under "Image Files Acquisition" as well as "TWRP Custom Recovery Download". Mix-and-match to your liking!
There is also a new rooting method, which aims to address rooting issues for LG G3's that sport the newer firmware versions. We'll see if this new method can be added to ImageprepGUI.
Video tutorial is still in the works for this new version. I inadvertently deleted a copy of my LOLLIPOP KDZ firmware so I have to download it again in order to reflash and record a new video.
June 01, 2015 Update: ImageprepGUI v2.3 Released
Again thanks for those who have tried and provided feedback!
Some users reported that the rooting phase/portion of the script will continue towards completion, even if the device was not booted to Download Mode properly. I have tested since version 2.2 and didn't encounter the issue. Nevertheless, I modified it a bit so that only the rebooting to Download Mode, and the actual rooting, will be run in MS-DOS (command line) mode.
Also, I have reversed the order of steps. Extraction of image files (from a full KDZ or TOT firmware) as well as TWRP download (or manual copy-paste to the "twrp" sub-folder) will come first. Once these two steps are done, then "Rooting" and "TWRP installation" will be the next steps. This seems to be a more logical order: prepare the needed files first, and then run the rest automatically.
May 26, 2015 Update:ImageprepGUI v2.2 Released
Thanks for those who tried ImageprepGUI (a.k.a. Imageprep v2.0) and for reporting issues with it.
The rooting script does not run properly in GUI mode. Since I don't want you guys to wait, I stripped down the GUI piece of the "rooting" stage for the meantime until I get it all figured out. There's a lot going on (personal life) at work so I anticipate my progress to be slow.
Also, I momentarily removed the option of running only portions of the "complete" process. In version 2.2, users will have to go through the entire process from start to finish. I'm going back to the drawing board to design a better flowchart of events so as to further reduce problems that may inadvertently be caused by human error.
In version 2.2, there is no "installer" mode. It's just going to be a plain ".zip" file. When you open the ".zip" file, you will see a folder named "ImageprepGUI". Extract the folder itself to your Drive C:\ (so effectively, all the contents will go along with it).
May 11, 2015 Update: Back on Track: ImageprepGUI (Imageprep v2.0)
I've been out for quite a while due to family (personal matters) and work (gunning for a promotion!) and would like to apologize for my absence. But rest assured I continuously worked on Imageprep whenever I had the time. And so, I now present to you ImageprepGUI. This is my first attempt at programming for a GUI app/software so please go easy on this.
DISCLAIMER:
This product is not an official LG software and is therefore not endorsed by LG Electronics in any way. As such, this is a 'try-at-your-own-risk' approach. Please make sure to back up your important files when trying this for the first time. I take no responsibility for any undue outcomes resulting from the use of this software.
ABOUT IMAGEPREPGUI:
Imageprep is NOT a one-click application, and it is intentionally created to be so. Because its objective is to support multiple models/variants of the LG G3, it is developed in a way that the process will pause or exit if something is "off", so expect that there will be pop-up messages every now and then. Think of them as "security measures" to reduce the mistakes from a user point-of-view. In other words, Imageprep takes a balanced approach to automation, features, and "mistake-proofing" in order to provide a virtually seamless experience.
In order to support multiple LG G3 models/variants, Imageprep involves the ability to download TWRP Custom Recovery (recovery.img) for your specific LG G3 model/variant. If you are not comfortable with what is being downloaded, or if your device is not listed, there is an option to place a copy of your TWRP custom recovery (recovery.img) manually. Other image files (aboot.img and laf.img) will be extracted via the "KDZ and TOT Extractor Tool" which will be done automatically.
Outside of downloading and/or extracting, the rest of the actual rooting process is done automatically, just like how Imageprep was in its early stages.
FINAL WORDS:
Having no prior background in programming, this is my first-ever attempt to create a GUI application. While I have tested this application extensively and to the best of my abilities, nothing is perfect. Hence as a general rule: always back up your important data before embarking on activities such as this!
Imageprep is continuously evolving and is therefore a work-in-progress so I am open to suggestions, requests to add more LG G3 models/variants, and even small talk via chat or forums. I always strive to visit the XDA forums to respond to queries or Private Messages whenever time allows me.
I hope this application helps you in every simple way. Enjoy!
With kind regards from the Philippines,
- topet2k12001 @xda[/URL]
CREDITS:
@Chainfire for SuperSU.
@autoprime for his tutorial on “Manual Firmware Update” to keep root/”bump’d”, and for guiding and giving clarity by explaining what happens in the background when I conducted my experiment.
@Skin1980 for allowing me to use the commands from his Sharpening Script Mod (for sharpening options) as well as the commands for "live bumping" ("bumping" on-the-fly) of the boot.img.
@jcase for putting up the the “Stump” thread. Without “Stump” we would not have enjoyed “root” functionality of the LG G3.
@thecubed for “Bump”. Such a wonderful tool. It opened the doors of customization for the LG G3.
@bullghost for the “KDZ and TOT Extractor” tool. This nifty tool allowed us to extract the important components (partitions) of the LG G3’s firmware.
@mronly1love for “Bump Windows version”. It is through this tool that I was able to “bump” my TWRP 2.8.4.0.
@hoangnova for his post about the partition layout of the LG G3. It helped me confirm how I should flash aboot.img.
@itsbighead for his post that helped me understand what aboot.img, laf.img, and sbl1.img meant, and for the same post that explains what causes the LG G3 to boot into an error screen that says “certificate verify”.
@gzkenny from bbs.gfan.com for “D858HK TWRP 2.8.4.0”. It is a purely Chinese website and I actually spent time understanding everything even with Google Translate. I’m not sure if he/she will able to read/understand this but I thank him/her too.
@6ril1 for sharing to me how to "bump" a boot.img. Also thanking him for sharing a secret/tip, which actually inspired me to start learning how to program (I'm starting with simple scripts for now). This is the reason why I was able to come up with "imageprep".
@Unjustified Dev for sharing a method of rooting the Android Lollipop without downgrading to Kitkat.
@zurny for proof-reading the guide and pointing out clerical errors or any other errors that may cause future problems for the readers.
@DE52 and @ ravi.vydianathan for spreading the word about this thread and helping to explain the logic to fellow XDA members
@avicohh for automating the rooting commands via a script
@jac10000 for modifying the scripted rooting commands to add TWRP
@somboons for One Click ROOT+TWRP Recovery for Lollipop Stock Firmware

1. EXTRACT
This is a "sub" tutorial or how-to on extracting the necessary image files from an LG G3 firmware (KDZ or TOT)
In this example, we are extracting Lollipop system.img, boot.img, and modem.img based on the "Kitkat Downgrade" method.
For the "No Downgrade" (Manual and/or "Imageprep) method, it's the same procedure...only different files to extract.
​
1. Extract “system.img”, “boot.img”, and “modem.img” from your Android Lollipop firmware via the “KDZ and TOT Extractor”.a. Download the KDZ and TOT Extractor from @bullghost’s thread.
b. The file is in .zip format. Extract/uncompress it to a folder/location of your choice. This will be your working folder.​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
c. Put a copy of your Android Lollipop firmware in the working folder. At this point, the working folder should look like this:​
d. IMPORTANT!!!! Make sure that your File Explorer is set up to show “File Name Extensions”. In Windows 8, click on “View” and check “File name extensions”.​
e. Run the Extraction Program and select the Android Lollipop firmware.​
f. Extract the contents of the KDZ file. Basically, we want to get the DZ file from within it.​
g. Now we will extract the contents of the DZ file. Notice that your working folder will be filled with files, ending in “.bin”.​
h. Next is to merge the “system” partial files to create “system.img”.​
i. The resulting “system.img” file is inside a newly-created sub-folder named “merge-output”.​
j. Copy boot_xxxxxx.bin and modem_xxxxx.bin and paste them inside the “merge_output” sub-folder.
NOTE: the numbers may vary on different LG G3 variants. It doesn’t matter; just do it!​
k. Rename those files to “boot.img” and “modem.img”. You’re done with Step 1!
NOTE: If you missed Step 1.d, you will end up renaming only the file name as boot.img or modem.img but the file extension will still be “.bin”. That’s why you need to follow Step 1.d!!!​

2. Transfer
March 15, 2015 Update: these are the steps from the original "No Downgrade" Manual Approach. There is now an automated script called "Imageprep" that makes the process more convenient for you by entering only a single command in the Android Terminal Emulator. Head over to Post #153 for the details!
2. Transfer Needed Filesa. Save original copies of the files in your External Storage (removable microSD).i. Android Lollipop system.img, boot.img, and modem.img
ii. Sharpening Mod script
iii. “Bump’d” TWRP
iv. Tools for flashing the extracted .img files​b. Using a File Manager, create a folder named “flash2” (without the quotes) in your Internal Storage.
c. Place a copy of Android Lollipop system.img, boot.img, and modem.img inside “flash2” folder.
d. Place a copy of the following to your Internal Storage:i. The “tools for flashing the extracted .img files” (Flash2Boot.zip, Flash2Modem.zip, and Flash2System.zip)
ii. “Bump’d” TWRP
iii. Sharpening Mod script​e. Last chance to install “bump’d” TWRP recovery! Please make sure you do this!​

3. Flashing
March 15, 2015 Update: these are the steps from the original "No Downgrade" Manual Approach. There is now an automated script called "Imageprep" that makes the process more convenient for you by entering only a single command in the Android Terminal Emulator. Head over to Post #153 for the details!
3. Flashinga. Power off the device
b. Boot to TWRPi. Press/hold volume down and power.
ii. At the “LG Life’s Good” boot screen, release for 1 second and then press/hold volume down and power again. You will see a “Factory Reset” screen.
iii. Select “Yes”. You will do this twice.
iv. Device will boot to TWRP custom recovery.​c. Flash the “.img” filesi. In TWRP, select “Install”. Look for Flash2System.zip and flash it. This will take some time.
ii. Repeat for Flash2Boot.zip.
iii. Repeat for Flash2Modem.​d. Flash the Sharpening Mod script. Select your preferred sharpening level. At the end of the wizard, the script will “bump” your Android Lollipop boot.img.
e. At the screen where it says “Finished”, click “Next”.
f. In this screen you will be asked to reboot. Un-select the box for rebooting and exit the script! If you do not un-select, it’s possible that TWRP will skip the prompt to install SuperSU!​
g. Exit the TWRP custom recovery by selecting “Reboot” and then “System”.
h. You will be prompted that “SuperSU is not installed” and you will be offered to install it. Swipe the slider found at the bottom to install it.
i. It might take a while for the first reboot especially if you have a lot of user apps installed prior.
j. You’re done. Congratulations!​

Troubleshooting and Q&A
Q: No radio signal (wifi, 2G/3G/4G/LTE)
A: The Lollipop modem.img was not flashed because you forgot to rename the modem_XXXXX.img as modem.img. Or, you forgot to put modem.img in the "flash2" folder. Remember, the Flash2Modem.zip script is programmed to look for modem.img in the "flash2" folder.
A: You have various versions (Kitkat and Lollipop) of boot.img, modem.img, and system.img and you accidentally mixed them up. Make sure that you organize your files properly (put them in folders) and then try the process again.
Q: I get the “certificate verify” error when booting to Android.
A: The Lollipop boot.img was flashed successfully, but was not “bump’d” because you forgot to flash the Sharpening Script Mod BEFORE booting to Android as per the tutorial. Also, make sure as well that at the end of the Sharpening Mod Script, un-select the box for rebooting. You should reboot from TWRP’s main reboot menu and not from the Sharpening Script Mod.
A: You have various versions (Kitkat and Lollipop) of boot.img, modem.img, and system.img and you accidentally mixed them up. Make sure that you organize your files properly (put them in folders) and then try the process again.
A: You got adventurous and flashed the Lollipop aboot.img to the device.1. Hopefully you had a “bump’d” TWRP before you followed this procedure.
2. Extract the Kitkat aboot.img from your Kitkat KDZ (the Kitkat version that you were on prior).
3. Power off the device.
4. Boot into TWRP (yes you can boot to TWRP even with that error – as long as you had TWRP installed prior).
5. Plug the device to your computer. The device will open/show in Windows File Explorer. Transfer the Kitkat aboot.img to your Internal Storage.
6. Power off and then boot to TWRP again, and then reflash aboot.img.
7. You may end up booting properly to Android but losing “bump’d” hence, you will lose TWRP. That’s fine.
8. Assuming you are able to boot properly to Android, install Android Terminal Emulator.
9. While in Android, install the “bump’d” TWRP via Terminal Emulator, following the steps from the “Bump” thread.
10. Power off the device and boot into TWRP.
11. Flash the Sharpening Mod Script. It will “bump” your Lollipop boot.img properly.
12. Reboot to Android.​Q: After following the procedure, the phone boots to LG "Life's Good" but after that, I don't see the splash screen/boot animation. Instead, I just see a black screen with "security error" written in the middle of the screen.
A: The Lollipop boot.img was not flashed because you forgot to rename the boot_XXXXX.img as boot.img. Or, you forgot to put boot.img in the "flash2" folder. Remember, the Flash2Boot.zip script is programmed to look for boot.img in the "flash2" folder.
Q: I seem to go into a “boot loop” to TWRP.
A: Common mistake is that people accidentally flash recovery.img to the “Boot” partition, or flashing boot.img to the “Recovery” partition. Reflash the proper Image file to the appropriate partition. If the problem persists, @autoprime created a flashable zip that will fix this problem.
Q: I get the “certificate verify” error when booting to Download Mode, or I can’t boot to Download Mode.
A: You got adventurous and flashed the Lollipop aboot.img, laf.img, or sbl1.img (or other partitions that were not covered in this tutorial) to the device. See long answer from above.
Q: How do I "bump" my custom recovery (TWRP)?
A: D858HK users: you can download a copy from the "Requirements" section in Post #1. Popular variants: the more popular variants (like the D855 - International variant) are very well supported; please search for TWRP as a keyword under the LG G3 section. Less popular variants: there are two (2) tools that you can use. One is "Bump Windows version" and another is "Open Bump". It's easy; just drag-and-drop your custom recovery image (TWRP) to bump.exe (for Bump Windows) or open_bump.py (for Open Bump).
Q: Okay, now I have "bump'd" my custom recovery. How do I install it? I obviously can't flash it via TWRP because I don't have it installed yet.
A: There are two ways to do it. One is done manually. You need to be rooted (Kitkat) and should have Android Terminal Emulator installed. And then you will have to enter some commands. The other way is to do it via "Flashify" (it's an app). For details and instructions, please visit the official "Bump" thread; Post #1.
Q: Do I need to have a custom recovery (TWRP) installed? There are not a lot of custom ROMs for the D858HK anyway so it doesn't make any sense.
A: Yes, you do. Even if you do not intend to install custom ROMs. Installing custom ROMs is just one of the features of a custom recovery such as TWRP, but remember - its main purpose is to provide you with advanced options of recovering your device in the event of a "brick" situation. I have had many instances when I totally "bricked" my device and was saved because I created a full system backup using TWRP. Oh, and make sure that you have installed TWRP and created a full system backup while you are in Android Kitkat!
Q: Do I need to "bump" my current (Kitkat) boot.img and flash it to the device too, before I follow this tutorial?
A: So I downgraded back to Kitkat and tried upgrading again. One with a Kitkat "bumped" boot.img, and another without (stock). In both scenarios, the device was upgrade properly (with root, "bump'd" boot.img, and "bump'd" TWRP). I therefore conclude that it doesn't matter. When you update to Lollipop as per this tutorial, you will end up overwriting the Kitkat boot.img with the Lollipop boot.img and "bumping" anyway (at the part where you flash the Sharpening Script Mod).
Q: There are new threads for rooting Lollipop without downgrading. Here and here. How is your method different?
A: Yes I have read them as well. Great guides, actually. However, those are strictly for rooting only. No custom recovery, no "bump". If you want to maintain "bump'd" boot.img and "bump'd" recovery.img (custom recovery such as TWRP), you will still end up having to follow the steps in this guide - downgrade to Kitkat first, extract Lollipop KDZ firmware, and flash only system.img, boot.img, and modem.img. If you are not tinkering around and are confident enough that you won't do adventurous things with your device, it's okay not to have a custom recovery. Therefore, merely rooting your device would be sufficient. In my case, I have "bricked" my device multiple times and was saved by custom recovery, so I would say I need it.
I asked the question in one of the threads: http://forum.xda-developers.com/showpost.php?p=59328257&postcount=9
But eventually, I already saw the answer. Fellow XDA member (Recognized Contributor) @6ril1 also confirms this: http://forum.xda-developers.com/showpost.php?p=59325441&postcount=55
6ril1 said:
Bumps (kernel and recovery) needs KK bootloader (aboot partition and maybe others little partitions that constitute bootstack in KK version :aboot,tz,sbl1,rpm,persist,laf,dbi) for booting. And if you downgrade bootstack you have to bump kernel too for being able to boot firmware from KK bootsack.
You can extract LP recovery(with kdz extractor tool) and reinject it for returning to LP rooted , as you were before trying to inject bumped TWRP, or you can try to downgrade bootstack and bump kernel for being able to use custom recovery on the stock LP.
Click to expand...
Click to collapse
So, I created another guide (within this thread - see First Post for the link) on how to achieve that.
Q: After following the how-to guide, I lost my Download Mode! Whenever I try to go to Download Mode, it just hangs and show a "Certificate Verify" error!
A: This happens when you followed the "No Downgrade" approach and did not flash Kitkat versions of the "Boot Stack" (persist.img, dbi.img, laf.img, sbl1.img, rpm.img, and tz.img). The how-to guide for "No Downgrade" approach has been updated accordingly to include this step. Those who followed the "Kitkat Downgrade" approach do not need to flash these image files anymore because they are already on Kitkat version.
There is an easy way to do this. XDA member @6ril1 created a TWRP-flashable zip file to automate it. The zip file was originally created for the D855, but you can replace its contents with ".img" files for your LG G3 variant. Just follow the instructions in the link provided.

Well done, topet. Very very much appreciated your hard work, it must took you long time to finish the write up, sacrifice your weekend joyful time. Again, thanks a lot.
Sent from my LG-D858HK using XDA Free mobile app

supralex said:
Well done, topet. Very very much appreciated your hard work, it must took you long time to finish the write up, sacrifice your weekend joyful time. Again, thanks a lot.
Sent from my LG-D858HK using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your appreciation! If you get this to work please let me know.

topet2k12001 said:
Thanks for your appreciation! If you get this to work please let me know.
Click to expand...
Click to collapse
sure, I will probably do it after the weekend
Sent from my LG-D858HK using XDA Free mobile app

You're simply the best...
Thank you for your fine, hard work and very detailed documentation. :good::good::good:
My D858HK is "Lollipop-Rooted" now.
Thank you, thank you, thank you!!!

mystery007 said:
Thank you for your fine, hard work and very detailed documentation. :good::good::good:
My D858HK is "Lollipop-Rooted" now.
Thank you, thank you, thank you!!!
Click to expand...
Click to collapse
Glad to hear that, @mystery007!

Can't wait for feedback if this baby will accept CM12.

ch4dwick said:
Can't wait for feedback if this baby will accept CM12.
Click to expand...
Click to collapse
Hi @ch4dwick,
CM12 has already been out for the LG G3: http://forum.xda-developers.com/lg-g3/orig-development/rom-cyanogenmod-12-official-nightly-t2995524
...that's for the D855 variant (the International variant).
I believe that the D858HK variant will also work, but it won't have the dual-SIM functionality. See this thread for an explanation: http://forum.xda-developers.com/showthread.php?t=2297570

I tested your solution on D855 euro 32go + 3 Go ram and I have android L but no wifi work

i tried this process about a week ago without the sharpening zip bit at the end. Everything goes smooth, system img takes 5 min to flash, but it flashes successfully along with the modem and boot zips. I get prompted to install SU prior to rebooting and do so. the addition of the sharpening zip seemed to change nothing as the i get the same outcome as i did without it . when rebooting, i get a small reddish *security error* logo in the middle of the screen for 3 seconds and then the phone shuts off. any idea why ? im on the d852 variant

Has anyone tried this for AT&T?

jac10000 said:
I tested your solution on D855 euro 32go + 3 Go ram and I have android L but no wifi work
Click to expand...
Click to collapse
Hi @jac10000,
Let's try to troubleshoot: can you try 3G/4G/LTE instead and see if it works? If it does, then it means you were able to flash modem.img properly and the problem is probably the Internet connection. If you still can't go online with 3G/4G/LTE, please try reflashing the modem.img. Also please make sure you are flashing the modem.img that you extracted from your firmware, and not a modem.img that you got somewhere else.
tmjm28 said:
i tried this process about a week ago without the sharpening zip bit at the end. Everything goes smooth, system img takes 5 min to flash, but it flashes successfully along with the modem and boot zips. I get prompted to install SU prior to rebooting and do so. the addition of the sharpening zip seemed to change nothing as the i get the same outcome as i did without it . when rebooting, i get a small reddish *security error* logo in the middle of the screen for 3 seconds and then the phone shuts off. any idea why ? im on the d852 variant
Click to expand...
Click to collapse
Hi @tmjm28,
I did encounter this particular error when I was discovering everything, so I have an idea. Based on my experience, it is caused by one or all of the following:
1. Having a full Lollipop firmware flashed to the device. So even if you "bump" the boot.img (for example, via the Sharpening Script Mod), it won't work. You must flash ONLY system.img, modem.img, and boot.img (which will be "bump'd" when you flash the Sharpening Script). In technical terms, the reason why this process is done manually is so that some other key partitions will stay as "Android Kitkat" (laf.img, aboot.img, sbl1.img, tz.img, rpm.img and some others). If you happened to flash a full Lollipop firmware/OS before you tried this procedure a week ago, then those key partitions were already overwritten and will now become "Android Lollipop", whereby "bump" can't work. So I would propose a full downgrade to be sure that everything will be back to Kitkat and when you follow this process again, you will have assurance that you are flashing only the Image files specified in the guide.
2. The boot.img of D852 can't be "bump'd" properly by the Sharpening Script Mod. You may try other methods of "bumping" your boot.img (please search for Open Bump, or try the Bump Windows version that I used to bump my TWRP 2.8.4.0 - I put a hyperlink to that thread in the first page, under "Requirements").
3. You might have had multiple copies of boot.img and you got confused which one you flashed. It happened to me when I was experimenting - sounds dumb, I know, but it happens.
Now, the thing is I don't know how exactly you flashed your device a week ago. Therefore I won't be able to trace the actual cause. I would suggest starting from scratch (full downgrade to Kitkat, and then start over and follow the procedure).

I'm expecting someone to have actually done it in the future. I'd do it myself but I'm still busy at the moment to be actually redoing stuff from scratch if I fail to succeed in flashing CM12 on the D858HK. Oh, well, maybe later this year.

Wow, very much appreciate the time and effort you put not only into answering my question but also all the other ones! I'm almost positive I did a full factory reset using the LG flash tool ( tot dll) last week when I attempted to flash the zips, but I will try it again and see if it works. I believe your response labeled number 2 is what is holding me back. As of right now I have no idea what bumping TWRP means, therefore I will look into it further and attempt the process again after I understand what you mean by number 2?

just finished upgrading, and its work.. thanks dude for your hard work, really appreciate.....
but still confuse, what is sharpening mod for? and whats the best value number? sorry for my stupidity, just newbie in smartphone...
thanks again, and keep up the good work.

Wow thanks for this howto, I can confirm this worked on my D852G! Everything looks good so far!

[ROOT] [STOCK] [TWRP] Root Stock Firmware of Any Modern Sony Device

At first I created a guide about rooting stock Marshmellow of Sony Xperia Z5 Premium. After some time I realized that it may be useful to users of virtually any recent Sony phone or tablet, so here is my Sony Cross-Device general rooting thread. I will mostly copy-paste bits from my previous guide, but using renewed screenshots and firmwares'/tools' versions.
Please write back in this thread which model of Sony phone you was able to root with the help of this guide.
This guide does not work for MediaTek devices.
INTRODUCTION
Sony historically provides own versions of Android OS, modified for Sony phones. These firmwares with added Sony apps are known as a stock firmware, contrary to vanilla Android developed by Google.
This guide will lead you through the process of rooting the stock firmware for your particular Sony phone. At the same time, your phone will be supercharged with TWRP recovery image, a useful tool for things such as an installation of system behavior altering apps to a whole device backup including all system partitions.
WHY ROOT?
Sony, just as any other smartphone vendor, ships its devices without the ability to alter inner system workings of Android OS. Technically speaking, default OS only allows use of non-administrator accounts, which have access only to their own user space.
Rooting is a process of allowing access to the administrator account, also known as root. This enables a possibility to alter/remove system parts of the OS: apps, settings, behaviors. For example, with root access you can block ads system-wide, from apps to browsers.
WHAT ARE CAVEATS
During the rooting procedure, the unique DRM keys will be removed from the phone. These keys are used to make some proprietary Sony features work, such as X-Reality for Mobile, camera denoise filter etc.
During the course of this guide a so called DRM fix will be apllied, which effectively emulates DRM keys, so many Sony features remain in working condition, even without actual keys. Some features, such as Widevine, will not work but majority of typical users won't even notice this. I think most of you even don't know what Widevine is.
However, in this guide I will present a way to backup your DRM keys, if you still think you need them. I will not deep dive though, since I never bothered with DRM keys export/import procedure myself and have no experience in doing this.
Some apps will refuse to work on rooted device, Pokemon Go and Android Pay are couple of notorious examples. Research your apps for rooted device compatibility. If you find such app and cannot live without it, don't root your phone.
ACCOLADES
The rooting of Sony stock firmware will not be possible without the work of these brilliant community developers:
@Androxyde — Flashtool
@IgorEisberg — XperiFirm (integrated into Flashtool)
@Dees_Troy et al. — TWRP
@Chainfire — SuperSU
@topjohnwu — Magisk
@tobias.waldvogel — Kernel repack script and DRM fix
@zxz0O0 — iovyroot
@rayman — TA Backup v2
STEPS
The whole process of rooting your stock firmware is divided into the following steps:
Getting your phone recognized by your computer (driver installation).
(optional) Backup your DRM keys.
Unlocking a bootloader.
Flashing stock firmware with Flashtool.
Repacking and flashing a kernel.
Installing SuperSU or Magisk.
(optional) Restore your DRM keys.
Optional tasks.
After the completion of this guide, your phone contents will be completely erased, so you may want to backup all what is important to you to some external locations. External microSD card will not be erased, so you may copy your stuff to it. If you are already use some rooted Android, you may want to use some specialized tools like Titanium Backup or like. TWRP also have a nice backup features, if you have one already installed.
Also, use Sony's own Backup & reset tool from the settings. You may backup your local contacts, messages and much of such stuff directly to your microSD card. After the rooting, same tool may be used to restore some (or all) of these things back.
I usually make a whole backup with TWRP, Titanium Backup for user apps and the Sony's Backup & reset for conversations and call logs.
The guide was developed using Windows 10 Pro 64-bit and Sony Xperia Z5 Premium Dual-SIM E6883 official model for the Russian market.
Let's go.
1. GETTING YOUR PHONE RECOGNIZED BY YOUR COMPUTER (DRIVER INSTALLATION)
During the course of this guide, your phone will comminicate with your computer in Fastboot and Flashmode connection modes. When connected in these modes, for the phone to be properly recognized by a computer, you have to provide special drivers. Thanks to Flashtool creators, it comes bundled with generic drivers compatible with all recent Windows operating systems, so at first you should install Flashtool. You can get installer from the official website.
Next, you should install Fastboot and Flashmode drivers for your phone.
One caveat here however, these drivers are not from a "recognized Windows developer", that is they are not Windows-certified, so to get them installed on Windows 8/10, you should reboot with the disabled driver signature enforcement. Use Google to know how to perform this.
Once booted in the aforementioned mode (or in a regular mode if you are still on Windows 7), proceed to the actual driver installation. The drivers are packed into the Flashtool\drivers\Flashtool-drivers.exe executable, but it didn't work on my system, perhaps because it is 64-bit (but feel free to try it yourself), so I simply unarchived it with 7-Zip (right-clicked it and chose 7-Zip > Extract to "Flashtool-drivers"). I got a Flashtool-drivers folder, which contained all the drivers from the executable.
Once drivers are unpacked, connect your phone in a Fastboot mode. Recent Sony devices can boot in Fastboot just like this: shutdown the phone, press and hold Volume Up rocker button and connect USB cable to the phone while the other end is connected to a running PC. The phone's LED will turn blue shortly. That's it, you are in a Fastboot mode. Open Device Manager (Win + X, Device Manager) and check if there is some unknown device (with the name S1Fastboot or something like this).
Double-click this unknown device in the Device Manager, click Update Driver..., then Browse my computer for driver software, and choose the Flashtool-drivers folder created earlier with 7-Zip (leave Include subfolders checked). Shortly you will get a red warning dialog window, which inform you that this driver doesn't have a proper signature:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very scary. Just proceed with the install despite all the red flags, it's safe.
Once Fastboot driver is installed, plug out the USB cable off the phone and connect it in a FlashMode mode. This is done just like for Fastboot, but in this case you should press and hold Volume Down rocker button during the cable plugging in. The LED in this case will be green and not blue. The procedure to install the driver is exactly the same.
After the successful installation, try to reconnect the phone in these modes again couple more times to make sure all devices get properly recognized by Windows. If all seems good, proceed to the next step.
2. (OPTIONAL) BACKUP YOUR DRM KEYS
I encourage you to skip this step, but if you feel like you should do this anyway, here is some info.
There is a tool called iovyroot, with which you can backup your DRM keys from an unrooted phone, but at the time of the writing it doesn't support latest firmwares. It does support a lot of older firmwares so it may be useful to not upgrade your phone before checking up this tool.
If you're into this backup DRM thing, go to the original thread, download the latest version and check if it is working for you. For now I just skip this step. Basically, you want to download the zip, connect your phone in USB Debugging mode, run the tabackup.bat script and see the output.
Some people suggest to use the newer Universal (Dirtycow-based) TA Backup v2 tool instead of ageing iovyroot to backup you keys. Please check the official thread to get instructions (linked in the previous sentence).
I will not cover DRM keys extraction/restore in details, since I never did it, so I don't want to write about something I haven't myself performed. Please check corresponding threads.
Note that most proprietary Sony features will work even without DRM keys, such as X-Reality for Mobile, camera denoise filter and some others. DRM fix will be covered later in this guide. Some features will not work with DRM fix, Widevine for example. Most users will not even notice these.
3. UNLOCKING A BOOTLOADER
Sony does provide its own guide. It is a plain and simple and — good news! — if you have followed the previous steps, you just got all the prerequisites covered!
4. FLASHING STOCK FIRMWARE WITH FLASHTOOL
Now we will flash the latest available Sony firmware to the phone. In this step it will be untouched vanilla firmware, without root yet.
The Flashtool was installed on the completion of the first step, so let's start it. If you are on 64-bit Windows, start Flashtool64 (there is a shortcut in the Start menu). It does require administrator privileges.
Once you are in Flashtool, at first you need to obtain the most recent official stock firmware from Sony. Press the "XF" icon (the right-most one in the toolbar) to start XperiFirm. This is where it is:
The window will open, choose your phone from the left part of the window, then choose your particular model and after that choose your market and operator from the right part of the window. The entry will become highlighted and shortly there will be some info in the last column (Latest Firmware). This definition will be also in the right-most part of the window just under the phone thumbnail, click on it. Not a brilliant design decision, but that's it. Here is a screenshot for your reference:
If there are multiple firmwares available, pick the more recent (typically the top-most). The new window will pop up, press Download. The stock firmware will be downloaded to your computer and unpacked.
Once the download is completed, close all XperiFirm windows to return to the main Flashtool window. Flashtool will begin a creation of the .ftf file from the downloaded resources which will be used for a (subsequent) flashing. FTF-files are similar to ZIP-files, and may be opened with 7-Zip. For example, I've got E6883_32.3.A.0.376_1299-4828_R3D.ftf after the completion of this procedure. Flashtool places firmwares in the C:\Users\<Your Windows Username>\.flashTool\firmwares.
Now, once the stock firmware is downloaded, packed into .ftf and ready to be installed, let's do this.
Disconnect and switch off the phone for now, physically extract microSD card (if any) and press the left-most button on the Flashtool's toolbar (the "Lightning" one) and choose Flashmode. The Firmware Selector window will appear with a selected default folder and list of all firmware available for a flashing. I've got a single entry, the firmware I just downloaded. Before actual flashing, you can check some checkboxes from the Wipe section, I usually check all to start clean (all the data on the phone is erased). Once again, just to be safe, extract the microSD card from the phone at this moment. It is not needed for a flashing anyway. Here is how the window looked to me:
After all is set up, press Flash. The flashing process is not yet begun, since at first Flashtool just prepares firmware for a flashing.
After a while, a window will appear which will ask you to connect your phone in the Flashmode mode. With your phone off, hold the Volume Down button, connect the USB cable. Once Flashtool detects the phone in the Flashmode mode, it will start the actual flashing automatically. You may release the Volume Down button and go get some snack. The flashing will take some time.
After the completion of the flashing procedure, you'll get a stock Sony firmware installed, and now it is perfect time to proceed to the next step. You may leave your phone off at this moment, but if you are curious, start it up and check if the new Android is actually there. Note however that first start after the firmware installation takes a long time.
5. REPACKING AND FLASHING A KERNEL
Now it is a most interesting part: repacking and flashing a stock kernel. This procedure will allow the actual rooting.
To get the stock firmware rooted, you need a way to install SuperSU or Magisk. These are tools which enable root access to the Android system. To install them, you need TWRP. To run TWRP, you need a kernel, which supports both TWRP and your Android version.
Thankfully you can extract the kernel from the .ftf file, prepared by Flashtool earlier. Then you repack it, integrate TWRP (and DRM fix) into it, and finally flash it to your phone back modified. Sound like a complex task but it's definitely achievable. I did it multiple times mostly without any issues.
At first you should extract the actual kernel from the .ftf file. Reminder: it's in the C:\Users\<Your Windows Username>\.flashTool\firmwares folder and may be titled E6883_32.3.A.0.376_1299-4828_R3D.ftf or something like this. Open it as an archive (right-click on a file, 7-Zip > Open archive) and extract kernel.sin. It's your phone's packed kernel.
If it is packed, obviously you need to unpack it. Thankfully the almighty Flashtool can do this. Open Flashtool, navigate to the Tools > Sin Editor, select a kernel.sin you've just extracted and press Extract data. As a result, you'll get a kernel.elf file in the same directory where your packed kernel is residing. As you may have guessed, kernel.elf is an unpacked kernel. It can be modified, repacked and flashed back to the phone. Let's do this.
You will need a Stock kernel repack script from @tobias.waldvogel. Here is the original thread. Author of the script mentioned, that now it is hosted on GitHub, so let's just grab the latest version from there. Here is the link to the repository. In the upper-right corner there is a Clone or download button you may push it and choose Download ZIP from the menu. The script will be downloaded.
Once the contents of the zip-file with script are extracted to some directory, copy the kernel.elf there and summon command prompt in this directory (right-click in the empty space of this folder in File Explorer with the Shift button pressed and choose Open command window here).
In the command line type the following:
Code:
rootkernel.cmd kernel.elf boot.img
You'll get some questions about adding some features/tools to your kernel, feel free to answer "Yes" (type Y) to all of them. Screenshot for your reference:
If all went smoothly, you'll get a repacked kernel, boot.img in the script folder, supercharged with TWRP and DRM fix, and most importantly, which also supports rooting. Now it is time to flash it to your phone.
ATTENTION! Since the script is mostly unsupported, when new firmware get released, its kernel modules are not getting automagically added to the script package. You will get "Skipping TWRP recovery. No kernel modules for 3.10.84-perf-XXXXXXX available" error due to this. But don't worry, you can extract the required modules yourself from the firmware.
1. Open the FTF-file (firmware you downloaded) with 7-Zip, and extract system.sin file.
2. Open Flashtool, navigate to Tools > Sin Editor, choose this system.sin file, push Extract data. You'll get system.ext4 in the same directory.
3. Use the cool free Ext2Read tool to get into the ext4 filesystem in the system.ext4 (File > Open Image). Linux users can mount this filesystem as usual. Once you get into the filesystem, go to the lib/modules directory and grab the following files from there (Tools > Save):
core_ctl.ko
ecryptfs.ko
kscl.ko
mhl_sii8620_8061_drv.ko
texfat.ko
4. Once you get these files, create the 3.10.84-perf-XXXXXXX folder in the script's Android\twrp_common_kmodules directory. In my case I created 3.10.84-perf-g5e25a09 folder, just as was mentioned in the script's output in the console (when it complained about Skipping TWRP recovery). Copy these 5 files into this newly created folder.
5. Voilà! Re-run the script and see that now TWRP gets properly integrated! Thanks to @sceryavuz for his initial instructions. I just elaborated them a bit.
When all is clear, turn off your phone if it's on and connect it in a Fastboot mode: hold the Volume Up rocker button and connect USB cable. The LED on the phone will turn blue. Release the button.
Flashing images in this mode is typically done with a fastboot.exe from the Android SDK. Android SDK weighs many gigabytes but thankfully you don't need it. Fortunately Flashtool contains fastboot.exe from the SDK. It's in the Flashtool\x10flasher_lib folder. For the brevity of the following steps, I assume you have all necessary files there. To make it true, copy the newly generated boot.img to this folder.
Now Shift-right-click in the empty space of this folder window and choose Open command window here entry from the context menu. Windows console will appear.
At first try this command:
Code:
fastboot.exe devices
If all is good, there will be one device in the output of this command, just like this:
If not, perhaps there is some driver issue, so head back to the step #1 and make sure the drivers are installed correctly.
If your device is shown correctly, let's flash some files to the phone. Execute the following command to flash the modified kernel:
Code:
fastboot.exe flash boot boot.img
The proper output of this command will be like this:
If you get any errors, the first and more likely reason is that you still have a locked bootloader. Head to the step #3 to verify its state and unlock it if necessary.
If there were no errors — congratulations! — you now just flashed a stock kernel supercharged with TWRP recovery and DRM fix. You're almost done! You may plug out the cable from your phone. If you are attentive to the details, you'll notice that now, once your phone is started, its LED turns amber for 2-3 seconds. This is a special signal for those looking to boot into a recovery (TWRP). But you don't have to start your phone yet.
Although @tobias.waldvogel claims his script is able to also integrate SuperSU during the kernel repacking, I didn't managed to get this working, so the SuperSU (or Magisk) installation is a separate step in my guide. The next step.
6. INSTALLING SUPERSU OR MAGISK
Now when you have TWRP in place and latest Android installed, let's install SuperSU to it. SuperSU distributed in a TWRP-friendly .zip archives, so you should copy one to your microSD card. I used version 2.79 from here. Download TWRP / FlashFire installable ZIP, not the APK. At the time of your reading, there probably will be some newer versions available, feel free to install them them instead. Copy the downloaded ZIP-archive to your microSD. Don't bother to unpack the ZIP.
Once SuperSU zip-file is copied to your microSD card, place it into your phone and reboot to recovery (TWRP). To do this restart or power up your phone and look at the LED. Once it lights amber, press Volume Up rocker button and you'll get into recovery — TWRP. In my case it was TWRP v3.0.2-0.
To install SuperSU, press Install, go to the /external_sd and select the .zip (in my case SuperSU-v2.79-201612051815.zip). Swipe right to confirm installation. Once it is installed, press Reboot System button. Phone will reboot twice. Do not interfere with the process during these multiple reboots, the things are getting done, so just wait once Android is started. When it's started, the phone is rooted and functional!
If you would like to install Magisk instead, the instructions are exactly the same. Grab the latest ZIP from the original thread and flash it with TWRP. That's it!
7. (OPTIONAL) RESTORE YOUR DRM KEYS
If you had successfully backed up your DRM keys in step #2, it is now time to restore it back to the device. There is a flash_dk.cmd script shipped with the Root kernel repack script you used in the previous step. flash_dk.cmd can be used to flash the DRM partition back to your phone.
At first prepare the flashable .ftf:
Code:
flash_dk.cmd <ta backup image> dk.ftf
And then flash dk.ftf via Flashtool, just like you flashed the whole firmware in the step #4, but don't wipe anything this time.
8. OPTIONAL STEPS
8.1. Xposed installation
If you use Lollipop and later, you should install Xposed APK from here. At the time of writing there is XposedInstaller_3.0_alpha4.apk installer there.
Once APK is installed, grab the latest .zip from the repository, I've got xposed-v86-sdk23-arm64.zip. Install it in a regular TWRP way covered in step #6.
Once all these steps are done, you should have Xposed Installer app in your phone, and if you open it and check Framework section, if everything is alright, there will be text in green, something like "Xposed framework version 86 is active".
8.2. Resolving Voice Search and random volume up/down issues while using regular headphones
See this thread.
8.3. Disable startup notification if there is a newer firmware available
Some people get annoyed by a persistent notification, which is displayed once the new firmware become available (new Android version from Sony). Rooted users cannot just tap it and update over-the-air, because they need to perform a complex rooting procedure in beforehand (covered in this guide). It is possible to disable this notification. You may get these notifications by email anyway.
The easiest and safest way is to use some autorun manager. I used Autorun Manager Pro and disabled all receivers of system apps com.sonymobile.fota.service, fota update service and Software update. Notification vanished after a restart.
You may even freeze or remove these apps via some app manager like Titanium Backup Pro.
8.4. Disable that damned green LED light while phone is charged and attached to the cable or docked
This is a historic Xperia behavior, not easily fixable without the root. The notorious green LED is on all night no matter which settings you set up. In fact, there is no setting to switch it off.
However, if you are rooted, you can solve this issue easily. One method is to install a free Light Flow - LED Control app. Once it is installed, you need to enable the following settings in the Settings > Device Settings and Root section: Direct mode, Root mode and Run every command as root. Then you can mess around with individual notifications in the Notification settings, but I just cleared all in there and hey! — the annoying green LED is gone!
THAT'S IT
At this point you have a stock Sony Android enhanced with root privileges. SuperSU / Magisk app is also installed, so you are ready to use root right away. SuperSU now can be updated in a regular way via Play Store. Magisk has it's own updating capabilities.
P.S. WHEN NEW FIRMWARE IS AVAILABLE
Once the new firmware is released, you may perform the same procedure for it beginning from the step #4, but if it is a minor upgrade, you may want not to wipe anything during Flashtool flashing this time. If it is a major upgrade, e.g. Marshmallow > Nougat, you probably may want to start with a clean system and wipe all.

Fragmentation said:
Getting your phone recognized by your computer (driver installation).
(optional) Backup your DRM keys.
Unlocking a bootloader.
Flashing stock firmware with Flashtool.
Repacking and flashing a kernel.
Installing SuperSU.
(optional) Restore your DRM keys.
Optional tasks.
Click to expand...
Click to collapse
I'm pretty sure that once you have unlocked the bootloader, the easiest thing at that point is to use fastboot to flash a custom kernel/recovery, then boot to recovery, flash su, then reflash your original kernel. Then you're rooted.
Plus, rooting is easy now even with locked bl, since we have Kingroot, and new Sony bootloader with real recovery.
(However, I can't say for sure on every device... I appreciate you taking the time to post...)

levone1 said:
I'm pretty sure that once you have unlocked the bootloader, the easiest thing at that point is to use fastboot to flash a custom kernel/recovery, then boot to recovery, flash su, then reflash your original kernel. Then you're rooted.
Click to expand...
Click to collapse
Hey. If you'd say this to my mom, I'm sure she'll not understand any of these. And with this guide she at least have some chance of success.

levone1, why at the end would you flash your original kernel again instead of just running your custom kernel that you made like in the guide?

F2a said:
levone1, why at the end would you flash your original kernel again instead of just running your custom kernel that you made like in the guide?
Click to expand...
Click to collapse
If you flash stock-based kernel via boot.IMG in fastboot that will work with your stock ROM, great, keep it. I was just imagining easiest thing to be to flash, for example, CM boot IMG, just to be able to get into recovery to flash su. Usually stock-based kernels are zips, with other things besides just boot IMG. What I've usually done with unlocked BL and stock ROM is use fastboot to flash CM boot and recovery IMG, then go to recovery and flash supersu, then use flashtool to flash kernel only of stock ROM. Once you reboot, rooted, you can do whatever from there.

Which ROM have you flashed to 6883. The Nougat?

levone1 said:
If you flash stock-based kernel via boot.IMG in fastboot that will work with your stock ROM, great, keep it. I was just imagining easiest thing to be to flash, for example, CM boot IMG, just to be able to get into recovery to flash su. Usually stock-based kernels are zips, with other things besides just boot IMG. What I've usually done with unlocked BL and stock ROM is use fastboot to flash CM boot and recovery IMG, then go to recovery and flash supersu, then use flashtool to flash kernel only of stock ROM. Once you reboot, rooted, you can do whatever from there.
Click to expand...
Click to collapse
I am not quite sure what you mean tbh so forgive me if I missunderstand.
stock kernels are not zips they come in .elf hence the use of rootkernel to unpack/repack it to something more manageable. nowadays supersu makes changes to this partition once flashed, so if you flash stock kernel.sin containing kernel.elf again from flashtool changes will be reverted and you loose root.
the easiest way to get into twrp recovery without flashing anything is to just fastboot it.

nigeta_gr said:
Which ROM have you flashed to 6883. The Nougat?
Click to expand...
Click to collapse
Yes, the latest official firmware available for Z5P (E6883) is Nougat (7.0). I flashed it during the assembly of this guide.

I suppose it will work with my E6833 as well.
Fragmentation said:
Yes, the latest official firmware available for Z5P (E6883) is Nougat (7.0). I flashed it during the assembly of this guide.
Click to expand...
Click to collapse

nigeta_gr said:
I suppose it will work with my E6833 as well.
Click to expand...
Click to collapse
I'm sure it will.

Fragmentation said:
At first I created a guide about rooting stock Marshmellow of Sony Xperia Z5 Premium. After some time I realized that it may be useful to users of virtually any recent Sony phone, so here is my Sony Cross-Device general rooting thread. I will mostly copy-paste bits from my previous guide, but using renewed screenshots and firmwares'/tools' versions.
Click to expand...
Click to collapse
Ogromnoye spasibo bratan!
This helped me tremendously, just wanted to say thanks!
FYI, I'm using latest Nougat 333 UK firmware on Xperia X F5121 US version --- so that my fingerprint scanner works. Got stuck in a boot loop after installing TWRP but after reading your thread, I fully understood and fixed the reason why. The root tool from GitHub worked kinda --- meaning I had busybox and others but no su binary I still had to install SuperSU.zip via TWRP to actually have root. You documented a similar experience.

JZ SmartMort said:
Ogromnoye spasibo bratan!
This helped me tremendously, just wanted to say thanks!
FYI, I'm using latest Nougat 333 UK firmware on Xperia X F5121 US version --- so that my fingerprint scanner works. Got stuck in a boot loop after installing TWRP but after reading your thread, I fully understood and fixed the reason why. The root tool from GitHub worked kinda --- meaning I had busybox and others but no su binary I still had to install SuperSU.zip via TWRP to actually have root. You documented a similar experience.
Click to expand...
Click to collapse
You're welcome, zemlyak! Sure, for root you definitely need SuperSU, it just won't work without it this way. It's a shame US versions of Xperias don't have fingerprint scanner activated, but it's cool to hear, that flashing another region firmware helps.

Hi, I followed everything until the part where I need to flash the modified kernel in step 5. There is no error messages. the output is exactly like the screen captures. When I start the phone, I don't see the amber light. I cannot proceed. Where did I go wrong? Appreciate any help available.
Edit: Used a rooted stock kernel from another thread. Seems to work. Still not sure what I missed out though.

viperc said:
Hi, I followed everything until the part where I need to flash the modified kernel in step 5. There is no error messages. the output is exactly like the screen captures. When I start the phone, I don't see the amber light. I cannot proceed. Where did I go wrong? Appreciate any help available.
Edit: Used a rooted stock kernel from another thread. Seems to work. Still not sure what I missed out though.
Click to expand...
Click to collapse
Hey. If the phone don't turn on amber light for a while during the boot up, then TWRP is not there.
If you used the kernel repack script I mentioned in the guide with a very recent Sony's firmware, probably you didn't notice, that TWRP has not been integrated into the kernel due to some error. It is because this script should be frequently updated to work with any newly released firmware, and Tobias, its author, apparently have not time to do this.
However, you can update the script yourself, following this procedure.

viperc said:
Hi, I followed everything until the part where I need to flash the modified kernel in step 5. There is no error messages. the output is exactly like the screen captures. When I start the phone, I don't see the amber light. I cannot proceed. Where did I go wrong? Appreciate any help available.
Edit: Used a rooted stock kernel from another thread. Seems to work. Still not sure what I missed out though.
Click to expand...
Click to collapse
I don't have the amber LED light on boot up on my X Compact but everything works fine. I can't seem to find it but I recall reading somewhere an actual reason why I didn't see it but as far as I know it's not a problem.
Edit: Simple check, reboot and hold volume down. Do you enter TWRP? I do even though I never see the amber led.

F2a said:
I don't have the amber LED light on boot up on my X Compact but everything works fine. I can't seem to find it but I recall reading somewhere an actual reason why I didn't see it but as far as I know it's not a problem.
Edit: Simple check, reboot and hold volume down. Do you enter TWRP? I do even though I never see the amber led.
Click to expand...
Click to collapse
Maybe it wasn't a proper kernel for your rom or device, I also experienced some errors including yours but at last (after 12 try) I found a working kernel for me. I really don't know what the problem is, sometimes it just doesn't work...

Fragmentation said:
Hey. If the phone don't turn on amber light for a while during the boot up, then TWRP is not there.
If you used the kernel repack script I mentioned in the guide with a very recent Sony's firmware, probably you didn't notice, that TWRP has not been integrated into the kernel due to some error. It is because this script should be frequently updated to work with any newly released firmware, and Tobias, its author, apparently have not time to do this.
However, you can update the script yourself, following this procedure.
Click to expand...
Click to collapse
Thanks. I will look into that again when my region's Sony release the latest firmware.
F2a said:
I don't have the amber LED light on boot up on my X Compact but everything works fine. I can't seem to find it but I recall reading somewhere an actual reason why I didn't see it but as far as I know it's not a problem.
Edit: Simple check, reboot and hold volume down. Do you enter TWRP? I do even though I never see the amber led.
Click to expand...
Click to collapse
Interesting, didn't try that lol. I used another pre-rooted sick kernel to flash after my attempt failed. I can see the amber led now with the other kernel.

Tried again after re-downloading the script. It's working now. Thanks.

if not do drm-fix, and flash dk.ftf with old flashtool, the result is" FIDO KEYS NOT PROVISONED PROVISION FAILED"
any way to fix this?

This thread is a complete guide and must be sticked, Thanks :fingers-crossed:
You should add backupTA-V2 for Lollipop devices..
Thread : https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
iovyroot method is very old..

[GUIDE][OSPREY] Moto G3 BEGIN: Unlock bootloader, Flash: TWRP, ROM, Root, Boot logo

Edited Dec 22 -2017 <-- I may not always change this, but this is a work in progress!
[GUIDE][OSPREY] Moto G3 2015 - BEGIN: How to Unlock bootloader, flash TWRP, flash ROM, flash Root, Flash boot logo.
I started this because while trying to explain it to a user I kept running in to old info.
Code:
/*
* Your warranty is now void.
*
* This may destroy your phone. As with any modification to a phone,
* you must be prepared/willing to THROW IT AWAY without thinking twice.
* If you need it or it is your daily driver, don't mess with it.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about the suggestions in this guide
* before following it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This may well work on Merlin but I don't have one to test.
--> NOTE: I no longer use LineageOS so can't help there. Using AOSP 8. Should be no difference.
1a) Prep - before you do anything, in stock, go to settings/Development Options (which is turned on by tapping /settings/about phone/Build Number about 10 times.)
turn "OEM unlocking" ON
turn Debugging - "USB debugging" ON.
1b) Now! - To do anything, you must unlock your bootloader: This is done by going to the Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
They want you to "Install the Android SDK.". You only need adb and fastboot on your PC (windows or Linux).
Try this guide to get ADB and FASTBOOT onto your computer: https://forum.xda-developers.com/showthread.php?t=2588979
For Ubuntu Linux simply type fastboot on the terminal and if it's missing a command will pop up as to how to add it - simple. same with adb.
ADDITIONAL THOUGHTS: a very helpful user suggested the following additional for unlock bootloader and getting adb and fastboot: @Dave here - see post 34ff.
Dave here said:
Glad it was helpful! Happy to be able to give something back. Here are some links I used...
LineageOS Osprey install guide:
wiki.lineageos.org/devices/osprey/install
LineageOS Using ADB and fastboot guide:
wiki.lineageos.org/adb_fastboot_guide.html
adb & fastboot: I used this link, which was in the LineageOS ADB guide and I think also the Motorola bootloader unlocking instructions:
Mac: dl.google.com/android/repository/platform-tools-latest-darwin.zip
Windows: dl.google.com/android/repository/platform-tools-latest-windows.zip
Linux: dl.google.com/android/repository/platform-tools-latest-linux.zip
Lenovo forum: "THERE IS AN ERROR WITH YOUR REQUEST! MOTO G ROOTING PROBLEM!" (it's actually about bootloader unlocking, not rooting):
forums.lenovo.com/t5/MOTO-G-MOTO-G-...EST-MOTO-G-ROOTING-PROBLEM/m-p/3458979#M27009
European Motorola unlocking URLs:
motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-a
motorola-global-portal-de.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that in step 4.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
-> Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode on your Osprey, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest.
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP. If you get the dead android it means you still have the stock recovery - boot to fastboot and flash TWRP again.
IMMEDIATELY tap Backup and select to put backup on external storage - your SDcard. NOTE - if your SDcard has been converted to "internal storage" you will have to choose "internal storage" (em0). I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
-- > For TWRP BACKUP I use the default settings of "system,data, and boot". Here is a nice article that explains the differences: https://twrp.me/faq/whattobackup.html .
At this point I recommend you boot back into stock and connect your phone to your PC via USB (slide down) and copy that backup in the TWRP folder to your PC. at least once, maybe twice, for safe keeping. You will need this if you wish to test if a problem exists only on a custom ROM but not on the stock ROM. You will also need this if you simply choose to run stock, instead of a custom ROM. Remember, you are now testing ROMs - nothing is certain!
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
Be aware there are some sites out there with logos that don't work on Moto G3.
5. To flash a custom ROM: Download to PC and put it on your SD card. Do same for gapps. (gapps - g-apps - google apps allow you to log in to your google account, use play store, etc. example http://opengapps.org/ (use arm, 7.1, whatever size you wish)(if you're new use full, mini, or micro until you know what you need. If you're on a 1GB phone, consider nano or pico.) )
https://download.lineageos.org/osprey or whatever ROM you want.
http://opengapps.org/ or whatever gapps you want.
Boot to TWRP.
Clean flash:
tap WIPE,
tap advanced, carefully checkmark:
Dalvic/ARTCache,
System,
Data,
Cache,
and then swipe the bottom swipe button. Takes a few sec. This is what makes a "clean flash".
Generally: Don't wipe "internal storage" or SDcard as this is where TWRP stores its backups/nandroids. - I always copy my TWRP backups to PC for safety.
Then back to menu screen and tap Install, select the rom, and swipe and let it do its thing.
Then back and tap Install, select the gapps and swipe to flash it.
THEN, and only then: tap Reboot (if you're at the main menu you also have to tap System to boot from system.)
The install takes 3 min or so before it starts asking questions.
Be sure to choose "Set up as New" or else you get whatever junk is in your google drive. This has cost errors and much time. <-----
6. Root: If you want to use bank apps, PokemonGo, etc, follow these instructions for Magisk:
https://forum.xda-developers.com/2015-moto-g/general/guide-pass-safetynet-custom-roms-t3603609
read the whole thread.
- Else go to https://download.chainfire.eu/1019
and download the zip form of Chainfire's SuperSU 2.79 and boot to TWRP and flash (install) it.
Many thanks to @acejavelin for inspiration and information(which I probably shamelessly stole from him), to @squid2 for his installation guide and his version of TWRP, to @Chainfire for the tons of work that continue to go into superSU, to @coolguy_16 for the safetynet/CTS work, and all the many Devs and helpers who make these ROMs possible, and as clean as they are! And to users like you who find bugs and file bug reports! Thank you!
Remember you are working with a Development ROM - a work in progress! (Even stock isn't perfect!!!)
Enjoy!

KrisM22 said:
I started this because while trying to explain it to a user I kept running in to old info.
As with any modification to a phone, you must be prepared/willing to throw it away without thinking twice. If you need it or it is your daily driver. don't mess with it. It is YOUR responsibility alone. If you break your phone, I will laugh.
1) To do anything, you must unlock your bootloader: This is done by going to a Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that later.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
a) you need to have fastboot support on your PC
Try this guide: https://forum.xda-developers.com/showthread.php?t=2588979
You do not need to put the whole SDK on as s9ome guides would have you do.
Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest - twrp-osprey-3.1.0-r1.img
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP.
IMMEDIATELY tap Backup and select to put backup in internal (em0) storage. I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
5. To flash a custom ROM: Put it on your SD card. Boot to TWRP.
Clean flash: tap WIPE, tap advanced, carefully select Dalvic, Data, System, Cache, and then swip the bottom swipe thing. Takes a few sec. This is what makess a "clean flash".
Then back to menu screen and install, select the rom, and swipe and let it do its thing.
Then back and select gapps and flash it.
Then do supersu and flash that (optional)
Then "reboot".
6. Root:
Click to expand...
Click to collapse
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk

save1

save2

Subins Mani(Tintumonn) said:
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Thanks - hopefully it will help.

A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.

KrisM22 said:
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.
Click to expand...
Click to collapse
Yes you are correct, gapps won't get removed for new builds of the same ROM due to a persistent ROM script. However flashing a ROM different than the one currently installed usually ignores such scripts and does a clean wipe. Doing a manual wipe just to be sure is fine, even needed sometimes.
I just wanted to point out that not performing a factory reset (twrp>wipe>swipe to factory reset) can leave potential conflicting files in aforementioned places which can cause unexpected behaviours ranging from FCs to bootloop. The potential issues are rare but I think you know how much trouble it can bring to folks trying to capture real bugs (thanks for hard work at Linage ); it was all about removing the potential factors .
Broadcasted from Zeta Reticuli

The TWRP wipe-swipe does Data, Cache, and Dalvic. That's what I used to do. After messing up some tests this past week and wasting a lot of time, I now recommend adding system to that:
In advanced, checking data, cache, and dalvic/ARTcache, and, now, system. as far as i can see, I am leaving nothing other than internal storage and sd card (and of course whatever is in OTG if there's one attached). TBPro puts its backups on "internal storage". By the way I do appreciate your taking the time to look so closely at this!

KrisM22 said:
[GUIDE]
6. Root: Go to http://www.theandroidsoul.com/supersu-2-79-zip-apk-download/
and download the zip form of Chainfire's SuperSU 2.79 . Use it in step5 above.
NOTES: this has nothing to do with rooting your stock ROM which afaik can't be done.
Click to expand...
Click to collapse
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
Edit: Not necessary anymore, just flash SuperSU zip and you're done
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).

xMotoDA said:
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).
Click to expand...
Click to collapse
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not since SuperSU 2.79 - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!

KrisM22 said:
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not after SuperSU 2.78 (or 2.70 or something) - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!
Click to expand...
Click to collapse
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.

acejavelin said:
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.
Click to expand...
Click to collapse
Huge thanks for that!!! Changed above post.
Never played with Magisk - others (you!) are the authority on that. I think some were saying that was a way to get a custom rom to pass safteynet... Thanks!
Huge thanks for looking in!!!

edited/updated 5-4-17

Problem!
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!

GermanRodriguez said:
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!
Click to expand...
Click to collapse
This is possibly a problem with that rom - ask at that thread.
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-n-5-8-2-t3587204
or
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-t3478845

edited...

edited

update

changed.

upgrade to Android Q & keep twrp and data

Ok here's what I did. To keep my data and twrp when upgrading from "P" to " Q".
1. I downloaded the OTA zip file.
2. Extracted it on your phone.
3. Edit the "Flash-all.bat" file
A. Delete "-w" from one of the last command lines.
B. Add "reboot-bootloader"
"fastboot boot twrp-3.2.3.1-marlin.img"
C. Hit "save"
C. Both the above command lines should be right
before the line "echo press any key to exit"
4. Add the twrp.img to the folder with the above extracted contents.
5. Edit "flash-all.sh" to read the same as you have just edited the "flash-all.bat" file. And then hit "save".
6. Compress the extracted file so as to create a .zip file again.
7. Move this .zip file to your PC.
8. Plug up your phone to your PC and make sure android debugging is active.
9. On your PC extract the .zip file you just created.
10. Make sure you have the twrp installer zip on your phone.
11. Go into the extracted .zip file and double click the "flash-all.bat" windows batch file and sit back and wait.
12. When it finishes it will boot up. 1 out 3 times I tried this it booted then immediately rebooted to the stock recovery with an error saying that my data may be corrupt and if I see this message again then perform a factory reset. And gave me to options "try again" and "factory reset". I clicked "try again". It then booted normally.
13. Power off your phone.
14. While holding vol down press and hold power button for a few seconds and then release the power button but NOT the vol down button. This will put you in bootloader mode.
15. Once in bootloader mode it will then boot twrp.
16. Once once twrp loads click install then navigate to the folder you put the twrp installer.zip and flash the installer. 17. Hit "reboot system"
18. Sit back and wait.
19. All your data will remain on the phone. All your settings stayed the same.
***********NOTICE ***********
1. YOUR BOOTLOADER MUST BE UNLOCKED. IF YOU DONT KNOW HOW TO DO THAT THEN YOU SHOULDNT BE ATTEMPTING THIS. ESPECIALLY IF YOU ASK ME HOW TO UNLOCK YOUR BOOTLOADER.
2. I TRIED THIS 3 DIFFERENT TIMES WITH THE SAME RESULTS. I will post pics of the step by step process later. Just wanted to go ahead and get this out there so those of you who know your way around an android could do it.
3. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
I AM NOT RESPONSIBLE FOR YOU F'ING THIS UP AND NOT FOLLOWING INSTRUCTIONS TO A "T".
4. THIS IS RISKY BUT IF YOU FOLLOW INSTRUCTIONS CAREFULLY YOU SHOULD HAVE NO ISSUES.
Im also posting a pic of my about phone to show I am indeed on "Q" and that this worked for me.
Hope you enjoy
Be patient I'll have step by step screen shots posted in a little bit of the process. To maybe make it easier to understand.

Could this work for official android 10

Very nicely explained, thank you.
Please excuse me if this is a stupid question, but why not just extract and edit on your PC instead of on the phone then transfer to PC?

Did you try flashing magisk?
Thanks for letting us know latest twrp works. But did you try to get root @mattwheat ? I am too afraid to lose data so didn't flash magisk yet.

All I did was manually flash bootloader, radio, system and vendor and it kept all my data with working twrp and root (coming from pie custom rom).

sinkoo1979 said:
All I did was manually flash bootloader, radio, system and vendor and it kept all my data with working twrp and root (coming from pie custom rom).
Click to expand...
Click to collapse
So you didn't even wipe anything? You just booted into TWRP and manually flashed the files? I'm also on a 9 custom ROM and would love to know the best/safest way to make the move to 10

johnblundon said:
So you didn't even wipe anything? You just booted into TWRP and manually flashed the files? I'm also on a 9 custom ROM and would love to know the best/safest way to make the move to 10
Click to expand...
Click to collapse
no wipes
Flashed through fastboot.
Steps:
flash bootloader
reboot to bootloader
flash radio
reboot to bootloader
flash system
flash vendor
reboot to system
I was missing OTA function in settings.....
it work for me but can't guarantee it will work for everybody. Best way is to try it.
flashed q beta and went back to pie customs roms by flashing bootloader, radio, and vendor (before official q was released). Have to download all apps but internal storage stayed intact.

salpsuc said:
Very nicely explained, thank you.
Please excuse me if this is a stupid question, but why not just extract and edit on your PC instead of on the phone then transfer to PC?
Click to expand...
Click to collapse
You're welcome. And sure you could do that I would imagine. May be easier but then I would be explaining a method I did not actually try. And that would suck if by chance some ones phone caused world's to collide. I would feel pretty bad about that. Unless the end result was Nancy pelosi shutting up and resigning.

rahil3108 said:
Thanks for letting us know latest twrp works. But did you try to get root @mattwheat ? I am too afraid to lose data so didn't flash magisk yet.
Click to expand...
Click to collapse
I did not have root after flashing twrp.... Seems like, looking back, that I tried and seems like it may have said "successful" but it didn't stick upon reboot. But I imagine it's neither here nor there cuz y'all prolly have root by now...

[Guide]How to Root Your Pixel 3a and Install Magisk - Android 9 - 12

Edit - just an FYI for complete transparency. I have moved from the Pixel 3a XL to the Pixel 6. I no longer own my Pixel 3a XL. While I've been told (thanks @AndDiSa) that the root process for Android 12 is the same as it historically has been, I no longer can test things myself. (The root process for the Pixel 6 is different and more complicated than this phone). If you run into any problems or issues, please post in this thread and someone will hopefully be able to answer them.
I'm assuming you understand how to use ADB on your computer. If you need assistance with installing or using ADB, please refer to this XDA article for more information. However, here are some common issues that people have with ADB if it doesn't work initially for you. 1) Check the Android System Notification that appears in your phone's notifications after you plug in your USB cord. Your phone probably defaults to "No data transfer" and you need to change it to "file transfer" to allow the phone to connect. 2) Make sure you have USB debugging turned on in the Settings/System (advanced)/Developer options. 3) If this is your first time using this phone/computer combination, you will have to accept the connection when it pops up on your phone.
You also need an unlocked bootloader to complete these steps. If you need assistance with unlocking your bootloader, here is decent set of instructions. Those instructions are based on the Pixel 3 phone, but the steps are the same for the 3a devices.
Here are the official Magisk installation instructions. I will walk through them to help everyone understand them. Please note that while TWRP does work with Android 9 (Pie), it does not work currently with Android 10 or 11. If you are still on Pie for some reason you can choose either installation option, but if you have moved to a later Android version, you must use the "Boot Image Patching" installation method.
Custom Recovery Installation Method - (available for Android Version 9/Pie only because TWRP does not work currently with the Android 10/11)
This is the easier installation method IMHO, but it does require using TWRP. If you don't know how to get TWRP for the Pixel 3a, please refer to the official TWRP for Pixel 3a thread
Step 1 - Download and install the Magisk manager app on your phone. (link to the latest stable version can be found here).
Step 2 - Using the Magisk manager app, select "Install Magisk" and select the "Download Zip Only" option. This simply downloads the installation zip to your phone's download folder. It doesn't attempt to install anything.
Step 3 - Boot into TWRP - (because TWRP is not permanent on the stock Pie OS, we must follow these instructions each time we want to boot into TWRP).
Step 3a - Download the latest TWRP image for the 3a to your computer (not your phone) from the official TWRP for 3a thread.​Step 3b - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".​Step 3c - Boot your phone into the bootloader (type the command "adb reboot bootloader").​Step 3d - Boot into TWRP using this command, "fastboot boot twrp-3.x.x-x.img" (where "twrp-3.x.x-x.img" = whatever the name of the TWRP download is). Please note you are not using the "flash" command as we are not permanently installing TWRP.​Step 4 - Once the device boots into TWRP, select "Install" and then find the Magisk.zip download from step 2. Swipe to confirm the installation
Step 5 - After the installation is complete, simply reboot system.
Step 6 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 7 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed under the "Taking an OTA Update" section below
The Boot Image Patching Installation method - (the only method currently available under Android 10, 11 or 12, but it also works with Pie).
Use this method if you are on Android 10 or 11 or you are on Android 9/Pie but you don't want to or can't use TWRP.
Step 1 - Obtain a stock boot.img file for the OS version/update that you are currently on. The easiest method is probably to download the applicable full stock image directly from Google. Unzip the files and unzip the second folder and you should find the boot.img file inside.
Step 2 - Copy the stock boot.img file to your phone's storage - probably to /sdcard or to /sdcard/downloads
Step 3 - Download and install the Magisk manager app on your phone. (link to the latest version can be found here). If you are early in the Android 12 cycle, you probably need to use a Canary build of Magisk.
Step 4 - Using the Magisk manager app, press "Install --> Install --> Select and Patch a File" - select the stock boot.img file that you put on your phone in step 2.
Step 5 - Magisk will modify the stock boot.img file and create a patched boot image file. It will save this modified file at "sdcard/Download/magisk_patched.img"
Step 6 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 7 - Copy the patched boot image from your device to your PC and the adb folder. If you can’t find the file on your phone via MTP or Windows Explorer, you can pull the file by typing the command "adb pull /sdcard/Download/magisk_patched.img" - Please note, I would suggest double checking the "file modified date" prior to moving the file. Be sure to only move the file if it was last modified on the date you are doing this. I've had a strange situation before where the newly modified file didn't immediately show up and the file showed a modified date of the previous month. If you flash an old version, your phone will bootloop.
Step 8 - Boot your phone into the bootloader (type the command "adb reboot bootloader").
Step 9 - Flash the patched boot image to your device using this command, "fastboot flash boot magisk_patched.img"
Step 10 - Reboot (using command "fastboot reboot").
Step 11 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 12 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed next.......
Taking an OTA update in the future (if you used this method to install Magisk).
Taking OTA updates is very easy with the Pixel devices because of their A/B partition system. It allows us to uninstall Magisk, take the OTA update, and reinstall Magisk - all from the phone and all without rebooting during the process. Here are the offical Magisk OTA instructions. I will go through the steps to help explain them.
Step 1 - In the Magisk manager app: Click “Uninstall” then “restore images”. DO NOT REBOOT or press the reboot button.
Step 2 - Download and install OTA (in your phone's Settings/System/System Update). DO NOT REBOOT or press the reboot button.
Step 3 - Open the Magisk manager app and click “Install” next to Magisk (usually it says "Magisk is up to date") then “Install to second/inactive slot (After OTA)”
Step 4 - Press the Reboot button in Magisk.
That should be all it takes to install an OTA and keep root.
Please note, we are getting reports that users are getting notifications that an OTA update has been installed even when they have "Automatic Updates" turned off. If this happens to you, don't reboot the phone which is suppose to be the final step in the update process. Instead, follow the above instructions on taking an OTA update, but start in step 3. In other words, you shouldn't have to uninstall Magisk because the update has already been installed. All you need to do is install Magisk to the "second/inactive slot (After OTA)”. After completing that step, you can reboot your phone to complete the update process. Be sure to post your experiences in this thread to let us know if this process works or not.
Just remember that many custom parts (like kernels and Magisk modules) may need to be updated to any new OTA version. Please be sure to check out the forums for each custom kernel or module that you may want to install to ensure it has been updated to the lastest OS version. Don't assume anything or you may find yourself in a bootloop.
If you find yourself in a bootloop after upgrading an already rooted phone
If you find yourself in a bootloop after updating to a new OS version and flashing the magisk_modified boot.img again, it is likely due to an installed Magisk module not being compatible with the new update. To uninstall all Magisk modules to fix the bootloop, follow these steps:
Step 1 - Connect your phone to the computer you use ADB on.
Step 2 - In ADB type the command "adb wait-for-device shell magisk --remove-modules"
Step 3 - Start your phone again or wait for it to go through another bootloop cycle.
Step 4 - as soon as ADB is available (which occurs even during a bootloop) the command will activate, the modules will be removed, and the phone will reboot.
If the normal OTA method isn't working - sideload the OTA update
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on a couple Android 10 images, but most do not require this step.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, while the initial boot is usually pretty quick, it can take longer. I've occasionally seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that sometimes it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take an regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just need be patient and let the phone complete the process.
My rant about using these "Pre-patched Boot image" files
I started this thread during a period of time where there was a another thread on this forum started by pbanj that showed users how to root their phone by using some pre-patched boot image files. This method is not the generally accepted method and while it works, there are major shortcomings with it (see explanation below). Because it was the only root thread available at the time and he only showed the "pre-patched boot image" method, many people blindly followed his directions only to be confused when it came time to update the software on their phones. I wrote this thread in an effort to show people the official Magisk installation method. Pbanj has since updated his thread and it now includes the preferred method as well. With his edits, the two threads are sharing the same information now, although Pbanj thread still offers people the "pre-patched boot image" method (which I don't recommend people using).
EDIT - Yet another thread pushing a pre-patched root method has been started. It suffers the same issues as listed below.
Shortcomings with using the "pre-patched boot image" method.
As I already mentioned, there is a huge shortcoming with using the "pre-patched boot image" method described in the other root thread. Because he provides a pre-patched boot.img file, you skip some normal installation steps. In the end you have the exact same patched file (which is why his method works), but you cripple the system when it comes to taking any future OTA. That's because the first step in taking an OTA update is having Magisk reflash the stock boot.img effectively uninstalling itself. This step fails if you used his pre-patched boot image method because you skip the step where Magisk creates the backup of the stock boot.img that it needs to uninstall itself.
I already used the "pre-patched boot image" method to gain root. What can I do?
First, let me clarify and say that there is nothing wrong with your phone or root privileges. Your phone will work exactly as expected and root and Magisk will work exactly as expected. That being said, in the near future you will want to update your phone to the latest Android update and this is where the "pre-patched boot image" method is much more cumbersome. The best option is to simply undo his root method and re-root using the method described above. To do this, flash the correct stock boot.img file to your boot partition and then follow the steps above to reinstall Magisk. Jbanj has confirmed this method will work. The other option is just wait until you need to take an update and then sideload the OTA update following the instructions above. This will remove root and you can then follow one of the two methods to obtain root as outlined in this thread.
Notes
- Please be sure you are on the latest adb and drivers which can be found here.
- You do not need to keep the stock boot.img file (from step 2 of the Boot Image Patching method) on your phone after completing these steps. Magisk saves the stock boot.img backup at /root/data in a file with the name "stock_boot_XXXXXXXXXXXX.img.gz"
Thanks to.......
@ZVNexus for getting TWRP working on the 3a and 3a XL phones
@topjohnwu for making Magisk what it is today

Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!

You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk

jmtjr278 said:
You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......

sic0048 said:
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......
Click to expand...
Click to collapse
Sure. It's the way I do it also. But show some class and don't call out other, helpful members in this fashion and crap all over what they do. I have seen your posts and know your a helpful members also, let's respect each other and be classy.
Sent from my Pixel 3a using Tapatalk

@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?

Bankuu said:
Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!
Click to expand...
Click to collapse
I've edited the steps and added a few more going into greater detail to try and make it even clearer for users. Let me know if you have any suggestions.

alliance1975 said:
@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?
Click to expand...
Click to collapse
You should be able to use the normal Magisk OTA update instructions for future updates.
I've updated the thread and I think the "step 9" you listed isn't the same anymore, but I think I understand your question. Actually I think my original instructions were inaccurate as far as that step. I've always gone back into Magisk after flashing the modified boot.img and I thought I hit install to install the Magisk framework (if that is the correct term). But after reading some other guides, I think my memory is incorrect and you don't really have to install anything after the flashing portion of the steps.
Once you reboot after flashing, that should be all you have to do. I'll uninstall Magisk here in a while and walk through the steps myself to ensure this is correct howeve.

The OP should be made a sticky.

Cool guide. Can the method be applied to Q beta 4 ?

MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
No root for Android q on our devices yet afaik.
Sent from my Pixel 3a using Tapatalk

@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?

alliance1975 said:
@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?
Click to expand...
Click to collapse
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"

sic0048 said:
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"
Click to expand...
Click to collapse
Thanks sic0048. You put up with my dumb questions and helped make my pixel 3a a great phone.
Respect.

Edited - now that jbanj has confirmed we can simply flash the stock boot.img file to the boot partition and start over, the post I originally had here is pointless.
Alliance's question got me to thinking.....
Since Magisk saves the stock boot.img backup at /root/data in a file named "stock_boot_XXXXXXXXXXXX.img.gz" I wonder if we can't simply share a backup file with someone that used jbanj "modified boot image" method and have them copy it to that location. I suspect Magisk will then allow the normal OTA update prceedures to work.
I can share the backup file that I have, but it is for the 3a XL model, Android version 9 (Pie) and the June 5, 2019 security update. That means it will be next month before there will be another OTA update pushed out.
If someone is still on the OEM March update and rooted using the normal directions and is willing to share their backup file, we might be able to try it sooner.
Unfortunately I don't know if Magisk modifies the backup to be some sort of unique file. I doubt it, but I don't know for sure. Of course worse case scenario is that it doesn't work and the person has to flash the OTA manually - which is no different than what they would have to do anyway. So there really isn't much risk in trying this.

MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.

Bankuu said:
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.
Click to expand...
Click to collapse
Google has changed the file structure in the Q beta 4 release and root is not possible at this time. This is true across all devices (not just the Pixel 3a). I know John Wu (the Magisk developer) is working on a solution and I would expect to see results before Android 10 is released, but only time will tell.
However, at this time there is no root on the Q beta 4. If you need root, you will have to stick to Pie for now.

@sic0048 I've updated my thread

I'm getting weird behavior here that I've been able to replicate.
Bottom line, if you use the Magisk patch method, upon flashing that boot image, your phone will auto-play music every single time it boots up. That's incredibly annoying.
Uninstall and go back to stock boot.img, and it goes away. Flash again, it's right back.

Guess I'll just wait for TWRP instead of going through those steps again, lol.