Database Users

[Guide Finder] Root, Upgrade, Back to Stock + More

These guides are for 2014 Fire HD 6 and 7. Don't use for any 2015 model. If your device has a micro-SD slot, it's 2015.
All root/upgrade guides install Gapps
Credit: Guides for rooting OS above 4.5.3 rely on powerpoint45's instructions for downgrading to 4.5.3 to obtain root. Thanks @[COLOR="Black"]powerpoint45[/COLOR]!
Basic Root and Upgrade
UPGRADE - Upgrade guides link back to root instructions, so you can just begin here.​
Upgrade to Lollipop
- [TUT] Install [FireOS 5.1.2, Feb 26, 2016, "blue shade"], ROOT & GAPPS http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Upgrade to OS 4.5.5
- [How to] Upgrade to 4.5.5 (or other 4.5.x) with root in TWRP: http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
- [How to] Upgrade to 4.5.4 and keep TWRP and root: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
ROOT​
Root, install TWRP, and upgrade
-[ROOT, v2.0] + FireOS 4.5.4 + fully working latest GAPPS http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
Video Root and Upgrade to Lollipop
Step-by-step video guide to root and upgrade to Lollipop
- OS 5.0 + ROOT + GAPPS + Play Store VIDEO TUTORIALhttp://forum.xda-developers.com/fire-hd/general/os-5-0-root-gapps-play-store-video-t3238734
Return to Stock
[How to] Restore full stock FireOS; http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267
Obsolete
Detailed Root and Upgrade to Lollipop (for never-rooted devices)
Step-by-step "newbie friendly" guide to root and upgrade to Lollipop
- [Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly") http://forum.xda-developers.com/fir...lipop-os-5-t3172408/post62188341#post62188341
Out of date as of 3/3/16
- [ROOT] With working PlayStore Google Apps + Custom Launcher + superSU http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Install ADB Drivers for Windows
Illustrated - Run ADB in normal and sideload mode from any folder location
- [GUIDE] Install Windows ADB Drivers for Fire HDs ("Newbie Friendly"): http://forum.xda-developers.com/fire-hd/general/guide-install-windows-adb-drivers-fire-t3189000
Video
- Install ADB USB Drivers for Fire HD 6/7 (normal & sideload mode) (Windows): https://www.youtube.com/watch?v=CyJlmTtLsIg
Other Good Stuff
Temporarily Install TWRP on Rooted OS 5: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Links to Stock ROM Update bins
Fire HD ROM links : http://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102
Lollipop Info, Issues, Tips/Tricks and Workarounds
[Discussion] Lollipop on Fire HD : http://forum.xda-developers.com/fire-hd/general/qa-lollipop-fire-hd-t3167532
Disable OTA, Amazon Launcher, Appstore and More
[How To] Disable System Apps and Services (includes OTA): http://forum.xda-developers.com/fire-hd/general/how-to-disable-apps-services-includes-t3165348
Use a Script to Disable/Enable Sys Apps, and Switch Launchers with One Tap:
[FireOS 5.x + ROOT] Quickly switch to Amazon UI and back: http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
Get Wallpaper on OS 4 Custom Launcher
[HOW TO] Get Wallpaper on Custom Launcher: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009

:fingers-crossed:

Another where's root guide question, another nudge

Gapps tutorial for Hd6/7
DoLooper said:
Another where's root guide question, another nudge
Click to expand...
Click to collapse
It will be a great help someone can compile a guide about how to install gapps on hd 6 or 7 running 5.2.X. there are lot of confusion about which xpose and gapps and in which order should flash to get them working. (specially who are already on 5.2.x without gapps)

Nudge

I changed the title and added a bunch more guides. Post if I got something wrong or left out something you think is helpful. thx.

Added @powerpoint45's new video guide

DoLooper said:
Added @powerpoint45's new video guide
Click to expand...
Click to collapse
Coolio

:angel:

:fingers-crossed:

Hi everyone,
I have the Kindle Fire HD 6 4th Gen currently on the developer preview Fire OS 5.0.1..... Is there any way to get this rooted????
I've tried Kingroot v4.90 but no luck....

Pardon the dumb question, but from reading the guides here, my conclusion is: there is no way to directly root 5.1.2.1 and install playstore / gapps. One must do either
1) regress to 4.5.3 / root / upgrade to 5.1.2.1 + gapps + xposed
or
2) sideload 5.1.2 factory image and flash that, root it, then install gapps and xposed (and update disabler) <<--- probably recommended
Did I understand that correctly?
I am familiar with bootloader / gapps / roms / Xposed and all that. I play with my Nexus 7 / Moto X stuff all the time. Fire HD is primarily an e-reader, but would be nice to have Playstore on it too.

