Database Users

[VIDEOS] How to Root, recovery, roms, and much more

Here are some videos that I have put together on the Kindle fire HD 7in. Hope they help out the noobs on this device
How to Root your Kindle Fire HD
2nd Bootolader and TWRP custom recovery install
How to enter Fastboot Mode
KitKat CM11 rom install
How to push files with ADB to your KIndle FIre HD when stuck in Recovery
Kindle Fire First aide tool and restore
More to come soon

Not bad. Probably useful to many people.
Sent from my iPod touch using Tapatalk

r3pwn said:
Not bad. Probably useful to many people.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
thanks much more to come in the next couple weeks check out my other threads to see what I mean.

Hi there,
i'm new here.
I unboxed my new kindle fire hd today.
Is there any possibility to root a device with version 11.3.1.0 ???
thx
greatmanu

greatmanu said:
Hi there,
i'm new here.
I unboxed my new kindle fire hd today.
Is there any possibility to root a device with version 11.3.1.0 ???
thx
greatmanu
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2544736

Video added to the OP on custom recovery install.

Hi,
I have a rooted Kindle Fire HD 7 2012 with 7.2.2. In the video you flash kfhd7-freedom-boot-7.4.6.img which fits to the version of your installed Firmware.
Which files must I flash to avoid bricking my Kindle. And where can I get it if I have to use another img-file
Thanks
Frank

frankm123 said:
Hi,
I have a rooted Kindle Fire HD 7 2012 with 7.2.2. In the video you flash kfhd7-freedom-boot-7.4.6.img which fits to the version of your installed Firmware.
Which files must I flash to avoid bricking my Kindle. And where can I get it if I have to use another img-file
Thanks
Frank
Click to expand...
Click to collapse
here yu go this is all of hashcodes files on the tate / kindle fire HD
http://goo.im/devs/Hashcode/tate/

New Video added to OP should help some of you out.

