Develop Bugs

Kindle Fire + Mac Guide

If you're like me, you have a Kindle Fire, but you would prefer to use it with a Mac than with a Windows computer. I'm writing up a guide on how to do numerous things such as rooting the Fire, but with a Mac.
Rooting
If you want to modify your device, the first thing to do is to root it. You can then install many apps that require root privileges, as well as install TWRP and FireFireFire Bootloader.
I use the utility Breakdroid, and it is easier to use than KindleFireUtility, the Windows counterpart, because it does not require you to install any drivers, it just works. Here is the website. Go to downloads to download the Breakdroid tool for Kindle Fire.
http://northmendo.com/breakdroid/ Feel free to donate to the guy who made this.
1. Download Breakdroid and mount the DMG file.
2. Make a folder on your desktop or applications folder called 'Breakdroid' and copy over all the files.
3. Open the Breakdroid application. It will open a terminal window. Use option 5 'Kindle Fire Tools' and hit return.
4. An icon will bounce on your dock. It may bounce for up to a minute. It will then ask you if you want to open this application downloaded from the web. Click ok.
5. It will then show a dialog warning you that this voids your warranty. If you are attempting this, you should know this already.
6. Now it opens another terminal window.
{
"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"
}
7. Type '1' and press enter. Follow prompts. Make sure you follow any instructions exactly. Follow all the steps until step 8. You can use step 9 to donate to the guy who made this. It is optional.
8. Finally you can use step 10 to quit the Kindle Fire tools.
9. FireFireFire has been installed as bootloader and you have rooted your device.
Recovery
You can use TWRP which has been installed by the previous guide to install ROMS, backup the current system and recover from any problems.
1. To access the TWRP recovery, shut down your kindle by holding down the power button until it shows a shut down dialog. Tap shut down.
2. Now turn the Fire on again. It will show a blue 'Kindle Fire' logo. This is the new FireFireFire bootloader which has been installed.
3. Keep your eye on the power button light. It should be green. Wait for it to flicker slightly. Or you can wait 2 seconds. Then press the power button again. It will show boot options.
4. Use the power button to cycle between the boot modes. Choose recovery to boot into recovery, then leave your Fire to boot.
5. Team Win logo will show, then the curtain will rise, showing a grid of buttons.
6. You have booted into recovery! Reboot without choosing recovery mode to get back to the normal system.
Install a ROM
1. Hook up your Fire with your Mac with a Micro-B USB cable. You can get them cheap on eBay, but mine broke after a few weeks, so feel free to find a more reliable vendor.
2. Download a ROM for your Fire. I'd recommend the GedeROM if you want an Ice Cream Sandwich ROM, or MoDaCo if you want a modified stock ROM with Google Play Store preinstalled.
3. Copy over the .zip file, placing on the Fire which has mounted on your desktop. Also copy over the gapps .zip if provided if you want the Google Apps package.
4. Eject the Fire and disconnect it from the Mac.
5. Use the previous guide to boot into Recovery.
6. Tap the Backup button and backup your system. This is very important, especially when installing your first ROM.
7. BACKUP YOUR CURRENT SYSTEM! For good measure.
8. Now tap the home button at the top right of the screen. Now tap Wipe, then tap Factory Reset. Then wipe Cache, then wipe Davlik Cache. Finally System Wipe. (Thanks to Thepooch for the best way to do this bit!)
9. This will wipe the device, so make sure you've Backed up your Fire! (See steps 6 and 7).
10. Now go back to the home screen using the home button and tap the install button.
11. Choose the ROM .zip file which you placed on the sdcard. I hope you named it something easy to remember and identify.
12. Tap install.
13. If it fails, restore from the backup you made (see how important backing up before wiping is?) and make sure your ROM you downloaded was downloaded properly. Also make sure it's the original zip file, not expanded or recompressed. Then repeat. If all else fails, try a different ROM or just stay with stock.
14. If it was successful, then go back to the home screen, and if you downloaded a gapps zip file, flash this as well, in the same manner as the ROM zip.
15. Reboot into system using the reboot button on the home screen.
16. Successful? If you don't like your ROM, you can always revert to stock using your backup, or install a new ROM following these steps.
_________________________________________________________________________
If you found this guide helpful, please click the Thanks button. It means a lot.

great guide nice job really

Ok, I'll add that.
Yea, I'm just annoyed how little support there is for Macs so I wanted to show that it can be done

where can i get the link to the rom
I tried googling for the rom, and i downloaded the rom from MoDaCo, but when it finished downloaded, it's not written as .zip file.
I tried to place the entire folder in the sd card, but when go thru the TWRP recovery, of course, i couldnt find any .zip file.
Anybody can help?

This is a common problem. Open Safari, then press Command + (comma). This opens your preferences. Untick the option of automatically opening 'safe' files which is automatically unzipping your zip files. Now you can redownload the ROM and find the zip in your Downloads folder