Is there a way to root a Fire HD 7 4th gen 5.3.1.0?

[REQ] Deodexed FotaClient & SyncmlDM apps from N910C COJ5 ROM

Apparently a de-Knoxing script included in my kernel(?) removed these apps from my phone; seeing the recent N920T and possibly N910F Marshmallow leaks through OTA, it would be nice if I still had these apps on my phone for capturing an update.zip in case Samsung again accidentally pushes something interesting. Unfortunately, because IU have Xposed installed (which deodexes the ROM and breaks running odexed apps), I can't just copy these apps from an official ROM.
Does someone have these 2 apps in a deodexed version? Or do they now somehow depend on Knox?

Those won't make a difference, as soon as you modified your ROM you will not receive OTAs.
The only solution is to flash a stock firmware via Odin if you want to receive updates again, no root, custom kernel or any other /system mod.

There is a well-known hack to override rooting checks in OTA, which enables grabbing update.zip files on rooted phones (although they won't apply cleanly on a rooted ROM). However, SuperSU(?) now appears to remove the OTA apps as part of its "KNOX removal" routine.

Nevermind, managed to deodex them myself. Turns out my oat2dex was an old version.
Anyone running into this problem: use oat2dex.jar from the Linux deodex guide (even on Windows!) The one in the Windows Lollipop deodex guide is old, and can't handle 5.1.1 and/or TouchWiz.

[GUIDE] Any Custom Modified Kernel Flashing Guide For Smoother And Better Performance

●BRIEF INTRODUCTION :-
•Many Users Prefer To Use Custom Kernels For Advanced Functionality Like Better DeepSleep/Permissive SE Linux For Audio Mods/Battery Life Improvements/Wakelocks And Hotplugs Etc.
•Dirty Flashing Of Custom Kernel Without Wipe/Over Flashing Of Same Roots/Flashing Root On One Another Without Removing Previous Root's Residuals Remained In Root Directories Can Probably Cause Various Issues
•By Following This Simplified And Detailed Guide Users Can Avoid Such Possible Further Flashing Issues
●GUIDE IS USEFUL FOR :-
•Users Facing Issues Like Device Hanging/Random Reboots/Software Glitches Etc.
•Users Facing Issues Like Unexpected Battery Drain/SOD/DeepSleep Broken Etc.
•Users Facing Issues Like Root Not Detected/Root Functionality Issues Due To Over Flashing Of Same Roots/Different Root Flashing On One Another Without Removing Previous Root's Residuals Remained In Root Directories Etc.
●PRE-REQUISITES :-
•Before Installing Any Custom Kernels To Avoid Further Flashing Root Messup/Root Misbehavior Kindly Follow The Below Steps To Make Your Device Clean By Removing Remained Residuals Of Previous Root For Only One Of Preferred Root Choices At A Time Either Magisk Root OR SuperSU Root
•Removal Of Previous Root's Residuals Remained In Root Directories For Root Switching Purposes
Like For Eg. Switching From SuperSu To Magisk OR Switching From Magisk To SuperSU Etc.
Note :-
+Switching From Magisk Root To SuperSU Root :-
*If You Were Previously On Magisk Root, Then Flash Latest Available Magisk Uninstaller First
*It Will Remove All Previously Flashed Magisk Root's Residuals Remained In Root Directories
*Now You Are All Ready To Flash SuperSU Root Along With Custom Kernel Without Any Possible Flashing Errors
+Switching From SuperSU To Magisk Root :-
*If You Were Previously SuperSU Root Then You Have To Unroot/Remove SuperSU Root First To Use Magisk Root Without Any Issues
*Before Booting Your Device Into TWRP-Custom-Recovery/Flashing Custom Kernel Kindly Follow Below Steps
*Open SuperSU App> Go To Settings> Select Full Unroot> Select 'Continue'> Select 'No' When Asked For 'Attempt To Restore Stock Boot Image'> SuperSU Will Unroot Your Device Automatically> Your Device Will Reboot Afterwards> You Can See SueprSU App Is Disappeared From AppDrawer
*But Still There Are Some SuperSU Root's Residuals Remained In Device System Root Directories
*Kindly Flash UPDATE-unSU-Signed Zip By @osm0sis You Can Find Below Through TWRP Before Flashing Custom Kernel To Remove All Remained Residuals Of SuperSU Root In Device's Root Directories
*Direct Link To Thread And Download For UPDATE-unSU-Signed Zip :-
https://forum.xda-developers.com/showpost.php?p=63615067
*Now You Are All Ready To Flash Magisk Root Along With Custom Kernel Without Any Possible Flashing Errors
●INSTALLATION INSTRUCTIONS :-
•Boot Your Device Into TWRP-Custom-Recovery
•Wipe Dalvik/Art And Cache
Note :-
*This Step Is Always Recommended Before Flashing Custom Kernels Over Stock/Any Other Custom Kernels
*This Step Is Not Always Recommended Before Flashing Stock Kernels Over Stock/Any Other Custom Kernels
•Flash Custom Kernel With Your Preferred Root Choices Either Magisk Root OR SuperSU Root
•Flash BusyBox Version Of Your Preferred Choice
Note :-
*Flashing BusyBox Is Totally Your Choice As Some Users Find It Useful While Some Not
*Also BusyBox Availability/Functionality Varies With Different Developers OfCourse
*Various Mods/Fixes Sometimes Needs BusyBox Installed/Enabled For Actual Working
*So You Can Flash Any Preferred BusyBox Version Of Your Own Choice According To Requirements
•Reboot Device From TWRP-Custom-Recovery
•Don't Touch Device For Atleast 5 Minutes To Make Custom Kernel Integrate With Both Hardware And Software For Performance Stability
•Reboot Device Again After 5 Minutes When Custom Kernel Gets Properly Integrated With Both Software And Hardware
Note :-
*Second Reboot Is Not Compulsory But Always Recommended For Smoother Experience
●Sticky Note :-
*I Am Aware Of Simultaneous Working Status Of Magisk Root With SuperSU Root And Vice Versa
*But I Always Prefer Clean Install Of Only One Preferred Root Choice After Removing Previous Root's Residuals Remained In Root Directories To Avoid Any Further Flashing Root Related Issues Already Mentioned
*Choice Is Yours Either To Use Both Roots Choices Simultaneously OR To Use Single Preferred One At A Time
* @The Joker And @haifish9999 Thanks Mates Because Of Your Discussion And Custom Kernel Threads I Was Encouraged To Make This Guide Publicly For Benefits Of Every Single User Here On Xda

What about flashing modules with kernel ?
Do you need to flash Kernel modules with your built kernel as well or it(your built kernel) would boot with stock kernel modules too ?
What about wiping "/data/" partition? is it necessary?

Unable to install stock apps

On a rooted Moto G5 plus running 5.8.4 RR. How do I flash my stock Moto Apps?

With this (Magisk Module) you can install vendor apps from PlayStore or Manually, but some apps dont launch properly
https://forum.xda-developers.com/apps/magisk/module-xmlpak-install-vendor-apps-t3701604

Be aware, most of them won't work anyway even if you install them, especially Moto Display and Gestures, as the framework in the stock ROM is proprietary and not implemented in custom ROMs.

Also, custom ROMs already have active display and gestures built-in. Which stock apps are you trying to install?

How can I root my Moto g4 plus correctly?

I tried all methods which are there on site but each time same and only problem is coming that is my phone is not getting rooted correctly I tried so many times but when I'll check with root checker it says it's not rooted but I successfully unlocked bootloader but I can't complely root it, can someone help me?

What device do you have and what ROM are you running?
If you're rooting on the stock Motorola ROM, do you have TWRP flashed/booted, then flashed ElementalX? Afterwards, what root managers are you using? You could try magisk 16 or 15.3. However, if you've previously used SuperSU or another root manager, you may have to re-flash the original stock kernel (then flash ElementalX then root) to remove any remainders of the old root managers, else they may interfere with magisk to the point of the root not being stable.

I have Moto g4 plus XT 1643 and I tried to root with by using twrp latest version and lineage os 14.1 athene. The was working fine but my phone is still showing that this device is not rooted

MsK96918 said:
I have Moto g4 plus XT 1643 and I tried to root with by using twrp latest version and lineage os 14.1 athene. The was working fine but my phone is still showing that this device is not rooted
Click to expand...
Click to collapse
What root manager are you using? The official Lineage OS (as of Jan 2017) does not come with a root manager, you must download and flash your own. You could either use the Lineage_SU_addon (you'd want the arm variant for 14.1) or magisk or SuperSU as a root manager.

I am new in this so I don't know that much details so can you help me by giving me link so that I can go through step by step and try to do what you are saying

MsK96918 said:
I am new in this so I don't know that much details so can you help me by giving me link so that I can go through step by step and try to do what you are saying
Click to expand...
Click to collapse
1)Download the Lineage SU addon (from here https://download.lineageos.org/extras - you want the arm 14.1 zip) OR magisk (from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 ) Only download one, please and if you want to switch, you ideally want to restore your backup or dirty flash the custom ROM to restore the Lineage kernel.
2)Reboot your device to TWRP.
3)In TWRP backup your device. Keep this backup safe.
4)In TWRP, go to 'Install' and flash the package you downloaded.
5)Wipe cache and Dalvik in TWRP after the flash.
6)Reboot.
7)Verify you have root.
You may also wish to browse the Lineage 14.1 thread for our device here: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101 Please use the search function by the page numbers to quickly search the thread for information