Tomsgt said:
New Video added to OP should help some of you out.
Click to expand...
Click to collapse
I would like to install 7.4.6 (have 7.2.3) with fire flash (y have just intalled 2nd-bootloader + TWRP 2.6.3.1), but I cant
I download kfhd7-freedom-boot-7.4.6.img from Hashcode, run Fire Flash and then select in Boot Partition the Hashcode 7.4.6 img. Select Apply stack override and flash. The process run Ok, but I´m still in 7.2.3. Any idea of what iI´m doing wrong?
All this things I tried is because my Kindle shutoff itself without any appareant reason. I read related posts (http://forum.xda-developers.com/showthread.php?t=2380191; http://forum.xda-developers.com/showthread.php?t=2161719) but I cant fix the problem.
Thank you.

Elgari said:
I would like to install 7.4.6 (have 7.2.3) with fire flash (y have just intalled 2nd-bootloader + TWRP 2.6.3.1), but I cant
I download kfhd7-freedom-boot-7.4.6.img from Hashcode, run Fire Flash and then select in Boot Partition the Hashcode 7.4.6 img. Select Apply stack override and flash. The process run Ok, but I´m still in 7.2.3. Any idea of what iI´m doing wrong?
All this things I tried is because my Kindle shutoff itself without any appareant reason. I read related posts (http://forum.xda-developers.com/showthread.php?t=2380191; http://forum.xda-developers.com/showthread.php?t=2161719) but I cant fix the problem.
Thank you.
Click to expand...
Click to collapse
The freedom boot file is just a boot.img file not a system.img. A boot.img is the file that boots the system. So it will not change your system. If you want to update the device to 7.4.6 and have 2nd bootloader and twrp installed just search for a stock 7.4.6 rom and flash it in twrp
Sent from my SM-N900V using Tapatalk

Tomsgt said:
The freedom boot file is just a boot.img file not a system.img. A boot.img is the file that boots the system. So it will not change your system. If you want to update the device to 7.4.6 and have 2nd bootloader and twrp installed just search for a stock 7.4.6 rom and flash it in twrp
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Ok, thank you. I ve installed stock 7.4.1 rom from Hashcode (no find 7.4.6). Work good, but my problem of shutdown continue!
Thanks again

Elgari said:
Ok, thank you. I ve installed stock 7.4.1 rom from Hashcode (no find 7.4.6). Work good, but my problem of shutdown continue!
Thanks again
Click to expand...
Click to collapse
sounds like you have a bad battery or maybe something loose inside the device

Tomsgt said:
The freedom boot file is just a boot.img file not a system.img. A boot.img is the file that boots the system. So it will not change your system. If you want to update the device to 7.4.6 and have 2nd bootloader and twrp installed just search for a stock 7.4.6 rom and flash it in twrp
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
When using FireFlash you flash a freedom boot.img and TWRP. This can only be done from stock. After stock, you need a zip with the necessary files in it. This is something that gets buy newer folks.
That said, I have seen a lot of complaints about random un-fixable shutdowns all over. Even a system restore and letting Amazon push OTA updates is not fixing it. Probably some hardware or software issue. If it were me, I would see what Amazon would do for warranty.
Edit: Oops, I meant to quote Elgari. Sorry about that.

Thanks! It helped a lot !

Great videos.They help me understand what I have been reading about for a week make sense.

Not sure what to do?
OK, My kindle rooted fine, I got TWRP and 2nd bootloader to installed and did a backup, downloaded cm11 and gapps into my download folder,got into TWRP and did a wipe added zip files hit install, everything was going good and about 4 minutes into the install I got a message on the screen saying that said "system UI has stopped" then the screen went black. I waited a few minutes hit the power button and now I'm get a "cyanogenmod account has stopped"
Do I go back into TWRP and install my backup or try installing a different cm version ?

mrdave60 said:
OK, My kindle rooted fine, I got TWRP and 2nd bootloader to installed and did a backup, downloaded cm11 and gapps into my download folder,got into TWRP and did a wipe added zip files hit install, everything was going good and about 4 minutes into the install I got a message on the screen saying that said "system UI has stopped" then the screen went black. I waited a few minutes hit the power button and now I'm get a "cyanogenmod account has stopped"
Do I go back into TWRP and install my backup or try installing a different cm version ?
Click to expand...
Click to collapse
Either is file restore or download a different cm
Sent from my SM-N900V using Tapatalk

I think cm11 fully installed, I can adb to my kindle and get a device number and I can see all the files in the kindle on my laptop. I just don't have any user interface screen on my kindle.
Problem solved I held down the power button and the volume up and down buttons at the same time for about 15 seconds ,then release them and when it booted up every thing was fine. Running cm11

Tomsgt said:
KitKat CM11 rom install
Click to expand...
Click to collapse
Hello
I followed your video step by step and got CM 11.0 installed. But I can't get Google Now to work. After opening Google app, it asks me to get Google Now. If I say yes, it asks me to add a Google account. After doing that, if I open the app again, the search bar opens. No option for Google Now. Any help would be appreciated.

New Kindle FIre HDX7 with 3.2.6 rooted, safestrap it etc - how to get default back

Hi!
I recently bought a Kindle FIre HDX7. at first 3.1.0 was isntalled on it.. but while downloading and installing file explorer the kindle updater automatically downloaded the 3.2.6 update.... at first i thought great - now no root possible; but it still was possible
so then i rooted the device, installed SU, xposed and safestrap and flashed the Google Apps ROM.
I used this tutorial (but made a safestrap backup after xposed).
youtube com/watch?v=ZcD5mjZK0gU
How do i get back my Kindle Fire to the Stock Rom? or lets call it better this way: how can i make a complete reset of the device so that its in the same state like delivered. is a simple factory reset in the settings enough?
thx in advance.

sotizzle said:
Hi!
I recently bought a Kindle FIre HDX7. at first 3.1.0 was isntalled on it.. but while downloading and installing file explorer the kindle updater automatically downloaded the 3.2.6 update.... at first i thought great - now no root possible; but it still was possible
so then i rooted the device, installed SU, xposed and safestrap and flashed the Google Apps ROM.
I used this tutorial (but made a safestrap backup after xposed).
youtube com/watch?v=ZcD5mjZK0gU
How do i get back my Kindle Fire to the Stock Rom? or lets call it better this way: how can i make a complete reset of the device so that its in the same state like delivered. is a simple factory reset in the settings enough?
thx in advance.
Click to expand...
Click to collapse
open safestrap -> uninstall recovery -> reboot -> factory reset

but isnt my backup of the system combined with a root? because i made the backup after the root....
so thats all i need to do?
how about this description i just found:
youtube com/watch?v=HYwn9xWpDNw
I dont need any swiping, clean stock ROM etc?!

sotizzle said:
but isnt my backup of the system combined with a root? because i made the backup after the root....
so thats all i need to do?
how about this description i just found:
youtube com/watch?v=HYwn9xWpDNw
I dont need any swiping, clean stock ROM etc?!
Click to expand...
Click to collapse
if you found that tutorial use it

152
because the tutorial has not the same situation as my device.
what would be the correct sequence to restore the stock rom and make a factory reset without root and all the installed apps etc - and will i get 3.1.0 back?

taette said:
open safestrap -> uninstall recovery -> reboot -> factory reset
Click to expand...
Click to collapse
Do i just have to uninstall the recovery? or also the safestrap app itself?
and how about the costum rom? do i have to uninstall it somehow or delete it?

sotizzle said:
Do i just have to uninstall the recovery? or also the safestrap app itself?
and how about the costum rom? do i have to uninstall it somehow or delete it?
Click to expand...
Click to collapse
My girlfriend got her fresh kindle today. she wants to test the rooted/safestrapped/xposed amazon 13.3.2.4 but she doesn't like it. She hasn't flashed a custom rom to one of the TWRP rom slots. So i would say you have to delete the rom slots ( not the stock one) and double check in fireOS if your device space becomes the normal size. If this worked I would uninstall the recovery with the button in safestrap. And re-enable the OTA update with KFHDX-ToolKit.
Then restart your Kindle and then check for updates. Install them all and after you installed them. Make a factory reset. Then its the pure amazon fireOS with the newest version BUT BUT (!!!!) you can't use root / safestrap / google playstore anymore - keep that in mind.
Wish you the best

taette said:
My girlfriend got her fresh kindle today. she wants to test the rooted/safestrapped/xposed amazon 13.3.2.4 but she doesn't like it. She hasn't flashed a custom rom to one of the TWRP rom slots. So i would say you have to delete the rom slots ( not the stock one) and double check in fireOS if your device space becomes the normal size. If this worked I would uninstall the recovery with the button in safestrap. And re-enable the OTA update with KFHDX-ToolKit.
Then restart your Kindle and then check for updates. Install them all and after you installed them. Make a factory reset. Then its the pure amazon fireOS with the newest version BUT BUT (!!!!) you can't use root / safestrap / google playstore anymore - keep that in mind.
Wish you the best
Click to expand...
Click to collapse
I also didnt use a costum ROM slot - but i have a backup from my system. or i can also download the stock rom or? but how do i install the backup? just hit install in the safestrap option (boot up) and install it on the stock rom slot? and then uninstall the recovery?
or do i just have to hit factory reset when i didnt use a costum rom slot? but re-enable OTA and install update is not an option...

Okay if i get it right now. You want a stock 13.3.2.4 fireOS without root and so on? And you are currently on 13.3.2.6 with all stuff. Right?

correct - because apparently im not able to use the HDX Nexus ROM with 3.2.5 or 3.2.6 (even though there are several youtube vids that show it works perfectly with 3.2.5?!)
but the main reason is that i want the stock ROM slot clean with the stock fire OS and use a costum ROM slot for the HDX Nexus Rom.
so basically a clean setup because now the gapps i flashed/installed on the stock ROM slot
i know i will have to reroot / install everything etc - but thats no problem. all i want is a factory reseted fresh kindle fire HDX with my current situation.

please help :/
in which order do i get the stock factory reset in the right order?
uninstall recovery
uninstall safestrap
factory reset? or do i need a stock .bin file which i have to install first?

sotizzle said:
please help :/
in which order do i get the stock factory reset in the right order?
uninstall recovery
uninstall safestrap
factory reset? or do i need a stock .bin file which i have to install first?
Click to expand...
Click to collapse
if you are on your stock rom slot start the system.
open SAFESTRAP APP
click the "uninstall recovery"-button
restart your tablet
SAFESTRAP should now gone
if you want a specific version use the rollback tutorial
then your tablet should be stock in your preferred version (without ROOT and so on)

[VK810][ROOT][Lollipop][5.02] No downgrade required

Hello everyone. I have successfully rooted Lollipop 5.0.2 for VERIZON LG PAD 8.3 VK810 without downgrading.
PREREQUISITES
-Updated drivers installed
-turned on usb debugging
- Supersu installed from playstore
STEPS
More specifically HERE
Now the English version stands at 2.2.1 while Chinese is still at 1.85
2.Run iRoot app from PC. Wait till it is complete. You will have root with some system cleaner app with King user.
IF ABOVE FAILS
1.Install KingoRoot as well
http://www.kingoapp.com/
2.After running iRoot, run KingoRoot. Wait about 5-8 minutes as it would go on forever. Close it afterwards.
3. Run Iroot and Kingoroot together. Wait till it is restarted and you acquire root with KingUser
3. Download supersu from here and install its apk. Upgrade binaries and uninstall kinguser.SUPERSU BETA 2.49
The apk file is located in the zip
If binary upgrade fails, try2.48 version. Link given below.
You should be rooted with Supersu.
If it fails to upgrade binaries.
.Flash aboot 4.2.2 to flash twrp 2.7.0.1. Instructions given Here on my guide
.Update Twrp to 2.7.1.0. FROM HERE
.Reboot into recovery via twrp menu
. Flashed SuperSu 2.48beta via twrp.
https://download.chainfire.eu/735/SuperSU
. Flash aboot 5.0.2 via twrp from HERE
Clear cache and wipe dalvik via recovery (twrp)
Reboot.
Done!
CHECK HERE FOR OTHER INSTRUCTIONS AND PROOF
UPDATE
LATELY I HAVE SUCCESS WITH KINGROOT APK for rooting devices.
Download apk from here and report back
http://www.kingroot.net/
XDA LINK TO KING ROOT
@imilleson
KingoRoot 4.62 worked on my Verizon LG GPad 8.3 (vk810) with sim card running Android 5.02 - at first it said failed but proceed after that point and it succeeds.
Click to expand...
Click to collapse

Credits
@roirraW "edor" ehT for his aboot 5.0.2 and innumerous suggestions
@rant for giving a link to the official Verizon PDF detailing this release.
@Chainfire for SuperSu! [MENTION=2282431]
twrp team
@Drgravy for bringing tarp to this device
@KyPbP for providing the kdz file in a jiffy.
@DeanGibson for his valuable feedback and testing my guide @imilleson for confirmation that kingroot works on lollipop!
Anyone else I forgot?

FAQs
1.I flashed 2.48beta via twrp. Did not try version 2.48 or 2.49 apk to update supersu binaries.
2. Supersu 2.46 from play store failed. Even flashing 2.46 failed via twrp

Hnk1 said:
Credits
@roirraW "edor" ehT for his aboot 5.0.2 and innumerous suggestions
@rant for giving a link to the official Verizon PDF detailing this release.
@Chainfire for SuperSu! [MENTION=2282431]
twrp team
@Drgravy for bringing tarp to this device
Anyone else I forgot?
Click to expand...
Click to collapse
Maybe the guy who made us aware the KDZ was available. Without that I couldn't have gotten the ROM out so quickly.

RE: Step 12 - Does TWRP survive the updated aboot flash?

w0rdie said:
RE: Step 12 - Does TWRP survive the updated aboot flash?
Click to expand...
Click to collapse
No it doesnot survive it as TWRP is not compatible with aboot 5.0.2. I am sure developers are looking into it

roirraW "edor" ehT said:
Maybe the guy who made us aware the KDZ was available. Without that I couldn't have gotten the ROM out so quickly.
Click to expand...
Click to collapse
Added him as well to credits post

Even simpler!
Hnk1 said:
Hello everyone. I have successfully rooted Lollipop 5.0.2 for VERIZON LG PAD 8.3 VK810 without downgrading.
PREREQUISITES
-Updated drivers installed
-turned on usb debugging
STEPS
1.Install iRoot (also called Vroot) (in chinese). The Chinese version is on 1.83 while the english translated is still on 1.78. Use the Chinese one.
http://www.mgyun.com/
2. [Install KingoRoot -- not needed]
3.Run iRoot app from PC. Wait till it is complete. You will have partial root but some system cleaner app with King user. Do not do anything
4. [Run KingoRoot -- not needed]
5. Run Iroot and Kingoroot together. Wait till it is restarted and you acquire root with KingUser.
...
Click to expand...
Click to collapse
The above is all I needed to do, to root my two VK810 tablets. I had SuperSU already installed on both tablets, but it didn't want to successfully update its binary ("su"), so I uninstalled SuperSU and kept "KingUser", the equivalent tool that comes with iRoot.

w0rdie said:
RE: Step 12 - Does TWRP survive the updated aboot flash?
Click to expand...
Click to collapse
Just to be clear, TWRP itself is still there when you have the 35A_08 aboot flashed, the new bootloader just won't let you boot into recovery. To get back into it temporarily you just have to flash the 4.2.2 aboot, then when you're done in TWRP and want to boot the ROM again, you can flash the 35A_08 aboot that I provide in zip flashable format in my ROM thread in Development. I also provide a mirror of the 4.2.2 aboot and instructions for everything.
If you forget to re-flash the 35A_08 aboot before leaving TWRP, the only symptom is the ROM won't boot. Just use the hardware keys (volume down and power buttons held in) long enough (about 10 seconds) to manually boot back into recovery (choose Factory Reset from the regular recovery menu, which takes you into TWRP).
Hnk1 said:
No it doesnot survive it as TWRP is not compatible with aboot 5.0.2. I am sure developers are looking into it
Click to expand...
Click to collapse

DeanGibson said:
The above is all I needed to do, to root my two VK810 tablets. I had SuperSU already installed on both tablets, but it didn't want to successfully update its binary ("su"), so I uninstalled SuperSU and kept "KingUser", the equivalent tool that comes with iRoot.
Click to expand...
Click to collapse
Well, the only concern I had on my mind was if King User is safe enough and could be trusted with privacy. That's the reason I had to do all the effort to bring back Supersu. ELSE, King User was doing everything too, it's just I don't trust it that much. I'll update the guide , thanks for your feedback. If you wish to try, uninstall supersu from Google play, install supersu from links I provided (not available in market yet)using apk and then try upgrading your binaries. See what happens.
@roirraW "edor" ehT
Many thanks for clarification.

Hnk1 said:
Well, the only concern I had on my mind was if King User is safe enough and could be trusted with privacy. That's the reason I had to do all the effort to bring back Supersu. ELSE, King User was doing everything too, it's just I don't trust it that much. I'll update the guide , thanks for your feedback. If you wish to try, uninstall supersu from Google play, install supersu from links I provided (not available in market yet)using apk and then try upgrading your binaries. See what happens.
@roirraW "edor" ehT
Many thanks for clarification.
Click to expand...
Click to collapse
You're welcome!
Re: SuperUser, I agree with you. Hesitant to trust anything but SuperSU until I do more research.

roirraW "edor" ehT said:
Just to be clear, TWRP itself is still there when you have the 35A_08 aboot flashed, the new bootloader just won't let you boot into recovery. To get back into it temporarily you just have to flash the 4.2.2 aboot, then when you're done in TWRP and want to boot the ROM again, you can flash the 35A_08 aboot that I provide in zip flashable format in my ROM thread in Development. I also provide a mirror of the 4.2.2 aboot and instructions for everything.
If you forget to re-flash the 35A_08 aboot before leaving TWRP, the only symptom is the ROM won't boot. Just use the hardware keys (volume down and power buttons held in) long enough (about 10 seconds) to manually boot back into recovery (choose Factory Reset from the regular recovery menu, which takes you into TWRP).
Click to expand...
Click to collapse
I appreciate the clarity. :good:

I agree with the sentiment
roirraW "edor" ehT said:
...
Re: SuperUser, I agree with you. Hesitant to trust anything but SuperSU until I do more research.
Click to expand...
Click to collapse
I agree with the sentiment. I did uninstall SuperSU 2.46 and then sideload SuperSU 2.49, and it still had problems updating its binary. SuperSU even detected that there was another "root management" (my term) app installed, and offered to uninstall it. I let it try, and that failed as well. So, I will wait for a report of a successful conversion to SuperSU.
I did originally try Kingo Root (per the OP's instructions) on the 1st tablet, and that got me another "root management" app installed, so now I had three (before I uninstalled SuperSU)! It also installed something on the 1st tablet that Google warned me was a security risk, so after the 2nd tablet rooted with just iRoot, I did a factory reset on the 1st tablet and just used iRoot.
Both iRoot and its "root management" app KingUser seem well-written, surprising (at least to me) from a region not known for well-written, easy to use software.
---------- Post added at 09:42 AM ---------- Previous post was at 09:25 AM ----------
Hnk1 said:
Well, the only concern I had on my mind was if King User is safe enough and could be trusted with privacy. That's the reason I had to do all the effort to bring back Supersu. ELSE, King User was doing everything too, it's just I don't trust it that much....
Click to expand...
Click to collapse
Unfortunately, once you install anything with root privileges, who knows what it left behind. KingoRoot in particular left around several apps with no app icon, that KingUser listed and I was able to uninstall. However, that left me with an uneasy feeling, which is why I did a factory reset on the 1st tablet and started over.
I'd rather trust what one Chinese/Korean app left around (which I have to, if I use iRoot), rather than two.
iRoot does install two other apps, one is the "Cleaner", and another is part of the download process, but I very promptly uninstalled them.

w0rdie said:
I appreciate the clarity. :good:
Click to expand...
Click to collapse
You're welcome!
DeanGibson said:
I did originally try Kingo Root (per the OP's instructions) on the 1st tablet, and that got me another "root management" app installed, so now I had three (before I uninstalled SuperSU)! It also installed something on the 1st tablet that Google warned me was a security risk, so after the 2nd tablet rooted with just iRoot, I did a factory reset on the 1st tablet and just used iRoot.
Both iRoot and its "root management" app KingUser seem well-written, surprising (at least to me) from a region not known for well-written, easy to use software.
Unfortunately, once you install anything with root privileges, who knows what it left behind. KingoRoot in particular left around several apps with no app icon, that KingUser listed and I was able to uninstall. However, that left me with an uneasy feeling, which is why I did a factory reset on the 1st tablet and started over.
I'd rather trust what one Chinese/Korean app left around (which I have to, if I use iRoot), rather than two.
iRoot does install two other apps, one is the "Cleaner", and another is part of the download process, but I very promptly uninstalled them.
Click to expand...
Click to collapse
I thought the same thing, once something has root it could already have done whatever hidden "damage" it wanted to. I had the same experience regarding what iRoot left behind, the one time early during @Hnk1 's experimenting that I tried it.

Hnk1 said:
STEPS
1.Install iRoot (also called Vroot) (in chinese). The Chinese version is on 1.83 while the english translated is still on 1.78. Use the Chinese one.
http://www.mgyun.com/
2.Run iRoot app from PC. Wait till it is complete. You will have root with some system cleaner app with King user.
Click to expand...
Click to collapse
Well I sort of achieved root with this method.
The vroot program said I had root and root checker did too.
However adaway and titanium backup could not perform their functions. They are allowed in the king user app and tibu even said it had root access.
Anyone else run into this issue?

_Boondock_ said:
Well I sort of achieved root with this method.
The vroot program said I had root and root checker did too.
However adaway and titanium backup could not perform their functions. They are allowed in the king user app and tibu even said it had root access.
Anyone else run into this issue?
Click to expand...
Click to collapse
I was also partially rooted with the above method and thus I performed IF ABOVE FAILS in my guide, that is using another app and then running both apps simultaneously. However, another user said, he only needed to use IROOT so I edited it a bit.
Try restarting your device, and then try IF ABOVE FAILS.
See if that helps ?

@Hnk1 I really appreciate all your work but I have tried this method 100 ways and can not get it to work. Iroot says yea but root check says na and Kingo root never takes. If you have any ideas I will try again. Does it matter if I am on the ota or kdz?

mopartonyg said:
@Hnk1 I really appreciate all your work but I have tried this method 100 ways and can not get it to work. Iroot says yea but root check says na and Kingo root never takes. If you have any ideas I will try again. Does it matter if I am on the ota or kdz?
Click to expand...
Click to collapse
Although it shouldn't matter, I would try with a fresh CSE mode flash of the 35A KDZ.

roirraW "edor" ehT said:
Although it shouldn't matter, I would try with a fresh CSE mode flash of the 35A KDZ.
Click to expand...
Click to collapse
Yep tried that also, I will keep playing til I get it

mopartonyg said:
Yep tried that also, I will keep playing til I get it
Click to expand...
Click to collapse
It's tedious work, but satisfying once we figure it out. I had to reflash so many times in order to find out what two things I was debloating was causing the initial setup to FC. Google Webview and Google TTS.
Good luck!

How to Root Fire TV 2 & 1 in 3 min

Fire TV 2 or 1 running Fire OS 5 can be Rooted with KingRoot very fast. Jute follow the Setp by Step Tutorial
This method was tested on Fire Tv 2 Gen but it should work with any Fire Tv device as long as it Running Fire OS 5.
Video How to Root Fire TV 2 or 1, Enjoy
https://www.youtube.com/watch?v=jDSishmkhgo
Download KingRoot 4.1 from here:
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
---
Video How to install TWRP Custom Recovery For Fire TV 2 Only:
https://youtu.be/gENmnUvb_Po
Download :
TWRP Custom Recovery v5
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780
SManager v2
http://smanager.wikidot.com/
---
Note & Disclaimers:
- KingRoot will not play well with SuperSU where it may brick your device if you try to remove KingRoot files after root.
- Best way to make sure you do it right is to setup a Custom Recovery after root and install a Custom Rom.
- Custom Recovery is only available for Fire TV 2 for now, for FireTV 1 If you want to root using kingRoot, Please block updates and wait for recovery to be released.
- 2ed video tutorial was add here to show how to install a Custom Recovery.
- 3ed video tutorial will be add here to show how to install a custom Rom very soon.
---

Careful people! Don't try to get rid of kingroot afterwards with supersume, or you will brick your device!
And in case of the fire tv1 bricked means bricked!
For firetv2 better use other means of rooting by installing the recovery!

santamanga said:
Careful people! Don't try to get rid of kingroot afterwards with supersume, or you will brick your device!
And in case of the fire tv1 bricked means bricked!
For firetv2 better use other means of rooting by installing the recovery!
Click to expand...
Click to collapse
For FireTv 2 you can use kingroot, install recovery and then flash a pre-rooted rom ----this will get rid of kingroot however I agree do not try to remove kingroot with superSUme if you do not want a doorstopper.

Agreed. Please make sure to put some disclaimers here that Kingroot is closed source, calls remote servers, and any attempts to clean it up via other applications can brick your device, especially without recovery or unbrick images (FireTV 1).
The best way to do this is to root offline (if that is even possible with Kingroot), install recovery, and install a clean system image.

jpeg42 said:
Agreed. Please make sure to put some disclaimers here that Kingroot is closed source, calls remote servers, and any attempts to clean it up via other applications can brick your device, especially without recovery or unbrick images (FireTV 1).
The best way to do this is to root offline (if that is even possible with Kingroot), install recovery, and install a clean system image.
Click to expand...
Click to collapse
I jute add it to the post thx for the handy comment :good:

inwisso said:
I jute add it to the post thx for the handy comment :good:
Click to expand...
Click to collapse
One more thing: this will only apply to FireTv2 for now, recovery is not available yet for FireTv1. If you want to root FireTv1 (OS5) use kingroot, block updates and wait for recovery to be released.

bula1ca said:
One more thing: this will only apply to FireTv2 for now, recovery is not available yet for FireTv1. If you want to root FireTv1 (OS5) use kingroot, block updates and wait for recovery to be released.
Click to expand...
Click to collapse
That true thx for the help... Great community.

[Q] SuHide by Chainfire, Anybody got working for Android Pay yet?

Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message

TheATHEiST said:
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
Click to expand...
Click to collapse
requirements :
- SuperSU installed in systemless mode
So does not work on our device

xander33 said:
requirements :
- SuperSU installed in systemless mode
So does not work on our device
Click to expand...
Click to collapse
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?

TheATHEiST said:
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
Click to expand...
Click to collapse
As i know the method for root our phone is system mode, the systemless zip not work
Here the procedure that i followed for rooting my phone and is system mode
What you need:
Unlocked bootloader (see chapter 2).
TWRP installed (see chapter 7).
1.Zip .
2.Zip .
How:
Put 1.zip and 2.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2.zip .
Install it.
Reboot

That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.

TheATHEiST said:
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
Click to expand...
Click to collapse
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app

Fedroid said:
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.

TheATHEiST said:
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
Click to expand...
Click to collapse
3 months since your last contact....
Things have changed a lot and android pay is working hard for avoid us pay with rooted phones.
Nowadays magisk is on v9 version and facing v10.
Want a clue?
If your mobile is compatible with multirom go this way. One rom rooted and modified as you want and another stock for doing payments.
Luck!