Database Users

[How To] Install TWRP on OS 4.5.3 and Boot Recovery (newbie friendly)

TWRP (Team Win Recovery Project) replaces a device's stock recovery and provides, among other options, the ability to install img (image) and zip files. TWRP for the Fire HDs was developed by JMZ and is described here.
How to install TWRP
These steps are for a first-time install on a rooted Fire HD running OS 4.5.3 with stock bootloader and recovery.
At this time, 4.5.3 bootloader is required. You're welcome to try to get it onto a different OS, but you need the 4.5.3 bootloaders and I'm not getting into that. So, if you're running a different OS, have messed with partitions or done something that requires a TWRP reinstall (other than reinstalling 4.5.3 and rerooting), you risk being unable to boot recovery or bootloop/brick.
OK, that doesn't sound so "newbie-friendly" but this really is a simple process that should always go smoothly on a "clean" OS 4.5.3.​
You can easily install TWRP with either TWRP Manager (also by JMZ) or Flashify from the Play Store.
If you don't have Play Store access:
- Flashify - v 1.9.1 from APKMirror
- TWRP Manager - Download from JMZSoftware​For installing TWRP, the only difference between the two is that TWRP Manager auto-downloads the correct TWRP version while Flashify requires you download it yourself.
[EDIT 8/16/2015] At this time, TWRP Manager doesn't seem to be working. Use Flashify, instructions below. Steps for TWRP Manager are at bottom of post.
Install TWRP with Flashify
Download JMZ's ariel TWRP image (https://www.androidfilehost.com/?fid=24052804347756852) to the Fire's download folder.
Install and run Flashify (download link above) and give it superuser access when prompted. It probably will also prompt to apply loki patch for Kitkat. Say yes.
Tap Recovery Image and then Choose a File.
Navigate to download folder, tap the TWRP file, and when Flashify asks if you are sure, tap Yup!
If install succeeds ("Flash Complete"): (a) Tap Reboot now. (b) When back in Fire OS, boot to recovery (below) and confirm you're in TWRP. Note: If tablet bootloops, post the problem in one of the bootloop threads.
If install fails (error messages displayed), first take a screenshot. If you can determine the problem, fix it and try again or try TWRP Manager. If you don't understand the error or can't resolve it, post in a "TWRP install failure" thread.
How to Boot to Recovery
Manual: (a) Power off tablet. (b) Hold down power and volume-up buttons at same time until you see "Amazon," then release. (If you just boot back into Fire, you didn't power off first or didn't hold buttons long enough.)
adb command from computer: adb reboot recovery
- If you see TWRP, great! Check it out and then press Reboot and System to go back to OS.
- If you get stock recovery screen ("reboot" and "factory reset"), TWRP didn't install. Reboot should be highlighted. (If it's not, use volume-up or -down to select it.) Press the power button to click reboot and when back in Fire OS, try the other app.
[EDIT 1] For simplicity, install TWRP Manager on the Fire and follow these steps.
Install TWRP with TWRP Manager
Install and run TWRP Manager and give it superuser access when prompted. It will also prompt to apply patch for Kitkat. Say yes.
Tap top-left of screen for slide-out menu and select Install TWRP.
Confirm Device Name shows "ariel" and then tap Install Recovery. [download begins]
At warning screen, tap yes.
If install succeeds ("Flash Successful"): (a) Go to slide-out menu and choose Reboot Options and then Reboot Device. (b) When back in Fire OS, boot to recovery (above) and confirm you're in TWRP.
Note: If tablet bootloops, post the problem in one of the bootloop threads.
If install fails (error messages displayed), take a screenshot in case you need to post the problem and then look at comments here for a solution. If you can determine the problem, fix it and try again or try Flashify. If you don't understand the error or can't resolve it, post in a "TWRP install failure" thread.

After step 5 a) only puts on the screen "Kindle Fire" and I can not make the "Power and Volume up buttons reboot".
Could you help me please?

Po069 said:
After step 5 a) only puts on the screen "Kindle Fire" and I can not make the "Power and Volume up buttons reboot".
Could you help me please?
Click to expand...
Click to collapse
I'm sorry I can't help you. This guide is for the 2014 Fire HD tablets. The Kindle Fires are ealier models. Look here to figure out which tablet you have and then post the problem in the forum for your tablet:http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350

DoLooper said:
I'm sorry I can't help you. This guide is for the 2014 Fire HD tablets. The Kindle Fires are ealier models. Look here to figure out which tablet you have and then post the problem in the forum for your tablet:http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350
Click to expand...
Click to collapse
Thank you very much for your answer.
Kind regards.

Sorry if this is a stupid question, but if I update the Fire OS after successfully rooting/installing TWRP will I mess up anything?
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates). If I update the OS now will it brick it or mess up TWRP in any way?
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Thanks for your help!

SpaceBananas said:
Sorry if this is a stupid question, but if I update the Fire OS after successfully rooting/installing TWRP will I mess up anything?
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates). If I update the OS now will it brick it or mess up TWRP in any way?
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Click to expand...
Click to collapse
If you update now without following that guide you will lose root and TWRP. You may not be able to root with Kingroot and you won't have the "friendly" bootloaders that can boot TWRP. Don't do it.
I'll have to get back to you about updating. Maybe bibikalka will jump in. Look around for a KitKat version of pico-uni Gapps, which you could install in TWRP now. There will be link in an old guide for OS 4.