some links to make this happen
Great info, will test much of it shortly. A few links that I found helpful and are ref'd above:
for the Google Apps package, Rootzwiki was helpful
http://wiki.rootzwiki.com/Google_Apps#Jelly_Bean_.28Android_4.1.x.29
and points to Jelly Bean universal apps:
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Kudos to twa_priv for a start to that trail.
Also twa_priv has useful info here (not mac specific, check the changelog for udpates)
http://forum.xda-developers.com/showthread.php?t=1778010&highlight=jelly+bean+gapps+fire
that also links to hashcode's kernel_omap (now over my skill set, but might be useful)
https://github.com/KFire-Android/kernel_omap/tree/p-android-omap-3.0
A couple of ROMs for Jelly Bean (I've not tested yet, but they're on my list):
Jandy Cane
http://forum.xda-developers.com/showthread.php?t=1766829&highlight=mac+kindle+fire
and since I can't find the post with the .sig file where I found AlienDroidV2.0 (which I'm told has hashcode's kernel in it), here's a bonus page that seems to have lots of good info:
http://forum.xda-developers.com/showthread.php?t=1859851&highlight=mac+kindle+fire
northmendo's breakdroid always worth mentioning, cuz you might need to start there:
http://northmendo.com/breakdroid/ (I found kindlewater mysterious but worked for me)
and the video to Root Kindle Fire Mac (6.3 & 6.3.1)
http://www.youtube.com/watch?v=5K_sw1quZlw
That ought to get you started. All links good as of today, 9/9 2012.

Most of that info is already on the original post :/

links were missing
jji7skyline said:
Most of that info is already on the original post :/
Click to expand...
Click to collapse
Info yes, but links to all things downloadable were missing (except breakdroid), which is why I spent time documenting it.