echo92 said:
1)Download the Lineage SU addon (from here https://download.lineageos.org/extras - you want the arm 14.1 zip) OR magisk (from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 ) Only download one, please and if you want to switch, you ideally want to restore your backup or dirty flash the custom ROM to restore the Lineage kernel.
2)Reboot your device to TWRP.
3)In TWRP backup your device. Keep this backup safe.
4)In TWRP, go to 'Install' and flash the package you downloaded.
5)Wipe cache and Dalvik in TWRP after the flash.
6)Reboot.
7)Verify you have root.
You may also wish to browse the Lineage 14.1 thread for our device here: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101 Please use the search function by the page numbers to quickly search the thread for information
Click to expand...
Click to collapse
Thank you bro i finally rooted my device correctly . It help alot thank you once again

Hi I'm new to XDA Forums, I was searching for posts about rooting my Moto g4 Plus. I would like to know Why we should flash a kernel before flashing SuperSU or Magisk ? Nb: I just only want the root access. Not in a plan to flash a custom rom. Thanks in Advance.

vinayroffl said:
Hi I'm new to XDA Forums, I was searching for posts about rooting my Moto g4 Plus. I would like to know Why we should flash a kernel before flashing SuperSU or Magisk ? Nb: I just only want the root access. Not in a plan to flash a custom rom. Thanks in Advance.
Click to expand...
Click to collapse
The stock Motorola kernel in stock Nougat ROMs appears to have anti rooting measures included (I think DM Verity?) If you attempt to root on this stock Nougat kernel, you'll likely soft brick/bootloop your device.
A custom kernel (e.g. elementalX v2.0.1 for stock) does not have these anti rooting defences, so it's safer to root with magisk. I would recommend magisk as super SU hasn't been updated in some time.
It appears that this need to flash a custom kernel before rooting applies to Nougat stock ROMs; marshmallow stock ROMs and the Oreo soak test stock ROM appear not to require a custom kernel.
As an aside, custom kernels and root are not necessary to flash custom ROMs. The only tools you require are an unlocked bootloader and the correct TWRP. The kernels included with these custom ROMs may also have anti rooting measures disabled, so it's safer to directly root without having to use a custom kernel.