SpaceBananas said:
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates).
. . .
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Click to expand...
Click to collapse
OK, I looked at the guide again. @bibikalka may have a preferred route, but here's what I suggest: Pretend nothing else is there except steps 1) through 3) and just carefully follow those steps.
Download all the files to the pc first. Get the 5.1.1 update (only because we know it's rootable with Kingroot) and rename the extension from bin to zip. Skip Xposed (step 1-7). Do get 5.2.0_stock_recovery_uboot.zip (step 1-10). Copy or move all the files to the downloads folder on device. (This is the long way and you can download directly to device if you prefer. I just find it easier to download and double check that you have all the right files from the pc.)
Hold Power and volume+ to get into TWRP, then carefully do all the sub-steps under 1) except for step 7. (From what you say, I just don't think you need Xposed.) Just be sure you have the correct file at each step and you'll be fine.

DoLooper said:
OK, I looked at the guide again. @bibikalka may have a preferred route, but here's what I suggest: Pretend nothing else is there except steps 1) through 3) and just carefully follow those steps.
Download all the files to the pc first. Get the 5.1.1 update (only because we know it's rootable with Kingroot) and rename the extension from bin to zip. Skip Xposed (step 1-7). Do get 5.2.0_stock_recovery_uboot.zip (step 1-10). Copy or move all the files to the downloads folder on device. (This is the long way and you can download directly to device if you prefer. I just find it easier to download and double check that you have all the right files from the pc.)
Hold Power and volume+ to get into TWRP, then carefully do all the sub-steps under 1) except for step 7. (From what you say, I just don't think you need Xposed.) Just be sure you have the correct file at each step and you'll be fine.
Click to expand...
Click to collapse
Any point in using 5.1.1 ? Since SuperSu gets flashed during the update, it does not care which FireOS version it is. Nobody will be running Kingroot since SuperSu is already there

bibikalka said:
Any point in using 5.1.1 ? Since SuperSu gets flashed during the update, it does not care which FireOS version it is. Nobody will be running Kingroot since SuperSu is already there
Click to expand...
Click to collapse
No, 5.1.2 is fine. It was just a cya suggestion in case user missed a step and somehow lost root--but OF COURSE no steps will be missed.

TWRP failed to install, now have no recovery
So I'll start by saying I'm an idiot. I wasn't paying attention to which version OS is required and tried to install TWRP using Flashify. It went through the motions and did its reboot, and now I'm stuck with absolutely no recovery at all. I've tried searching these forums for a "TWRP installation failed" thread and have had no luck, at least not for the Fire HD 6 device. Really need help here, I have absolutely no way to get into recovery to flash anything back at all.

[Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly")

This guide is for never-rooted 2014 Fire HDs. Don't use it on any 2015 (5th gen) Fire. If your Fire has an sd card slot, go here.
Mar 3 Update: This guide is out of date. It could brick you! Don't use it!
Instead, follow one of these guides:
http://forum.xda-developers.com/fire-hd/general/root-os-5-1-2-kingroot-tools-play-store-t3371824
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Ignore these hidden text boxes
Feb. 5, 2016 Update: Don't use this to root OS 5.1.1 yet. It needs to be updated!!
Jan. 18, 2016 Update: Don't use this guide if you are running OS 4.5.5.1.
Look at Settings->Device->System Updates. If it says 4.5.5.1, installing the Developer Preview will brick your device.
Before You Begin:
OS 4.5.4, 4.5.5 (NOT 4.5.5.1) - Follow these steps to install the Developers Preview (OS 5):
Here are 2 methods. If you request it from Amazon it could take 24 hours, but if it causes problems you have proof that it downloaded to device. If you don't care about that and want it right now, use method 2.
1/23/16 UPDATE: Developers Preview is no longer available from Amazon. Method 2 is the only option.
Keep in mind, this is your choice. We can no longer blame Amazon for downloading "bad" firmware to device.
1/22/16 UPDATE: Use only method 2 until the risk of OTA updating to 4.5.5.1 is over.
METHOD 1 - From Amazon
Go here and request the developers preview: https://developer.amazon.com/public...campaign=FireOSPreview&sc_ detail=GetPreview]
It could take 24 hours but usually doesn't.
Goto Settings->Device->System Updates and press "Update Now"
If it doesn't download, wait an hour and try again.
METHOD 2 - From device
Turn OFF wifi.
Get update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin from here.
Copy/move the update file to device
Goto Settings->Device->System Updates and press "Update Now"
The file will install. [long startup.]
If you haven't installed adb drivers, do that now and you're ready to go! Be sure to keep wifi off.
Note: If it hasn't booted after 20 minutes--it's stuck at "Fire" logo--hold down Power and Volume-up buttons to get to recovery menu. In recovery, factory reset, wipe cache and then boot to system.
OS 4.5.3 - Keep wifi OFF. Put the tablet into airplane mode immediately.
.
OS below 4.5.3 - Follow these steps to install OS 4.5.3:
Turn OFF wifi.
Download the 4.5.3 update to pc and copy/move it to device.
Go to Settings->Device->System Updates and press "Update Now."
The file will install. [long startup.]
If you haven't installed adb drivers, do that now and you're ready to go!
Install adb device drivers. Here's an illustrated guide for Windows.
* OS 5.0.n: Install driver for both OS mode and sideload mode.
* OS 4.5.3: Install driver for OS mode only.)
.
If you don't know how to drag & drop or copy/paste into the terminal/CMD window, read this.
This guide simply pulls together existing material, almost none of which is original to me. All thanks go to Powerpoint45, who discovered how to downgrade to rootable OS 4.5.3; bibikalka for the ingenious recovery-swap update method that preserves root; seigesoldier, hawkazn and hariiiii for file captures and fearless testing.​
A - Root!
Make sure ADB drivers are installed and adb is enabled in Developer Options.
Turn OFF wifi (airplane mode)
OS 4.5.3 - Download Kingroot (link below), open a terminal/CMD window from the folder you put it in, and go to step 6.
OS 5.0.n - Download to computer:
- 4.5.3 update bin: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
- Kingroot: http://www.kingroot.net/
Downgrade to 4.5.3 (thanks to @powerpoint45):a. Connect to computer and open terminal/CMD window from folder containing bin file and kingroot.
b. Enter: adb reboot recovery
c. On tablet, use volume buttons to select “apply update from ADB” and then press power.
d. If you KNOW you have working adb driver for sideload mode, go to step e. Otherwise, see here:
To see if sideload-mode driver is installed, open Device Manager and see if your adb driver is listed under Android Device.
- If it is, close this text box and continue the steps.
- If it IS NOT and you're on Windows, do the following:
(1) Find KFARWI under "Other devices." NOTE: If you don't see KFARWI under "Other," disconnect/reconnect and look again.
(2) Right-click KFARWI and select "Update Driver Software." [see Update Driver Software screen].
(3) Click "Browse my computer" and then "Let me pick from a list . . ." [see Select your device type . . ."]
(4) Click Android Device. [see "Select the device driver you want . . .]
(5) Select your usual adb driver from the list, press Next, and say yes at warning screen. [see "Windows has successfully updated your driver software"]
(6) In CMD window, run adb devices and confirm you see your device ID and "sideload," like this:List of devices attached
SERIALNUMBER sideload​If you don't see serial number, reboot tablet and computer and repeat "adb reboot recovery" and "Apply update from ADB" steps. Device should now be recognized.
e. From computer, enter: adb sideload update-kindle-20.4.5.3_user_453011120.bin
f. On tablet select "wipe data/factory reset" and then "reboot system" [long startup]​
Enter language in Amazon setup, but skip registration and keep wifi OFF.
On computer, enter commands to block OTA:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Install Kingroot from computer: adb install app_filename.apk
Turn on wifi, run Kingroot on Fire and press "root." If you don't get success (100%), keep trying.Kingroot works over wifi, so do this where signal strength is best.
If the latest Kingroot from the link just won't work, try version 4.0.0 or 4.0.1 downloaded from any safe site.​
On computer, give commands to confirm su access, granting root access on tablet when prompted:
adb shell
su
(In Windows, a # prompt indicates root.)
Type exit two times to get out of su.
B - Install TWRP and Get Files for the Upgrade
Download JMZ's ariel TWRP image to the Fire's download folder (or to computer and move to tablet).
Download Flashify v 1.9.1 to computer folder where you opened CMD window.
Install Flashify from computer: adb install app_filename.apk
Run Flashify on Fire and install the ariel TWRP.
If you have any question, follow the steps here. You must select Recovery image and Choose a File, and navigate to the ariel image.
Boot to recovery and confirm you're in TWRP:
adb command = adb reboot recovery; manual = power off, hold power & volume-up buttons until Amazon logo appears and then let go.
Tap Reboot, then System to boot back to OS.
Delete anything in tablet Download folder and get files for the upgrade.
.
Files for the Upgrade
Please hit Thanks when you pick up a file from an XDA site
Download apks to computer for later install.
- SuperSU: http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-52-android-apk-download/
- ES File Explorer: http://www.apkmirror.com/apk/es-glo...file-explorer-4-0-2-3-3-android-apk-download/
Download to tablet (or to computer and move to tablet Download folder):
➜ Take care here: Be sure to get the right files and that they all download completely.
- 5.2.2u2 UPDATE BIN (linked in the post) This is update-kindle-full_ariel-20.5.2.2_user_522053520.bin
Confirm downloaded filename matches the above and then rename the extension from .bin to .zip.
- 5.2.0 STOCK RECOVERY ONLY (5.2.0_stock_recovery_only.zip - attached to post) AND . . .
- MAKE_SPACE (make_space_v01.zip - attached to post)
- Latest PICO-uni GAPPS: Get "tk_gapps-modular-pico-5.1.1(uni)-5.1.1-*-signed.zip"
C - Upgrade to OS 5.0.1 and Install Gapps
Bibikalka's Lollipop guide has info about the upgrade (and a Thanks button we all ought to hit!)
The boots into recovery and the OS can take a long time; don't interrupt them (by trying to manually reboot, e.g.)
Turn OFF wifi and connect to computer.
Boot to recovery. (Manually or "adb reboot recovery" from pc).
[TWRP screen displayed on tablet.]
In TWRP, do following exactly and if you have any problem, post immediately and wait for reply :
a. Factory reset (Tap Wipe and swipe "Swipe to Factory Reset." At "Successful," tap TWRP home icon at bottom-left)
b. Install the update-kindle-full_ariel-20.5.2.2 UPDATE zip
. . (Tap Install button, navigate to Downloads folder and tap the UPDATE zip. Repeat for the following zips.)
c. Install the 5.2.0 STOCK RECOVERY ONLY zip
d. Install the MAKE_SPACE zip
e. Install the GAPPS zip
f. Tap Reboot > Recovery and when prompted (top of screen) "install SuperSU?," swipe the slider to install it!
[long startup]
➜ You're now running rooted OS 5.0.1 and TWRP is gone. If you need it again, see here. Do not try to reinstall TWRP with Flashify. (Brick!)
Confirm you see stock 5.2.0 recovery.
If tablet doesn't boot to recovery or is still booting after 30 minutes, post in bibikalka's Lollipop thread
Reboot to system [takes at least 10 minutes] and when prompted on tablet to allow USB debugging, say "yes"
- If you miss "Allow USB debugging" prompt, unplug/replug to see it
- If tablet bootloops or is still booting after 40 minutes, see step 4 in bibikalka's Lollipop thread
At Setup screen, press Exit (or choose language if required). Do not connect to wifi; tap COMPLETE SETUP LATER.
D - Install the Apps, Block OTA and Open Play Store
On computer, open terminal/CMD window from folder containing ES File Explorer and SuperSU apks and install each with this command:
adb install -r app_filename.apk
On tablet:
a. Enable apps from unknown sources in Settings > Security.
b. Run File Explorer and enable Root Explorer (in menu under Tools), granting root access when prompted.
c. Run SuperSU to update binaries and reboot when prompted.
. . [If SuperSU gives choice of "CWM/TWRP" or "Normal," choose Normal]
Block OTA:
a. In the terminal/CMD window, enter these commands granting root access on tablet after the su command:adb shell
su
pm disable com.amazon.otaverifier
pm enable com.amazon.dcp <--(renables dcp from Section A. This block is not needed after you do the next step.)​b. Use File Explorer on tablet to navigate to /system/priv-app/DeviceSoftwareOTA and rename extension of DeviceSoftwareOTA.apk to .apk_
Turn on wifi, open Play Store and sign in.
Register the Fire HD with Amazon.
Whew! Yay! :victory:

Some brave soul still needs to try to flash GAPPS during the 5.2.0 install in TWRP
If that fails, one will have to downgrade to 4.5.3, root, and get back to 5.2.0. So 20 minutes tops, not the end of the world ...

Yes, purposefully didn't put it in cuz untested. I'm thinking about it per your post at other thread. Just need to gird my loins

In Section C Step 7 adb returns failure due to the app already existing. When I was in Step 3f TWRP gave me the option to skip root install or to install SuperSu, which it only does the installer and that requires Google Play or TWRP to complete the installation. What should I do there?

ROMAddiction said:
In Section C Step 7 adb returns failure due to the app already existing. When I was in Step 3f TWRP gave me the option to skip root install or to install SuperSu, which it only does the installer and that requires Google Play or TWRP to complete the installation. What should I do there?
Click to expand...
Click to collapse
As the first line says, This guide is only for Fire HDs running the unrooted Developer Preview of Lollipop. I will clarify that. Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk." I assume you said yes at step 3f when prompted to root, but I do not understand this phrase, "which it only does the installer and that requires Google Play or TWRP to complete the installation."

DoLooper said:
As the first line says, This guide is only for Fire HDs running the unrooted Developer Preview of Lollipop. I will clarify that. Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk." I assume you said yes at step 3f when prompted to root, but I do not understand this phrase, "which it only does the installer and that requires Google Play or TWRP to complete the installation."
Click to expand...
Click to collapse
Yeah, I started out with my Fire on the developer's build and have been working my way back to it with root. I did say yes at step 3f and TWRP then installed a SuperSu Installer App. When you tap on the app it says it will install SuperSU but either from the Google Play Store or through TWRP. This is where I'm stuck because I can't install it from the Play Store or from TWRP, nor can I use ADB and install it from there because it says that SuperSu is already on my Fire.
Sent from my LG-H811 using XDA Forums Pro.

ROMAddiction said:
Yeah, I started out with my Fire on the developer's build and have been working my way back to it with root.
Click to expand...
Click to collapse
If you were on 4.5.4 and wanted to get to rooted 5.2.0, this is the guide you wanted: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950. But I thought you had done that and that's when you lost recovery. Oh, well, doesn't matter now, as long as you were able to boot to stock recovery at step C4.
Did you reinstall superSU with "adb install -r name_of_your_supersu.apk." as said in my last post? (Notice the -r) Please do that and continue the steps. Let me know if "adb shell" "su" does not show you're rooted. If step 13 insists on Play Store, skip that step, finish the guide and run SuperSU after Gapps is installed. Please let me know if you have to skip step 13, so I can edit the guide. Thank you.
DoLooper said:
. . . Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk."
Click to expand...
Click to collapse

DoLooper said:
If you were on 4.5.4 and wanted to get to rooted 5.2.0, this is the guide you wanted: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950. But I thought you had done that and that's when you lost recovery. Oh, well, doesn't matter now, as long as you were able to boot to stock recovery at step C4.
Did you reinstall superSU with "adb install -r name_of_your_supersu.apk." as said in my last post? (Notice the -r) Please do that and continue the steps. Let me know if "adb shell" "su" does not show you're rooted. If step 13 insists on Play Store, skip that step, finish the guide and run SuperSU after Gapps is installed. Please let me know if you have to skip step 13, so I can edit the guide. Thank you.
Click to expand...
Click to collapse
Ah, no I had been updated to 4.5.5 the other day and was wanting to roll back and root my Fire to make it much more useful to me. Signed up as a Developer to get it to update me to the 5.2 update and then followed the steps here to get me rooted and back to 4.5.3, etc.
I did the adb install -r with the apk and it loaded, but not in the app drawer. I could find it in Settings under Apps but the App Info wouldn't let me do anything like Force Stop or Clear Cache. Thinking that I may have to start back over from the beginning to fix this. Always make some sort of screw up when I do this sort of thing. Hopefully I won't have to bother you with anything again. I'll check to see if abd shell will tell me if I'm good and get back to you. Thanks for the help!
Sent from my LG-H811 using XDA Forums Pro.

ROMAddiction said:
I did the adb install -r with the apk and it loaded, but not in the app drawer. I could find it in Settings under Apps but the App Info wouldn't let me do anything like Force Stop or Clear Cache. Thinking that I may have to start back over from the beginning to fix this. Always make some sort of screw up when I do this sort of thing. Hopefully I won't have to bother you with anything again. I'll check to see if abd shell will tell me if I'm good and get back to you. Thanks for the help!.
Click to expand...
Click to collapse
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.

DoLooper said:
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
Click to expand...
Click to collapse
Alright! When I get home tonight I'll complete the rest of the steps as best as possible.
Sent from my LG-H811 using XDA Forums Pro.

Hint: You can also flash tk gapps in twrp

meganoahj said:
Hint: You can also flash tk gapps in twrp
Click to expand...
Click to collapse
Right! Did you do that--flash 5.2.0 UPDATE, RECOVERY then GAPPS before rebooting to 5.2.0 recovery? Bibikalka and I have been wanting to know if that'd been tested yet. thanks.

DoLooper said:
Right! Did you do that--flash 5.2.0 UPDATE, RECOVERY then GAPPS before rebooting to 5.2.0 recovery? Bibikalka and I have been wanting to know if that'd been tested yet. thanks.
Click to expand...
Click to collapse
Yes i done that, now you have The new lollipop Google Login when you add a Google account
And All works play Services updating and All fine (im on OS 5 with root,tkgapps,xposed framework)

meganoahj said:
Yes i done that, now you have The new lollipop Google Login when you add a Google account
And All works play Services updating and All fine (im on OS 5 with root,tkgapps,xposed framework)
Click to expand...
Click to collapse
Hey, that's great! Couple questions:
You got Gapps from here? http://forum.xda-developers.com/android/software/tk-gapps-t3116347/post60944096#post60944096
Which package?
Do you know how much space you had left in /system after the update (and before you added anything else)?
Any chance you flashed Xposed at same time?
 @bibikalka will also be glad to hear this! Thanks!

DoLooper said:
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
Click to expand...
Click to collapse
When I perform: option: adb shell
su
It returns 1|[email protected]:/ $
I'm going to try "option: adb install -r name_of_your_supersu.apk" here and see if that makes a difference.
Edit: That did it! SuperSu installed, Google Play Store/Services installed, and I'm good to go.

DoLooper said:
Hey, that's great! Couple questions:
You got Gapps from here? http://forum.xda-developers.com/android/software/tk-gapps-t3116347/post60944096#post60944096
Which package?
Do you know how much space you had left in /system after the update (and before you added anything else)?
Any chance you flashed Xposed at same time?
@bibikalka will also be glad to hear this! Thanks!
Click to expand...
Click to collapse
Yes i got gapps from There
Gapps: Pico Modular Package (Proper DPI Play Services)
I flashed xposed after the reboot to fire os 5 (back to twrp method)
but i think you can flash xposed after the gapps!
And i dont Know the space free in /system cuz im installed gapps directly after flashing the Update!

Ah sorry i forget that after i flashed xposed framework anytime my fire boots i got the android is upgrading screen
10 seconds long

meganoahj said:
I flashed xposed after the reboot to fire os 5 (back to twrp method)
but i think you can flash xposed after the gapps!
And i dont Know the space free in /system cuz im installed gapps directly after flashing the Update!
Click to expand...
Click to collapse
I meant how much space in /system after you got back to OS , after the upgrade and before deleting/adding any system apps. So, how much space in /system now?
meganoahj said:
Ah sorry i forget that after i flashed xposed framework anytime my fire boots i got the android is upgrading screen
10 seconds long
Click to expand...
Click to collapse
I got Xposed same way as you and don't get that. Maybe it's a module you installed(?)

Other than Kingroot taking forever and Xposed refusing to flash in TWRP everything went great and I was finally able to install all my apps from the Play Store on my wife's tablet following this guide.
Many thanks!

DoLooper said:
I meant how much space in /system after you got back to OS , after the upgrade and before deleting/adding any system apps. So, how much space in /system now?
I got Xposed same way as you and don't get that. Maybe it's a module you installed(?)
Click to expand...
Click to collapse
With gapps + xposed is 49.8 mb free in /system
I had the upgrading screen also without an Module

[How to] Upgrade to 4.5.5.1 (or other 4.5.x) with root in TWRP:

Update2: Updated for FireOS 4.5.5.1. Note that you can root 4.5.5.1 directly via Kingroot. With root, you could get TWRP to work, and re-install any FireOS 4 or 5 with all the goodies. The instructions to get TWRP working are here (you need to flash 4.5.3 bootloaders if you do not start with FireOS 4.5.3 !!!) : http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Update: I had a couple of knee-jerks, but realized that I can make TWRP say "full_ariel" (I've changed the string), which enables the standard Amazon update files to work !!! I did test the modified TWRP (and the attached zips), everything works fine.
This 4.5.5 update provides no perceptible difference with 4.5.4, and everything has been running smoothly for me for the past few weeks. So out of the general principle I do recommend upgrading!
If you are just joining us, and have a pristine Fire HD, head over here to get your fire rooted and TWRP installed [all steps up to and including 3) ] :
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
With TWRP installed, there is a quicker way to install 4.5.5, without changing the update file (in contrast to my earlier instructions for 4.5.4). This is a dirty flash, and will keep all the prior settings and programs (if you have not had GAPPS yet, see additional instructions below):
0) Turn off wireless (airplane mode)
If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
1) Boot into TWRP, flash the attached 4.5.3_twrp_recovery_full_ariel_string.zip. Reboot to recovery (TWRP)
2) While in TWRP (this modified version self-identifies as full_ariel) :
a) flash the respective Amazon ROM 4.5.x update (the latest one?): http://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102 (rename to zip before flashing)
b) Must do this (!!!) - flash attached 4.5.3_twrp_recovery_uboot.zip
c) flash attached make_space_v01_fireos4.zip to remove moffice and weather in order to increase space in /system.
d) flash Pico (Uni) GAPPS for KK http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html [if you did not have GAPPS before, skip this for now, and come back after Step 3) ]
e) wipe cache and dalvik
f) before reboot say yes to root
3) Boot into fireOS (wait for it to upgrade)
a) install SuperSu
b) disable OTA updates [in ES Explorer rename /system/priv-app/DeviceSoftwareOTA.apk to *apk_ ] - The script in make_space*zip already renamed this file automatically, so nothing to do here.
c) install Xposed. Note if you are using 4.5.5.1, you'll need to get the Xposed installer from here in order to address SDK version 19 error :
http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
d) install Busybox
Optional 4) : if you did not install GAPPS in 2), boot to TWRP, and install GAPPS
That's it! Whatever you had working before, should be working now the exact same way.
If you prefer a manual way where you repackage the 4.5.5 update file (and perhaps remove some apps from /system), see these instructions (the updater-script is the same) :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648

Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
This package is for "full_ariel" products: this is a "omni_ariel"
E:Error executing updater binary in zip '/sdcard/Download/update-kindle-20.1.5.5_user_455001420.zip'
Click to expand...
Click to collapse