nice job I`m sure that your research will help others

[EDIT 2] I've noticed that I am having an issue with charging since I installed the rom. It will only recognize the charger when the Kindle is turned on, and it charges VERY slow. Anyone have any insight to this? [EDIT 2]
[EDIT] Nevermind! The play store was included! This TOTALLY reinvented the Fire for me. [EDIT]
Thanks so much for this! Working on it now.
One question.. The site that I downloaded gede from didn't come with the GApps zip. I went searching, but it looks like there are many different versions. Could you please inform me of where to get the right one?
Thank you again. Very, very much!

handamputation said:
[EDIT 2] I've noticed that I am having an issue with charging since I installed the rom. It will only recognize the charger when the Kindle is turned on, and it charges VERY slow. Anyone have any insight to this? [EDIT 2]
[EDIT] Nevermind! The play store was included! This TOTALLY reinvented the Fire for me. [EDIT]
Thanks so much for this! Working on it now.
One question.. The site that I downloaded gede from didn't come with the GApps zip. I went searching, but it looks like there are many different versions. Could you please inform me of where to get the right one?
Thank you again. Very, very much!
Click to expand...
Click to collapse
The latest version of jandycane ROM seems to fix a lot of charging glitches.

this is an incredible tool, thanks for sharing!!

device not found
hey guys... got my kindle today and I'm trying to root with the help of your guide. But after starting step one the the tool starts working but soon it wont find any device and stops. any ideas? Do I have to turn the kindle on or off?
btw: I've got the newer version of the kindle fire with 1gb RAM
[EDIT]
I just disabled and renalbed ADB and now it seems to find my device but now I'm getting this error "fail opening shift: No such file or directory" and after this its stuck "< waiting for device >".
Pleas anybody help me

janowhatever said:
hey guys... got my kindle today and I'm trying to root with the help of your guide. But after starting step one the the tool starts working but soon it wont find any device and stops. any ideas? Do I have to turn the kindle on or off?
btw: I've got the newer version of the kindle fire with 1gb RAM
[EDIT]
I just disabled and renalbed ADB and now it seems to find my device but now I'm getting this error "fail opening shift: No such file or directory" and after this its stuck "< waiting for device >".
Pleas anybody help me
Click to expand...
Click to collapse
This will NOT work on the new kindle, as although it looks similar, it is very different inside. You stand an extremely high chance of a permanent hard-brick for your kindle fire. DO NOT PROCEED.

Hello guys!
I've been trying to root my kindle fire... I follow all the steps 1 to 7. Step 8 from me return "Invalid option".
I have installed Root Explorer but when I try to move "vending" apk from /sdcard/Documents to /system/app I get the message: "Your phone doesn't appear to be rooted...."
I need to follow some additional steps?
My device version is 6.3.1
Regards!

Issue
Why is it that at step 1 i am stuck on "waiting for device" ?

eliasn said:
Hello guys!
I've been trying to root my kindle fire... I follow all the steps 1 to 7. Step 8 from me return "Invalid option".
I have installed Root Explorer but when I try to move "vending" apk from /sdcard/Documents to /system/app I get the message: "Your phone doesn't appear to be rooted...."
I need to follow some additional steps?
My device version is 6.3.1
Regards!
Click to expand...
Click to collapse
Maybe you should go through the steps again? It shouldn't say "Invalid option" at all. Make sure you power off and power on the kindle fire in all the necessary steps.
@behhtaran: Is your kindle fire connected directly to your Mac?

Help!
Hey everyone,
I need your help. I rooted my Kindle Fire HD (7.2.3) with http://forum.xda-developers.com/showthread.php?t=2074565. I now have 'SuperSU' and 'Root Check Basic' Applications on my Kindle Fire HD.
What I want is to have the 'Google Play Store' and the latest 'Jelly Bean' version. How can I do this? The other website shows me only the way with a PC but not with a Mac.
Thanks for all your responses!

Afaik you can't root the HD (correct me if I'm wrong but) you risk bricking your device.
Sent from my Amazon Kindle Fire using xda app-developers app

unfoldyourwings said:
Hey everyone,
I need your help. I rooted my Kindle Fire HD (7.2.3) with http://forum.xda-developers.com/showthread.php?t=2074565. I now have 'SuperSU' and 'Root Check Basic' Applications on my Kindle Fire HD.
What I want is to have the 'Google Play Store' and the latest 'Jelly Bean' version. How can I do this? The other website shows me only the way with a PC but not with a Mac.
Thanks for all your responses!
Click to expand...
Click to collapse
Use the search, Luke...
http://forum.xda-developers.com/showthread.php?t=2074565

[ROOT](11-17-12) Root Nexus 10 with CWM and SuperSu Zip (Stress Free and Simpler)

{
"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"
}
Updated 11-17-12: Now that we have a stable CWMR image thanks to damien667 this procedure should be a lot less risky and less stressful!
This is confirmed working but due to the procedure involved is risky! The standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your tablet by following this procedure!​
You must unlock the bootloader before performing this procedure!
Credits: Kidgoo for testing and coming up with the method, thanks to damien667 for the fixed CWM images, and Chainfire for the SuperSu zip and binaries!
Before you begin make sure you read and reread the procedure and fully understand the directions.
1. Download the CWM-SuperSU-v0.98.zip
2. Download damien667's fixed CWMR 6.0.1.6 touch version of from here
3. Connect the Nexus 10 to your computer
4. Flash the CWMR image you downloaded in step 2 using fastboot
Code:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
5. Touch "Install from SD Card" in CWMR
6. Select CWM-SuperSU-v0.98.zip that was downloaded in step 1
7. Let CWM-SuperSU-v0.98.zip install
8. Select "Reboot System"
9. Enjoy your rooted Nexus 10 !
To keep your custom recovery installed permanently and not get overwritten by the stock recovery when your reboot your tablet delete the following:
Code:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p

Reserved

works! thank you very much!

Awesome!
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!

WannaB101 said:
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!
Click to expand...
Click to collapse
One-Klick CWM Tounch + SuperSU would be great!!! :good::good::good:

So what am I supposed to do if ADB doesn't recognize the "sideload" command?

gravis86 said:
So what am I supposed to do if ADB doesn't recognize the "sideload" command?
Click to expand...
Click to collapse
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.

Perhaps a video?
Perhaps you could provide a video to help us along?

shimp208 said:
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.
Click to expand...
Click to collapse
Yep, my ADB was out of date... Thanks!

Got the latest version of ADB?

With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?

WannaB101 said:
Perhaps you could provide a video to help us along?
Click to expand...
Click to collapse
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!

shimp208 said:
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!
Click to expand...
Click to collapse
I hit ya with a question above...

joeski27 said:
With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?
Click to expand...
Click to collapse
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.

I know this is probably a noob question but the fastboot commands (the first two, for booting from CWRT) -- should they be done in Fastboot Mode or can they be done while Nexus 10 is on and at home screen with USB debugging enabled? If you need to be in Fastboot Mode, how do you get there with Nexus 10?
Thanks!

shimp208 said:
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.
Click to expand...
Click to collapse
Ok, the problem I have now is while I have the files on my tablet, I cannot move them to the root of the internal storage at this point...??? Suggestions??? Don't you have to be rooted in order to do this???

For some reason when I'm not in fastboot mode, I can use adb (adb devices lists my Nexus 10), but when I'm in fastboot mode, adb no longer recognizes the device. fastboot devices does however see it when in fastboot mode.
Anybody else have this problem or know why this might be happening? Thanks!

I'm still getting the sideload error after updating the ADB
Any insight, please?

So to others who are working on this and awaiting responses from the OP, where exactly have you placed the downloaded files on your tablet? specific locations?? and if so how did you get them there? I'm totally lost at this point, LOL, hoping to get some clarification soon...

Worked ... however .. you DO have to be in FASTBOOT already (power + Vol UP + Vol DOWN) - yeah it might be obvious when you're not tired as hell - but for those wondering
The first line should be:
fastboot boot /path/to/<recovery>.img
no fastboot reboot was needed - it rebooted itself.
I had a HELL of a time finding the sideload entry in CWM (that's just my brain deadness).
You have quite a bit of time More than enough.
THANK YOU!

TMobile GPad F 8.0 (V496) Info

For those that picked up a TMobile GPad F 8.0 recently, here's a good thread to ask questions until we either get a separate forum or get enough info to move over to the General.
Root
Kingroot works well following the instructions here: All you need for LG GPad 8.0 [LG v490] thread. Once rooted, replace it with SuperSu using this method.
It is best to use KingRoot 4.1 or earlier to root, replacing it as soon as possible. 4.5 is very difficult to uninstall, although you can purchase SuperSUMe on Google Play to attempt it.
OS
Stock OS is the only option at the moment. There is a system update available which fixes the stagefright bug. It can still be rooted.
Recovery
Thanks to @Rashed97 and @KAsp3rd a beta TWRP is available here. This is not a zip, so use Flashify, TWRP Manager or equivalent to flash zips. Hooking up a USB mouse also works well for in-recovery navigation.
Kernel
Similar to LG stock ROM on their phones, the kernel has some adjustable features accessible through Kernel Aduitor or Trickster.
Xposed
Xposed installs and runs well. G3TweakBox has the ability to adjust some extra settings.

ADB driver
I got one as part of the Father's Day promotion as I needed to upgrade my mobile internet hotspot. I would like to migrate from a Nexus 7 2013 and needed the ADB driver for restore using Helium. Has anyone come across a working ADB driver for this GPad?

I was able to root with Kingroot 4.1 and then replace Kinguser and su binaries to SuperSU using this method:
http://forum.xda-developers.com/showpost.php?p=60669196&postcount=1&nocache=1&z=4065499287098646
---------- Post added at 11:45 AM ---------- Previous post was at 11:39 AM ----------
These are the USB drivers I used . Got them from this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951

nicknc said:
Anyone else had performance issues without rooting?
Click to expand...
Click to collapse
There are performance issues without root as well.

FYI I just unlocked this tablet. Doesn't give 4G LTE on AT&T though, only HSPDA+
To Unlock this model, access the Hidden Menu:
1) From Home screen,Touch the “ Contact”
2) Touch the “ Search Contact
3) You can see the “Keyboard” after Touch the “ Search Contact”
4) Touch the “＋ “ icon after Dialer 2945#*496#
5) Touch Network Lock, you only have 3 attempts to enter the correct Unlock Code which you can get from any online vendors.
6) Press Unlock

Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:

Post 1000, hooray.
VRAM seems to be on by default and is eating up about 256K according to Kernel Aduitor. Disabling that helped performance some after I did a factory reset. The LTE radio is stronger than my G3, but that might just be a longer antenna.

the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now

sinshiva said:
the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now
Click to expand...
Click to collapse
Which KingRoot version did you use?

nicknc said:
Which KingRoot version did you use?
Click to expand...
Click to collapse
KingRoot-4.1.0.524.apk
[edit/]
I think they must have updated something on their end because now the same kingroot apk is working - root correctly persisting across reboots

You Are The Man {Works Like A Charm}
xoxo_xdagirl91 said:
Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:
Click to expand...
Click to collapse
{
"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"
}
I followed your instructions to the "T"! Your method for rooting with Kingsroot 4.1 English version, and replaced it with SuperSu
works like a charm! My suggestion to everybody, do everything in the internal storage area! Don't use your external SD Card using the above instructions! I'm making phone calls on this baby to via WiFi and LTE, sweet!

now just need to get roms
kinda makes me want to try and make my own.. I've never developed before. lol!

Which custom recovery we use?

Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
Nothing out there yet that I've seen. It'll come-- the v500 has had TWRP for about 9 months now. This one has only been out a couple of weeks.

Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.

Now that we have the root, has anyone tried to adjust the color of a panel? It is way too warm compared to my other devices (viewing my DSLR pics almost makes me think thr wirte balance was off).

northantara said:
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.
Click to expand...
Click to collapse
Well, I flashed it, and things went, err, poorly. I'm done trying. Turns out, it's not actually possible to recover from download mode with LGMobile Support Tool, at least until an update is made available online.

Thanks for trying. I assume the bootloader is locked on this too, meaning we will need to bump any flashable zips anyway.

The step to replace KingRoot with Supersu failed half way for me. Apparently there's a typo in the script >.< Now KingRoot thinks that the tablet is rooted even though it isn't... stuck with broken root...

That is not good news, if this baby has a locked boot loader I am taking it back. Left AT&T for locking the boot loaders of their devices.

Reverting back to Fire OS from CM11

Hello All!
I decided to install CM 11 a few days ago and then thought I'd like to go back to Fire OS. I followed the instructions as much as I could from the thread on here to revert back but I have ran into a problem. I could only get 4.6.1 installed but obviously, 4.6.3 is out and my phone can see it's there to download (and it does (try to) download - every time I restart my phone). When the download finishes the phone says there is an error and it can't update but then I can search for the update and so on. I have tried doing it the way Amazon suggest from my PC but to no avail.
I can only assume that this has something to do with the fact I went from 4.6.3 to CM 11 and then back to 4.6.1 and the phones still sees itself has partially being on 4.6.3?
Any help is much appreciated!
Thanks

doing it the way Amazon suggest from my PC but to no avail
Click to expand...
Click to collapse
That means you downloaded the 4.6.3 BIN image and tried sideloading it via ADB?
If not, take a look at this (scroll down to the paragraph "Recovery / Sideload Factory Images")
I think OTA update is useless at this point but using the Amazon stock recovery is very reliable, I used it many times in the beginning for testing purposes.
Just give us some details when you encounter problems, e.g. driver missing when connected to PC, etc. ... and don't forget your backup for important apps & app settings.

I tried doing this before and the CMD does not show as any devices being connected. I have it in debugging mode and plugged it in but Windows did not see it even though the phone shows as being connected. Also, just in case I tried using the command you send and it just says "* cannot read 'update.bin' *".

You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"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"
}
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":

It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one which also needed updating which I have just done and appears to now let the cmd see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now. I will post my results once the update has finished.
Also, thanks for the help with this. Your information did help and with a bit of tweaking, it appears to have worked.

Thanks for mentioning so early that you use Windows 10, that makes it so much easier for me. :laugh:
Nah, but it looks like you will be good from here on out...
Btw. by sideloading the image, it will erase "everything" on your device, so you get clean system without leftovers, just like you hoped for.

Can you add the link for the thread you used to revert back from CM11 to FireOS?

paulalva05 said:
Can you add the link for the thread you used to revert back from CM11 to FireOS?
Click to expand...
Click to collapse
The link is actually in the first reply but I have put it below anyway!
http://forum.xda-developers.com/showpost.php?p=61271723&postcount=2

Bingo Bronson said:
You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
Click to expand...
Click to collapse
Hi, thank you for the detailed instruction. My pc can recognize and show the name of my firephone, just like what you showed in the image. But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.

iHuyou said:
But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.
Click to expand...
Click to collapse
Validate the MD5 checksum, maybe your downloaded image is corrupted...

Is the update.bin file in a different directory?

Bingo Bronson said:
Validate the MD5 checksum maybe your downloaded image is corrupted...
Click to expand...
Click to collapse
Hi, Bingo Bronson, thank you for your reply. What I downloaded from the link in your original post is a WinRAR ZIP archive. When I open it, there are multiple file and folders in there. There is a file called boot.img, should I change its name to update.bin and sideload it? But it is only 8Mb. Can you give a little more detailed instruction? Thanks

iHuyou said:
[...] is a WinRAR ZIP archive. But it is only 8Mb. Can you give a little more detailed instruction? Thanks
Click to expand...
Click to collapse
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
edit: Slight misunderstanding, luckily iHuyou found the solution by himself. :victory:
This is the direct download link from Amazon for the latest GSM unlocked version: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
An here is the direct download link from Amazon for the latest AT&T version: http://fire-phone-updates.s3.amazon...HC5/update-kindle-32.4.6.5_user_465000520.bin
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:

Bingo Bronson said:
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:
Click to expand...
Click to collapse
Thanks again, Bingo Bronson. I figured it out. The bin file has to be in the same directory as the adb file, otherwise adb cannot find the bin file therefore cannot read it. I have successfully sideloaded 4.6.5 following your post. Thank you!

Blank Screen amazon fire phone
Hello Guys i need help with my amazon fire phone, I tried to revert back from cm11 to stock rom (http://www.android.gs/downgrade-amazon-fire-phone-to-stock-fire-os-3-5/) using this site's method i got error sideloading from stock recovery then i tried it from safe strap recovery and it went successful but before sideloading update.bin from safestrap recovey i wiped and i did not know what options i selected but now my fone wont boot only black screen and when i connect it to pc it shows 3,4 partitions and says format, format... what went wrong ?

[Help Thread]Kindle Fire 2] Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Kindle Fire 2 - 2012​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"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"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters@sd_shadow
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible of posting there, you may post here. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
Fire Index: Which Amazon (Kindle) Fire Do I have? There are several 7' Amazon Fires. Be sure you know which one you have
[Index] Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2
[REF]All Things About Kindle Fire 2
Frequently Asked Questions - 2nd Generation Kindle Fires
Please look for a similar [HELP THREAD] when visiting another device forum.
If you would like to create a similar [Help Thread] please Click Here.
​

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Kindle Fire 2[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: How do I know if i have a Kindle Fire 2?[/SIZE]Kindle Fire 2 has a 7" screen, No Camera, No Volume Buttons, Looks just like the Kindle Fire 1​[SIZE=+1]Q2: How do I tell the Kindle Fire 1 from 2?[/SIZE]kindle Fire 1's will have a system version that starts with 6 (6.3.3, 6.3.4...).​*​Forum Rules | New Users Guide | XDA Tour | Report Posts​A special thanks to everyone who contributed to the production of this FAQ​

Basic Info
Kindle Fire 2 - 2012
7" screen, No Camera, No Volume Buttons
Model # KFOT
Serial #D026
Codename: Otter2
[REF]All Things About Kindle Fire 2 Last edited by Zeuscluts; 2nd July 2014
Frequently Asked Questions - 2nd Generation Kindle Fires

Need help rooting Kindle Fire gen 2
(Another weekend.. another attempt!)
I have a Kindle Fire Gen 2
System Version: Current version 10.5.1
Serial number starts with D0026
OS: Windows 7
I have looked at this thread/post:
http://forum.xda-developers.com/showthread.php?t=2247493
And am trying to following this rooting tutorial:
http://forum.xda-developers.com/showthread.php?t=2075959
When I get to this step:
Step 1: Type this in the window, hitting enter after each line.
cd ..\..\Root
runme.bat
I get these results:
Code:
Device type:
0) New Z2 Root Method by cubeandcube (thanks man!)
1) 2014 root (thx jcase for nice pwn binary :) and xsacha for the exploit)
2) Xperia Root by cubeundcube
3) New Standard-Root (thx Ariel Berkman)
4) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
5) Old
6) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Exploit type:
0) xsacha Z2 Tablet Root
1) jcase Z1S Root (make sure to download the pwn binary first from XDA thread!)
Make a choice:
Please connect your device with enabled USB-Debugging ...
adb server is out of date. killing...
* daemon started successfully *
and then it does nothing.
after a while.. I tried to quit, and got this:
Code:
Terminate batch job (Y/N)? n
Copy needed files ...
error: device not found
error: device not found
error: device not found
error: device not found
..........................
I have performed the Windows 7 mod here:
http://forum.xda-developers.com/showthread.php?p=36373627#post36373627
I have also verified the ADB drivers as mentioned here:
http://forum.xda-developers.com/showthread.php?t=2069117
"Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface"."
^^ which I do show/have in my Device Manager
Can anyone help me getting my Kindle Fire Gen 2 rooted? Or suggest something I may have overlooked/not done correctly?
thanks.

xl97 said:
(Another weekend.. another attempt!)
I have a Kindle Fire Gen 2
System Version: Current version 10.5.1
Serial number starts with D0026
OS: Windows 7
I have looked at this thread/post:
http://forum.xda-developers.com/showthread.php?t=2247493
And am trying to following this rooting tutorial:
http://forum.xda-developers.com/showthread.php?t=2075959
When I get to this step:
Step 1: Type this in the window, hitting enter after each line.
cd ..\..\Root
runme.bat
I get these results:
and then it does nothing.
after a while.. I tried to quit, and got this:
I have performed the Windows 7 mod here:
http://forum.xda-developers.com/showthread.php?p=36373627#post36373627
I have also verified the ADB drivers as mentioned here:
http://forum.xda-developers.com/showthread.php?t=2069117
"Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface"."
^^ which I do show/have in my Device Manager
Can anyone help me getting my Kindle Fire Gen 2 rooted? Or suggest something I may have overlooked/not done correctly?
thanks.
Click to expand...
Click to collapse
reboot pc
try a different USB port

sd_shadow said:
reboot pc
try a different USB port
Click to expand...
Click to collapse
done as suggested (rebooted.. tried 2 different USB ports)
my results:
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry =
= (15.06.2014) v36 =
======================================================================
Device type:
0) New Z2 Root Method by cubeandcube (thanks man!)
1) 2014 root (thx jcase for nice pwn binary :) and xsacha for the exploit)
2) Xperia Root by cubeundcube
3) New Standard-Root (thx Ariel Berkman)
4) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
5) Old
6) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Exploit type:
0) xsacha Z2 Tablet Root
1) jcase Z1S Root (make sure to download the pwn binary first from XDA thread!)
Make a choice: 1
Please connect your device with enabled USB-Debugging ...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Kindle does nothing.. sits on home screen
funny thing now.. when I plug/un-plug the kindle from the USB port.. I am no longer getting the 'prompt' asking me what I want to do.. (open folder..etc)

xl97 said:
done as suggested (rebooted.. tried 2 different USB ports)
my results:
Kindle does nothing.. sits on home screen
funny thing now.. when I plug/un-plug the kindle from the USB port.. I am no longer getting the 'prompt' asking me what I want to do.. (open folder..etc)
Click to expand...
Click to collapse
try kingroot
KINGROOT Thread
Sent from my XT1060 using XDA Labs

xl97 said:
done as suggested (rebooted.. tried 2 different USB ports)
my results:
Kindle does nothing.. sits on home screen
funny thing now.. when I plug/un-plug the kindle from the USB port.. I am no longer getting the 'prompt' asking me what I want to do.. (open folder..etc)
Click to expand...
Click to collapse
Edit!:..
sd_shadow said:
try kingroot
Click to expand...
Click to collapse
Indeed it does! Thank You! Take~Care!
For one I have yet to find any root on XDA or elsewhere that is working on the KF2 System Version 10.5.1 Be sure that you have Enable ADB in Settings > Security set to on. Also be sure you have Allow installation of Applications / From unknown Sources in Settings > Device set to on.
After that please enter the folder Root_with_Restore_by_Bin4ry_v36\stuff and open a command prompt - I use elevated cmd prompt in my context menu so all I need to do is right mouse click on the folder where I wish cmd prompt to open and select > Open command window here as Administrator.. If you wish you can download the .reg file to give you this option with instructions if needed here...
Code:
http://www.sevenforums.com/tutorials/47415-open-command-window-here-administrator.html
Once cmd prompt is open in that folder please type....
adb devices
You should see a message something like
List of devices attached
D026A0A0328601E8 device
If not I would UNinstall any drivers you have installed > Reboot > INstall the drivers linked below > reboot and try the above steps again...
Code:
http://www.mediafire.com/download/cizq7o8mwwqh9ji/Kindle_Fire2_ADB_Drivers.zip
If still no listed devices after opening cmd prompt > adb devices then I would check your factory cable maybe try another.
My apologies if this is to be no help. Take~Care!

rb2tfm said:
Edit!:..
Indeed it does! Thank You! Take~Care!
For one I have yet to find any root on XDA or elsewhere that is working on the KF2 System Version 10.5.1 Be sure that you have Enable ADB in Settings > Security set to on. Also be sure you have Allow installation of Applications / From unknown Sources in Settings > Device set to on.
After that please enter the folder Root_with_Restore_by_Bin4ry_v36\stuff and open a command prompt - I use elevated cmd prompt in my context menu so all I need to do is right mouse click on the folder where I wish cmd prompt to open and select > Open command window here as Administrator.. If you wish you can download the .reg file to give you this option with instructions if needed here...
Code:
http://www.sevenforums.com/tutorials/47415-open-command-window-here-administrator.html
Once cmd prompt is open in that folder please type....
adb devices
You should see a message something like
List of devices attached
D026A0A0328601E8 device
If not I would UNinstall any drivers you have installed > Reboot > INstall the drivers linked below > reboot and try the above steps again...
Code:
http://www.mediafire.com/download/cizq7o8mwwqh9ji/Kindle_Fire2_ADB_Drivers.zip
If still no listed devices after opening cmd prompt > adb devices then I would check your factory cable maybe try another.
My apologies if this is to be no help. Take~Care!
Click to expand...
Click to collapse
update:
ok.. well things are looking up! lol
* I am now getting a prompt when I connect the KF to the PC.. (so I can open up folders/directories..etc)
* I also now get a number back in the device list (adb device command suggested above) as well.
I tried the ROOT and QEMU steps above again.. and the device is now being somewhat responsive (as in rebooting when the screen says it will..etc)
most lines that say::
UNABLE TO CHMOD....
FAILED TO COPY FILE...
QEMU always ends with 'ROOTING FAILED!' message..
but at least its a start in the right direction!
@sd_shadow -
If RootKing approach is still recommended.. I have a some questions from quickly reading the link/overview.
* this can -not- be installed after install? (am I reading that correctly?)
* do I use the desktop or .apk approach?
* If .apk...this is done by transferring the file to my KF.. where does it get transferred to? (and how to 'run it')
thanks.

xl97 said:
update:
@sd_shadow -
If RootKing approach is still recommended.. I have a some questions from quickly reading the link/overview.
* this can -not- be installed after install? (am I reading that correctly?)
* do I use the desktop or .apk approach?
* If .apk...this is done by transferring the file to my KF.. where does it get transferred to? (and how to 'run it')
thanks.
Click to expand...
Click to collapse
Cool on the looking up =) My apologies for butting in as obviously I'm not sd_shadow....
As I stated in my original post before the edit I have found nothing but kingroot that will work.
So honestly, before you root, unless you have a file manager / explorer already installed on your kindle, I would go to the amazon store on your kindle and download / install ES File Explorer. The one I was working on did not have one installed and it gave me issues due to not being able to locate and install the .apk's unless they were from the amazon store where it could auto-install after downloaded.
Code:
http://www.amazon.com/ES-Mobile-File-Explorer/dp/B008K6HN8I/ref=sr_1_1?s=mobile-apps&ie=UTF8&qid=1458374068&sr=1-1&keywords=es+file+explorer
No settings in ES File Explorer need to be messed with until after root and then I would change the settings to use the recycle bin, show hidden files, root explorer ( root explorer, when enabled will try to get root permission... Just allow it access when prompted ) and a few others, but the rest are simple and I am sure you can get it to your liking.
After ES File Explorer is installed then I would go to the bottom of the first post here...
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
and download the attached KingRoot4.1-release-20150703-for-xda.apk if you downloaded with the kindle then just use ES file explorer to locate the KingRoot4.1-release-20150703-for-xda.apk , select it and it will install. Once installed, run the kingroot app.. it 'may' say there is not root for the device but run it anyway because it will root it.
Remember... No one twisted your arm on rooting your device.... You chose to do so and No damage is done to the device by rooting it.
After root then back to what I said earlier...
I would change the settings to use the recycle bin, show hidden files, root explorer ( root explorer, when enabled will try to get root permission... Just allow it access when prompted ) and a few others, but the rest are simple and I am sure you can get it to your liking.
Click to expand...
Click to collapse
From there you should probably go through this thread awhile if you haven't
http://forum.xda-developers.com/showthread.php?t=2228539
Need anything else... Just let us know. Take~Care!

xl97 said:
Edit!:..
Indeed it does! Thank You! Take~Care!
For one I have yet to find any root on XDA or elsewhere that is working on the KF2 System Version 10.5.1 Be sure that you have Enable ADB in Settings > Security set to on. Also be sure you have Allow installation of Applications / From unknown Sources in Settings > Device set to on.
After that please enter the folder Root_with_Restore_by_Bin4ry_v36stuff and open a command prompt - I use elevated cmd prompt in my context menu so all I need to do is right mouse click on the folder where I wish cmd prompt to open and select > Open command window here as Administrator.. If you wish you can download the .reg file to give you this option with instructions if needed here...
Once cmd prompt is open in that folder please type....
adb devices
You should see a message something like
List of devices attached
D026A0A0328601E8 device
If not I would UNinstall any drivers you have installed > Reboot > INstall the drivers linked below > reboot and try the above steps again...
update:
ok.. well things are looking up! lol
* I am now getting a prompt when I connect the KF to the PC.. (so I can open up folders/directories..etc)
* I also now get a number back in the device list (adb device command suggested above) as well.
I tried the ROOT and QEMU steps above again.. and the device is now being somewhat responsive (as in rebooting when the screen says it will..etc)
most lines that say::
UNABLE TO CHMOD....
FAILED TO COPY FILE...
QEMU always ends with 'ROOTING FAILED!' message..
but at least its a start in the right direction!
@sd_shadow -
If RootKing approach is still recommended.. I have a some questions from quickly reading the link/overview.
* this can -not- be installed after install? (am I reading that correctly?)
* do I use the desktop or .apk approach?
* If .apk...this is done by transferring the file to my KF.. where does it get transferred to? (and how to 'run it')
thanks.
Click to expand...
Click to collapse
I don't always go back and look for edited posts
so if you add information/questions
please add a new post, even if it just says see edit
root king should work, and should be safe
I'm not sure what is meant by "cannot be installed after install" means?
yes, use desktop or apk
if using apk, allow unknown sources on Fire, download apk with Web browser on Fire, after downloading is complete click on download complete notification bar, there will be a install prompt
Sent from my XT1080 using XDA Labs

Hello
I stupidly bricked my kf2, I thought I could do it without a fastboot cable.
the guide I was following was https://wiki.cyanogenmod.org/w/Install_CM_for_otter2
Got to step 6 no problems, kindle rebooted I missed what happened but it said something about having to wipe/format system then rebooted. now it just shows kindle logo for 5 seconds and then reboots and then again
I have ordered a cable after destroying 6 trying to make a fastboot one but going to be waiting weeks from china.
Anyways not the first device I have bricked and likely not the last, my question is what procedure should I follow when I do get it as I dont want to do more damage.
Thank you in advance

@rb2tfm - thanks!
@sd_shadow - thanks as well!
so to re-cap:
I have a fresh system restored KF Gen 2
I downloaded, and installed ES File Explorer.
I downloaded, and installed KingRoot (.apk file)..
When download was complete I ran KingRoot file....
Ran through some screens, had button saying TRY ROOT AGAIN.. I clicked it.. and waited until numbers were done counting..etc..
I walked away and came back to me being at the 'home' page... of the KF..
(page says to go to Google play and download root checker.. but I cant because when I go there is says browser (SILK) not supported)
If I load KingRoot again.. it shows home page with a count -down- from 100% and always seems to stop @ 56%? (Security Index/Checking running state...)
ES File Explorer settings have been changed to allow Root Exploring, Recycle Bin and Show Hidden Files as well..
At this point I'm not really clear what my next step is?
Go to this thread and try to install google play?
http://forum.xda-developers.com/showthread.php?t=2228539
My end goal here is to install the latest version of Android that I can on this device.. (or at least the latest that runs the best!)
Which 'ROM' is suggested for this step (once I get there?)
thanks!

@rb2tfm -
 @sd_shadow -
After a reboot of the device...
and running KingRoot again..
I got the message Root successful, share with friends?
and the Security Index now shows 100% (with text of running state.... under it still)
I'm guessing I'm rooted now? lol..
but really un-clear what my next step is?
thanks!

Honor 7
Sent from my PLK-L01 using Tapatalk

dibbler.c said:
Honor 7
Sent from my PLK-L01 using Tapatalk
Click to expand...
Click to collapse
huh?
Is this a response to me?
What does that (Honor 7) mean?

xl97 said:
@rb2tfm -
@sd_shadow -
After a reboot of the device...
and running KingRoot again..
I got the message Root successful, share with friends?
and the Security Index now shows 100% (with text of running state.... under it still)
I'm guessing I'm rooted now? lol..
but really un-clear what my next step is?
thanks!
Click to expand...
Click to collapse
you need to install the 2nd bootloader from Hashcode
see his thread
Sent from my XT1060 using XDA Labs

xl97 said:
huh?
Is this a response to me?
What does that (Honor 7) mean?
Click to expand...
Click to collapse
just spamming
Sent from my XT1060 using XDA Labs

link to 2nd bootloader thread
http://forum.xda-developers.com/showthread.php?t=2100963
Sent from my XT1060 using XDA Labs

Bricked KF2 trying to install 2nd bootloader. It now turns on, shows the standard boot screen and immediately goes blank except for a white triangle in the middle with an exclamation point inside of it.
I can get it into fastboot mode with my factory cable, but I have no idea how to get it back to working condition.