Sario27 said:
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
Click to expand...
Click to collapse
Yep, indeed! I wonder if TWRP could be patched such that the device is being identified as "full_ariel" even when rooted. Otherwise repackaging these ROM zips is a chore ...

bibikalka said:
Yep, indeed! I wonder if TWRP could be patched such that the device is being identified as "full_ariel" even when rooted. Otherwise repackaging these ROM zips is a chore ...
Click to expand...
Click to collapse
Having said that... is there a version of 4.5.5 that will work with root? I can repackage myself I suppose, but it is a mess to navigate that script...

Sario27 said:
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
Click to expand...
Click to collapse
meatwad12 said:
Having said that... is there a version of 4.5.5 that will work with root? I can repackage myself I suppose, but it is a mess to navigate that script...
Click to expand...
Click to collapse
I've updated the instructions. As the first step, you flash the modified recovery (which says "full_ariel"). This modified recovery will accept the standard Amazon update file. After the update is done, I have you flash the standard TWRP back (just in case) together with 4.5.3 bootloaders.

I don't understand new title, "Upgrade to 4.5.5 (or any 4.5.x) with root in TWRP:" Isn't this just for upgrading to 4.5.5? The files are for 4.5.5, so you wouldn't use it to upgrade to 4.5.4, right? (Yes, I'm going to post a pointer to all the guides. The choices are confusing even me, and I practically live here!) Also, if you see fit, could you add [How To] to title so this stands out with other upgrade guides? yr friend, Do consistency-my-middle-name Looper.

DoLooper said:
I don't understand new title, "Upgrade to 4.5.5 (or any 4.5.x) with root in TWRP:" Isn't this just for upgrading to 4.5.5? The files are for 4.5.5, so you wouldn't use it to upgrade to 4.5.4, right? (Yes, I'm going to post a pointer to all the guides. The choices are confusing even me, and I practically live here!) Also, if you see fit, could you add [How To] to title so this stands out with other upgrade guides? yr friend, Do consistency-my-middle-name Looper.
Click to expand...
Click to collapse
Wow, you are a hard man to please I've put a few changes in there, trying to make it more clear.
The procedure works for 4.5.4 as well, so that's why I try to keep things fairly generic.

bibikalka said:
The procedure works for 4.5.4 as well, so that's why I try to keep things fairly generic.
Click to expand...
Click to collapse
So would you say this supercedes http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613? Is this method "better?' thx

DoLooper said:
So would you say this supercedes http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613? Is this method "better?' thx
Click to expand...
Click to collapse
Potentially this will supersede this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
The difference is mainly not having to mess around with the update file (which has it's uses, if one wants to shrink the size of "system").

bibikalka said:
I've updated the instructions. As the first step, you flash the modified recovery (which says "full_ariel"). This modified recovery will accept the standard Amazon update file. After the update is done, I have you flash the standard TWRP back (just in case) together with 4.5.3 bootloaders.
Click to expand...
Click to collapse
This worked great for me. I have 4.5.5 running with the stock amazon ROM after following these instructions. Great work thank you!
---------- Post added at 03:19 PM ---------- Previous post was at 02:24 PM ----------
One problem...
I'm having a heck of a time trying to block ads in 4.5.5. I've tried the adb command pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.lockscreenupdateS ervice as mentioned in another thread but with no luck. Did Amazon change something in the structure of 4.5.5 that renders this method unworkable? Is there another way?

meatwad12 said:
I'm having a heck of a time trying to block ads in 4.5.5. I've tried the adb command pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.lockscreenupdateS ervice as mentioned in another thread but with no luck. Did Amazon change something in the structure of 4.5.5 that renders this method unworkable? Is there another way?
Click to expand...
Click to collapse
Did you put a space in "S ervice?" There is none, but it may display that way. So if you did, do it with no space and reboot afterwards if ads don't go away immediately. The other way is JMZ fire tool, but that does a chmod on ad folder and displays the "killed ads" message with every boot.
Please let me know if the pm block pm disable works or not. Thanks!

Looks like I'm good! I tried it several different ways (block vs. disable; with space and without) and it appears to have taken hold after a reboot. We can chalk this one up to user error. Thanks for the response.

meatwad12 said:
Looks like I'm good! I tried it several different ways (block vs. disable; with space and without) and it appears to have taken hold after a reboot. We can chalk this one up to user error. Thanks for the response.
Click to expand...
Click to collapse
Or u can upgrade to lollipop. Ads are disabled by default on lollipop. Here is the thread to lollipop with root. http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950

I followed the instructions and tried flashing gapps before the initial boot into 4.54 and also after booting but I get the same error. "insufficient storage space available in system partition"
I am flashing this version
pa_gapps-modular-pico(uni)-4.4.4-20150308-signed.zip it is 39,105kb.
this is on the 8gb model of the kindle hd 7, not sure if the 16 has a bigger system partition

mehmehmeh said:
I followed the instructions and tried flashing gapps before the initial boot into 4.54 and also after booting but I get the same error. "insufficient storage space available in system partition"
I am flashing this version
pa_gapps-modular-pico(uni)-4.4.4-20150308-signed.zip it is 39,105kb.
this is on the 8gb model of the kindle hd 7, not sure if the 16 has a bigger system partition
Click to expand...
Click to collapse
Did you flash the older 4.5.4 ? Or the newer 4.5.5 ?
Can you check how much free space you have in /system as is? (DiskUsage app in the store)
In any event, and easy quick hit (20Mb) is to remove something like /system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
You can remove more, as per this :
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3

flashed the newer 4.5.5. Will try later tonight, didn't get the amazon update disabled and woke up to a fire os 5 tablet. So I have to downgrade again

mehmehmeh said:
flashed the newer 4.5.5. Will try later tonight, didn't get the amazon update disabled and woke up to a fire os 5 tablet. So I have to downgrade again
Click to expand...
Click to collapse
Well, as they say, practice makes perfect !
I am surprised it managed to install itself with TWRP present instead of the stock recovery ...

Can you please upload the attachments to a file hoster cause the servers from xda are slow 14 kbps and downloads cancels!

bibikalka said:
Did you flash the older 4.5.4 ? Or the newer 4.5.5 ?
Can you check how much free space you have in /system as is? (DiskUsage app in the store)
In any event, and easy quick hit (20Mb) is to remove something like /system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
You can remove more, as per this :
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
Click to expand...
Click to collapse
Thanks for the tip!
Ran into the same issue while trying to upgrade my rooted 4.5.3 gapps Firehd 7..

Mhm Ok now I'm running into issues when trying to update the google play services, it always fails saying "not enough space available".
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
I've moved all the odexed system APKs mentioned in this post to /data/apps and I have 1.5gb free on the "sdcard".
:/
*Edit*
Nvm, found the reason...it's because I allready had gapps installed through jmz's tool and it blocked play services updates from being installed, because back then a play services update would break the entire thing again.
So I had to do these additional steps from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
0) If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
Click to expand...
Click to collapse
@op maybe include it in your updated guide for ppl who allready had gapps and used jmzs handy tool a couple months ago.

OS 5.0 + ROOT + GAPPS + Play Store VIDEO TUTORIAL

Please DO NOT use this guide anymore due to bricks. Instead use an up to date guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I was debating whether to make a new thread or not but ended up doing so. First off I want to thank the people on XDA including @bibikalka , @DoLooper , and @jmz who made everything work. I'm a visual & hands-on learner so I like making these types of tutorials and I hope others who favor more visual tutorials will find them useful as well. This video guide is a combo from guides from @bibikalka (ROOT & GAPPS & OTHER) , @DoLooper (ROOT & GAPPS & OTHER) , and @jmz (TWRP).
This video tutorial explains how you can get root, GAPPS, and the Play Store on Fire OS 5.0. This video is one of the more andvanced ones and contains many steps. I take no responsibility if something happens to your device. Try to follow the video as close as you can and you sould be fine. The basic process consists of downgrading to a root vulnerable OS, rooting it and installing TWRP, then through TWRP install the new 5.0 version and then GAPPS, root, etc.
Video
www.youtube.com/watch?v=gC0nm8I3IFE
Here are the in depth steps. Follow along with video for more insight:
1.Install USB ADB drivers: https://www.youtube.com/watch?v=CyJlmTtLsIg
Download Software version 4.5.3: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
Reboot into recovery: "adb reboot recovery"
Enter sideload mode from recovery
Install v4.5.3: "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
Wiipe data/ factory restet from recovery
Reboot & keep wifi off so that it does not re-update
Disable ota updates with "adb shell pm block com.amazon.dcp" and "adb shell pm block com.amazon.otaverifier"
Turn on wifi
Download kingroot from http://www.kingroot.net/ onto device
Root with app
Test root with "adb shell" and "su"
Download TWRP IMG: https://drive.google.com/file/d/0Bx_94ujbh0qobGpZcGV6aHNKT3M/view?usp=sharing
Check md5sum: 4fefd8b46ca97a2b66e4c8852d4c3396
Push recovery to device with "adb push openrecovery-twrp-2.8.6.0-ariel.img /data/local/tmp"
Go into root shell with "adb shell" and "su"
Go to /data/local/tmp/ directory: "cd /data/local/tmp/"
Install TWRP: "dd if=openrecovery-twrp-2.8.6.0-ariel.img of=/dev/block/mmcblk0p7"
Test TWRP with "adb reboot recovery"
Boot back up
Download 5.2.2 firmware: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
Download 5.2.0 stock recovery: http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
Download pico gapps package (Play Store etc): https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Download make_space zip: http://forum.xda-developers.com/attachment.php?attachmentid=3519998&d=1445918906
Move firmware, recovery, gapps, and make_space zip onto Fire internal storage
Rename 5.2.2 firmware to a .zip file instead of a .bin file so TWRP recognizes it
Reboot into TWRP: "adb reboot recovery"
STEPS 28-33 MUST BE DONE IN ONE SESSION
Do another factory reset
Flash 5.2.2 firmware
Flash 5.2.0 recovery
Flash/run make_space zip to clear up system space
Flash Pico GAPPS zip
Choose reboot into recovery from TWRP and tell TWRP that you would like to install superSU
Reboot device and wait for it to boot up (will take about ten minutes)
After booted up, disable ota updates with "adb shell", "su", "pm disable com.amazon.otaverifier", and "pm enable com.amazon.dcp"
Update SuperSU from Play Store, open it and choose to install normally
Root, GAPPS, and Play Store should all be working now
Click to expand...
Click to collapse
Notes:
Do not try to re-flash TWRP the same way you did on 4.4.3. It will not work
Click to expand...
Click to collapse
Links & Downloads:
•XDA Guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
•USB driver tutorial: https://www.youtube.com/watch?v=CyJlmTtLsIg
•4.5.3 software: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
•KingRoot: http://www.kingroot.net/
•TWRP image: https://drive.google.com/file/d/0Bx_94ujbh0qobGpZcGV6aHNKT3M/view?usp=sharing
•5.2.2 firmware: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
•5.2.0 stock recovery: http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
•pico gapps package (Play Store etc): https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
•make_space zip: http://forum.xda-developers.com/attachment.php?attachmentid=3519998&d=1445918906
Click to expand...
Click to collapse

Detailed tutorial
Will try later today.

Thanks a lot for the video. Used it and got everything working no problems!

argrr101 said:
Thanks a lot for the video. Used it and got everything working no problems!
Click to expand...
Click to collapse
Awesome to hear. Enjoy
Sent from my KFARWI using Tapatalk

powerpoint45 said:
I was debating whether to make a new thread or not but ended up doing so. First off I want to thank the people on XDA including @bibikalka , @DoLooper , and @jmz who made everything work. I'm a visual & hands-on learner so I like making these types of tutorials and I hope others who favor more visual tutorials will find them useful as well. This video guide is a combo from guides from @bibikalka (ROOT & GAPPS & OTHER) , @DoLooper (ROOT & GAPPS & OTHER) , and @jmz (TWRP).
This video tutorial explains how you can get root, GAPPS, and the Play Store on Fire OS 5.0. This video is one of the more andvanced ones and contains many steps. I take no responsibility if something happens to your device. Try to follow the video as close as you can and you sould be fine. The basic process consists of downgrading to a root vulnerable OS, rooting it and installing TWRP, then through TWRP install the new 5.0 version and then GAPPS, root, etc.
Video
www.youtube.com/watch?v=gC0nm8I3IFE
Here are the in depth steps. Follow along with video for more insight:
Notes:
Links & Downloads:
Click to expand...
Click to collapse
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update

2006yamahaR6 said:
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update
Click to expand...
Click to collapse
Hmm. Maybe try redownloading the update file as it cold be corrupted. I'm really not sure about this one
@DoLooper you've got any ideas?
Sent from my KFARWI using Tapatalk

@powerpoint45 Are you using the Amazon launcher or a custom one? Has anyone tried to change the launcher using the method that worked for 4.5.3?

2006yamahaR6 said:
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update
Click to expand...
Click to collapse
powerpoint45 said:
Hmm. Maybe try redownloading the update file as it cold be corrupted. I'm really not sure about this one
@DoLooper you've got any ideas?
Click to expand...
Click to collapse
Only that a search turns up lots of hits.

argrr101 said:
@powerpoint45 Are you using the Amazon launcher or a custom one? Has anyone tried to change the launcher using the method that worked for 4.5.3?
Click to expand...
Click to collapse
I'm using a custom one. If you have root just install your custom Launcher, go into adb shell, type "su", and then "pm disable com.amazon.firelauncher"
Sent from my SPH-L710 using Tapatalk

argrr101 said:
[MENTION=4469251]Has anyone tried to change the launcher using the method that worked for 4.5.3?
Click to expand...
Click to collapse
This is for latest OS 5.0.1 (5.2.2u2). Be sure to install custom launcher first. Need to be in SU.
pm disable com.amazon.firelauncher

Thanks, got Nova Launcher up and working.

cxm170 said:
Will try later today.
Click to expand...
Click to collapse
works like a charm
. thanks

Excellent write-up I didn't even bother watching the video... My hd6 is now working as it should!
One note - I had to register with both Amazon and Google via wifi before I could update SuperSU and disable ota updates through adb. Not sure if I did something wrong, but that's how it ended up working for me.

Hello, I have tried this tutorial but I'm unable to downgrade to 4.5.3
I get a signature verification error when sending the file; the exact error from the recovery logs is:
Code:
I: failed to verify against RSA key 0
E: failed to verify whole-file signature
The installed OS version is 5.0.1 on a Fire 5th generation.
Does anyone have a solution for this problem?

Get the same error :
E:failed to verify whole-file signature
E: signature verification failed
Installation aborted
Can smone help pls?

I followed this guide to root my fire, it worked.
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152

wasted whole day, try 3 times already, doesn't work on Fire HD6, Followed all the steps, upgraded from 4.5.5 to 5.0.1 Preview, then downgraded to 4.5.3, install KingRoot to get su, install TWRP, copy all zip packages, flash them, reboot via TWRP to install superSU and after 10 minutes it shows kindle fire OS 5.0.1, and to perform step 35, no SU access any more, can't complete step 35, such a wastage of hours and hours

george9584 said:
wasted whole day, try 3 times already, doesn't work on Fire HD6, Followed all the steps, upgraded from 4.5.5 to 5.0.1 Preview, then downgraded to 4.5.3, install KingRoot to get su, install TWRP, copy all zip packages, flash them, reboot via TWRP to install superSU and after 10 minutes it shows kindle fire OS 5.0.1, and to perform step 35, no SU access any more, can't complete step 35, such a wastage of hours and hours
Click to expand...
Click to collapse
Man I am glad I read this post... I have a Gen 4 HD6 that came with 4.5.5, and I would LOVE to get root and GAPPS and make this thing work the way it should, but these tutorials are confusing as hell...
Do we use ADB+Fastboot or do we have to install ADB from the SDK? There is NO mention of this in the video tutorials... I am confused.
Not everyone uses Linux. I am on a Windows box here at work and would love to make this happen... Can anyone shed light?

Hello,
@Team Scream, I suggest you look at Imma Wake's video "Downgrade and root Fire HD6/HD7". This one is giving you all you need to move from 4.5.5 to 5.0.1 and get root rights. It's shorter(18 steps) and rather self-explanatory. As an example, I did it today without any hiccups.
I used ADB+Fastboot (the one he made a video about), but didn't had to use any fastboot command. So don't get confused, it's just a rather simple way to get ADB up and running.
If it may be of any help, just know that I had to re setup the driver in the device manager will the tab was in sideload mode.
@powerpoint45 not forgetting ppl who made this tutorial possible, I deeply thank you for the tremendous work you've done! I will give it a shot soon hopping it goes as smoothly as the guide i mention before.
All the best,
EDIT
It all went smooth and easy.
So here is my backlog:
"Fire HD6" on "Fire OS 4.5.5"
Upgrade to 5.0.1 (dev version)
Downgrad to 4.5.3 and grant ROOT access via kingroot. (followed the 18 step tutorial made prior to this one. check his youtube videos. additionnaly I did "adb shell pm block com.amazon.dcp" not mention in the 18, but 37steps tutorial just to be safe about OTA stuff)
Catch up on this tutorial at step12. Upgraded to 5.0 + ROOT + GAPPS + Play Store
@powerpoint45, You may want to swap step 35 and 36 because by the time you reach 35, you can't "su" in "adb shell". In fact, 36 is meant to allow "su" usages as far as i can tell
Due to the above "su" issue, I was scared that during the SuperSU setup(needing Wifi and prior to OTA disable) between step 34 and 36 is that some update happen eventually transforming a piece of cake into nightmare. Is it something to be worried about for ppl following your tutorial?
Lastly, the "System Updates" panel state "Fire OS 5.0.1", but isn't "5.2.2 firmware" + "5.2.0 stock recovery" suppose to increase the OS number to 5.2.X? (that's the rookie question I suppose)
Once again, thank you very much for this great video tutorial and all the best to you stepping into it.

user0x80 said:
Hello,
@Team Scream, I suggest you look at Imma Wake's video "Downgrade and root Fire HD6/HD7". This one is giving you all you need to move from 4.5.5 to 5.0.1 and get root rights. It's shorter(18 steps) and rather self-explanatory. As an example, I did it today without any hiccups.
I used ADB+Fastboot (the one he made a video about), but didn't had to use any fastboot command. So don't get confused, it's just a rather simple way to get ADB up and running.
If it may be of any help, just know that I had to re setup the driver in the device manager will the tab was in sideload mode.
@powerpoint45 not forgetting ppl who made this tutorial possible, I deeply thank you for the tremendous work you've done! I will give it a shot soon hopping it goes as smoothly as the guide i mention before.
All the best,
EDIT
It all went smooth and easy.
So here is my backlog:
"Fire HD6" on "Fire OS 4.5.5"
Upgrade to 5.0.1 (dev version)
Downgrad to 4.5.3 and grant ROOT access via kingroot. (followed the 18 step tutorial made prior to this one. check his youtube videos. additionnaly I did "adb shell pm block com.amazon.dcp" not mention in the 18, but 37steps tutorial just to be safe about OTA stuff)
Catch up on this tutorial at step12. Upgraded to 5.0 + ROOT + GAPPS + Play Store
@powerpoint45, You may want to swap step 35 and 36 because by the time you reach 35, you can't "su" in "adb shell". In fact, 36 is meant to allow "su" usages as far as i can tell
Due to the above "su" issue, I was scared that during the SuperSU setup(needing Wifi and prior to OTA disable) between step 34 and 36 is that some update happen eventually transforming a piece of cake into nightmare. Is it something to be worried about for ppl following your tutorial?
Lastly, the "System Updates" panel state "Fire OS 5.0.1", but isn't "5.2.2 firmware" + "5.2.0 stock recovery" suppose to increase the OS number to 5.2.X? (that's the rookie question I suppose)
Once again, thank you very much for this great video tutorial and all the best to you stepping into it.
Click to expand...
Click to collapse
Ok so first off thank you so much for taking the time to try and help, and forgive me for being needy.
In your post you mention following Imma Wake's video which I tried to do, but the very first step is a brick wall. The YouTube video which supposedly shows how to upgrade to the 5.0 Developer preview has been removed. It is no longer there, so that very crucial first step is one that I cannot take.
Next, in your post, you reference upgrading the Kindle HD6 using both the 5.0 Developer preview AND the 5.01 Developer preview which has me totally confused. I do not see any videos on Imma Wake you tube channel referencing the 5.01 Developer preview. The last thing I want to do is brick my brand new Kindle...
SO, once again, I am back here at square one, stuck. Any chance you can point me to the quick and easy method of upgrading to 5.0 Developer so I can get past that step? I have signed up on Amazon and the developer page indicates that my device will be upgraded within 48 hours, but I am sitting here with time on my hands today and really wanted to give this a shot today.
Thanks.

[VK810.4G] [altev] most reliable way to root and install a custom recovery

Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On the tablet, download the Stump app from http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Credit and thanks @jcase, IOMonster , @autoprime and @PlayfulGod. Credit and thanks azureflux for the music although personally I turn the volume down all the way.
2. Install the Stump app you downloaded. Android should prompt you that it's an app from an unknown source since you didn't download it from the Play Store. It should direct you to the Security Settings option "Unknown sources" which you should checkmark and then attempt again to install the Stump app.
3. Launch the Stump app.
4. Turn the volume all the way down if you want because the music can be annoying for the duration necessary to root the VK810.
5. Choose "Grind".
6. Choose "Brute Force".
7. On the VK810, it can take up to 20 minutes at which time the Stump app should say to reboot the device to implement the root.
8. Once the device is rebooted, go to the Play Store and install SuperSU from https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Alternatively you can download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053), extract the zip and install the SuperSU app, or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
You'll also need this SuperSU.zip for step 8 of the fourth post "Flash to the latest stock ROM so that you can have it with root".
Credit and much thanks to @Chainfire !!!
9. Launch SuperSU, confirm the prompt to update binaries.
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3

Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
1. On the tablet, download the "VK810_twrp_2.7.0.1.zip" from http://forum.xda-developers.com/showthread.php?t=2726707
Credit and thanks teamwin , @Drgravy , @djrbliss , @Dees_Troy , @id10terror and @traccdma !
The link is in the "DOWNLOAD" section below the "DISCLAIMER" towards the bottom of the first post.
Credit @Drgravy for the original instructions but I prefer to run the commands directly on the device instead of from a PC via USB Cable and ADB.
2. Download TWRP v2.8.7.0 from http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-7-0-t3150812
Credit and thanks @AndroidUser00110001 !
3. Install "X-plore File Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en
Credit and thanks Lonely Cat Games!
4. While you're in the Play Store, install "Terminal Emulator for Android" https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
5. Launch X-plore.
6. Enable root mode in X-plore:
6A. Click the three-dot menu button in X-plore's upper right corner.
6B. Choose "Configuration".
6C. In the "Root access" section, click the gray area below it and choose "Superuser + mount writable".
6D. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up. It might not open this prompt until a later step when you actually access root.​
7. Find the "VK810_twrp_2.7.0.1.zip" file you downloaded in step 1 above. It should be on your internal storage in the Download folder.
8. Click once on the zip file - this will show you the files contained in it.
9. Navigate to the other file manager pane by choosing "SWITCH PANE" in the upper right corner.
10. Choose "Internal storage".
11. Navigate to the original pane by choosing "SWITCH PANE" again.
12. Select all the files inside the zip.
13. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
14. Now navigate to root. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up.
15. From root, navigate to data/local/tmp.
16. "SWITCH PANE" to where you extracted the files from the zip.
17. Select "loki_flash" and "twrp.lok".
18. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
19. Launch "Terminal Emulator" installed in step 4 above.
20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/twrp.lok
reboot recovery
Instead of "reboot recovery" you can use an app such as "Quick Reboot" from the Play Store at https://play.google.com/store/apps/details?id=phongit.quickreboot to reboot to recovery.
21. For getting to custom recovery with the tablet off, press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock-looking recovery and you can let go of both buttons). "Factory Reset" will no longer perform a Factory Reset. That's what you choose to get into custom recovery.
22. Update to to the latest TWRP v2.8.7.0 that you downloaded in step 2 above by (in TWRP v2.7.0.1) choosing "Install", navigating to where you downloaded the TWRP v2.8.7.0 zip (probably in internal storage in the Download folder), and choosing to flash the zip.
You can put a different custom recovery on the same way.
23. You can reboot into the newer TWRP by choosing the reboot recovery option.
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4

Flash to the latest stock ROM so that you can have it with root:
1. Download my ROM from my signature at the bottom of this post. I use ADM "Advanced Download Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.dv.adm&hl=en, especially for downloading larger files like ROMs.
2. Check the MD5 Hash of the ROM zip:
2A. Copy (to the clipboard) the MD5 hash that I have in the filename of the ROM zip you downloaded in step 1 above.
2B. Install @scary alien 's "AFV File Verifier for Android" from the Play Store at https://play.google.com/store/apps/details?id=sa.afvx&hl=en.
2C. Run the AFV app.
2D. Choose "Input checksum for comparison".
2E. Paste the MD5 hash previously copied to the clipboard in step 2A above.
2F. Choose "Select File".
2G. Navigate to where you have the ROM zip.
2H. Long-press on the ROM zip and choose "Calc MD5 Checksum".
2I. When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.
If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.​
3. Optionally download one or more of my debloat zip files in the third post of my ROM thread in my signature below. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
4. If you didn't already do so in step 8 of the second post "Rooting VK810 official stock release 11A", download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053) or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
5. Copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections.
6. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
7. Flash my ROM.
8. Flash SuperSU.zip (downloaded in step 4 above). This step is VERY IMPORTANT if you want to get back into custom recovery without having to re-flash a stock ROM and go through the whole process again.
9. Optionally flash one or more of my debloat zip files. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
Flashing the debloat zip(s) before the first boot of the ROM will give the advantage of never having the data/cache entries or internal storage folders for the debloated apps created, the latter is why I recommend a wipe of internal storage.
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5

Thanks to @JBurch/cry for the monetary motivation to finally put this all together in one place!
There are THREE variants of the G Pad 8.3: The Verizon VK810.4G which has LTE, and the V500 and V510 WIFI-only models. These instructions are ONLY for the VK810.4G.
Please don't quote the whole OP.
FAQ: If you use files meant for anything else other than the VK810, you'll brick your tablet. This will be exhibited by the tablet showing up in Windows' Device Manager under "Other devices" as "QHSUSB-BULK". You will have to Google for "QHSUSB-BULK" to find out how to fix that. I've read about some having success doing so and others not. I haven't ever had to fix that so I have no personal experience with it and can only lead you to Google about it.
This requires a Windows PC, preferably Windows 7 or newer, to first downgrade your VK810 variant of the G Pad 8.3 to LG build 11A / Jellybean 4.4.2, to make it easiest to root and to put a custom recovery on.
Disclaimer: I am not responsible for whatever you do to your device. This is my preferred method and what I recommend.
Note: These instructions are still working in order to downgrade from official stock release 36B on the VK810 (codename "altev"), Verizon LG G Pad 8.3 LTE, to official stock release 11A in order to make it easiest to both root and install TWRP. You can then install any ROM you like including my newest stock ROM in my signature at the bottom of this post.
Downgrading/resetting to 100% official stock unrooted release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On a Windows PC, preferably with Windows 7 or higher, download the latest Verizon-LG driver at http://www.lg.com/us/support-mobile/lg-LGVK810 (current version 4.0.3, direct download link if still working http://18d5a.wpc.azureedge.net/8018D5A/tool/dn/downloader.dev?fileKey=UW00520120427).
2. Install the driver.
3. Reboot the PC.
4. While you're continuing to follow the rest of the directions, might as well get the installed driver "loaded":
4A. Put the VK810 in Download mode:
4A1. Preferably using the original USB cable, or alternatively possibly a high-quality cable, connect the one end preferably to a USB 2.0 port on your Windows PC. Note: not all, but most USB 3.0 ports (to avoid for this process under normal circumstances) are blue in color whereas USB 2.0 ports are usually black.
4A2. Turn the VK810 off (within Android, long press the power button and choose "Power off").
4A3. The following is different from other G Pad 8.3 variants:
4A3a. Press and hold the Up Volume button.
4A3b. While continuing to hold it, insert the tablet end of the USB cable.
4A3c. You should feel the tablet vibrate and you can see a very dim, very faint graphic in the very center of the screen that says "Download Mode":
{
"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"
}
Credit and thanks @sevoan for posting the screenshot at http://forum.xda-developers.com/showthread.php?t=2782066
4A3d. Let go of the Up Volume button.​
4B. Windows may take up to 10 minutes to finish loading the driver you previously installed. Every time you connect any USB device to a new/different USB port on a PC, Windows will have to take a longer loading the driver process.​
5. Download the official stock release 11A KDZ for the VK810: https://www.androidfilehost.com/?fid=23991606952610809 (file name "5. VK81011A_01 - Jellybean 4.2.2.KDZ - MD5 hash inside - recommended for both ease of rooting and one less step to install the initial TWRP v2.7.0.1.7z")
If the previous link doesn't work, you can find it in my signature at the bottom of this post.
6. Download and install the free 7-Zip Windows program from ttp://www.7-zip.org"]http://www.7-zip.org[/URL]. Any version should work although you can only install the 64-bit version on 64-bit versions of Windows.
7. Use 7-Zip to extract the KDZ from the 7-Zip (7z) file downloaded in step 5 above. If you want to extract the 7-Zip on an Android device instead for some reason, use ZArchiver from the Play Store at https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver&hl=en
8. LG Flash Tool 2014:
8A. On the Windows PC, download "LG Flash Tool 2014" from http://forum.xda-developers.com/showthread.php?t=2797190
Credit and thanks @quangnhut123
The MediaFire link is in step "3. Tutorial"
8B. Run "LGFlashTool2014.exe" as Admin: Right-click on "LGFlashTool2014.exe" and choose "Run as administrator". Provide Administrator credentials if necessary. If you get a UAC (User Account Control) prompt, click "Yes".
8C. If the program doesn't run, install the Visual C++ Runtime Library, also available in step "3. Tutorial" at the link in step 8 above, then repeat step 9.
8D. Screenshots also available at the link in step 8.
8E. "Select Type" should already be at the correct default "CDMA". Same for "PhoneMode" is "DIAG" and "Reset time" is "33000".
8F. Click the yellow folder icon to the right of the "Select KDZ file" field and choose the 11A KDZ file extracted from the 7-Zip archive you downloaded in step 5 above.
For reference: "CSE Flash" is what you should normally always use. "CSE Flash" will wipe your user data including your internal storage so be sure to move/copy anything you want to keep that's currently on your internal storage. "Normal Flash" is like a dirty flash. Your device will be restored completely to stock but will keep all of your user data including your internal storage. If you're downgrading stock ROM versions, you can expect "Normal" to result in a device that'll crash. If you do so, you can attempt a "Factory Reset" from the stock recovery (with the device off - long press the power button for 10 or so seconds until the device shuts off - press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock recovery and you can let go of both buttons). "Factory Reset" will of course wipe all user data including Internal Storage.
8G. Click "CSE Flash".
8H. On the "Read Phone Information" dialog which appears, do NOT press the "Read Phone Information" button. This has always crashed for me.
8I. Click "Start".
8J. On the next dialog, you can change the Country and Language if you like - either way doesn't make a difference. Click "OK".
VERY IMPORTANT: Once you click "OK", ignore any error dialogs that pop up. I mean every single one. Don't click any buttons in them, just drag them out of your way if necessary. 99.9% of the time, given enough time the device will be flashed successfully anyway. On the VK810, usually within 20 minutes. For comparison, on the VS985 Verizon LG G3, usually within 10 minutes.​
Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=2
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5
General thanks to, for my previous experience:
@AndroidFileHost for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
@KyPbP for letting us know it's availability and giving the link to download the VK810 35A_08 KDZ. http://forum.xda-developers.com/showpost.php?p=60851710&postcount=108
@Revoe for letting us know the availability of the VK810 36B_00 OTA. http://forum.xda-developers.com/lg-g-pad-83/general/verizon-lg-g-pad-8-3-vk810-altev-ota-t3182449
@hsbadr for giving me permission to kang his Verizon G3 VS985 JasmineROM 7.0 update script for this use. http://forum.xda-developers.com/showpost.php?p=56005236&postcount=1
@rant for giving a link to the official Verizon PDF detailing 35B. http://forum.xda-developers.com/showpost.php?p=60857092&postcount=1 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g-pad-83-5-20-15.pdf
@DeanGibson for giving a link to the official Verizon PDF detailing this release. http://forum.xda-developers.com/showpost.php?p=62413430&postcount=2 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-8-17-15.pdf
@Chainfire for SuperSU! http://forum.xda-developers.com/showthread.php?t=1538053
@Hnk1 for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading.
@xdabbeb for further knowledge about the partitions!

In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
1. Download the corresponding "aboot only" (aboot is the bootloader) found in the same place to download as my ROM zip. Corresponding means if you installed the latest 36B VK810 stock ROM, then download the 36B VK810 aboot zip file.
2. Download the 4.2.2 aboot package from http://forum.xda-developers.com/showpost.php?p=54533937&postcount=2
Credit and thanks @paperWastage !
The download link is about three quarters down in that second post.
3. Move this aboot.4.2.2.img file into the top of the internal storage (meaning, not in a folder).
4. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. You can now reboot into recovery via your preferred method.
6. Once you're finished in TWRP, you need to re-flash the newer aboot zip downloaded in step 1 above. If you forget, the ROM won't boot. You should be able to long-press the power button to force the device off, then use the manual method to get back into TWRP mentioned in step 22 in the previous section above. Re-flash the newer aboot zip, then reboot from TWRP and the ROM will boot.
You can alternatively dirty flash my ROM zip instead of just the aboot. You'd have to re-flash SuperSU.zip and any debloat zips too.

Reserved

Update
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!

JBurch/cry said:
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
Click to expand...
Click to collapse
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.

@JBurch/cry I wrote up directions for checking MD5 hashes on Android - they're in the section for flashing my ROM. I realized that this won't help you in your current situation unless you take the MicroSD card out and put it in another Android device and check the hash on there.
I'm debating whether I should write up directions for checking MD5 hashes on Windows too.

So uh ya
roirraW "edor" ehT said:
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
Click to expand...
Click to collapse
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.

JBurch/cry said:
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
Click to expand...
Click to collapse
Cool! Glad at least it was something simple, even if a little bit painful to fix. You must at least be a fast learner.
Maybe I'll separate that into two steps to distinguish them.
Enjoy! I hope we get 5.1.1 someday because 5.1.1 on the G3 is so much better than 5.0.x was. You're welcome and thank you! I never even took donations until a few months back when one or two people wanted me to.
Most of the time I enjoy just seeing someone successfully do whatever they're trying to do.

Thank you, I felt so much better using this than some sketch chinese program.

FL4NKENSTEIN said:
Thank you, I felt so much better using this than some sketch chinese program.
Click to expand...
Click to collapse
You're welcome! I know what you mean.

Hey. Not sure if I am posting in the correct thread so apologises if warranted.
I recently rooted my vk810 with king root. Seemed to be the only thing to work. Only after I rooted did I realize that king root probably was not the wisest way to go.
So I'm about to attempt to unroot and hopefully get this thing rooted and a decent rom working. I like the tablet but all the verizon crap and associated bloatware are driving me nuts.
A little background, I've used linux distros for a while now, but not comfortable with command line stuff. I'm that copy and paste guy...
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!

Soundsofsublime said:
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!
Click to expand...
Click to collapse
Just follow all of the directions in the first through fifth posts and they'll get you there. You'll need a Windows PC.
Some people have told about an app called "SuperSU Me" (not by @Chainfire) to replace Kingroot with SuperSU. I have no experience with that or links to it, however.
Thanks and you're welcome!

Lost on step 3.20
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.

Slingb1ade said:
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.
Click to expand...
Click to collapse
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?

How to unlock boot loader anyone suggest me

zaccheo said:
How to unlock boot loader anyone suggest me
Click to expand...
Click to collapse
No one has done it. Someone more knowledgeable than I would have to tackle it.

roirraW "edor" ehT said:
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
Click to expand...
Click to collapse
i didn't pay attention to the provided instructions "20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure)"
i was typing temp, needed to type tmp.