Develop Bugs

Tried everything, still unable to root KF 2, 10.2.6

I have tried every method of rooting my Kindle Fire that I've come across, I have my Android Composite ADB Interface installed correctly, I have all my java installed correctly, I have the Android SDK files installed correctly, I have both qemu and runme.bat folders installed correctly, everything seems right, yet I'm still not able to root my device. As of right now, my problem is with the last step, its with the Qemu root. Qemu will take me all the way to step 3 then give an error and stop, this error is attached.
I'm not sure what to do from this point on, but I assume that I am missing a critical file. If anyone could help me, it would be much appreciated.
This was the last method I tried: http://forum.xda-developers.com/showthread.php?t=2075959
Thank you.

Anyone? Anyone at all?

Honestly man it was a mega pain in the ass. I recommend doing bin4ry's root, then qemu's root, then SIDELOAD superuser. That last step made all the difference for me.

jimgreat said:
Honestly man it was a mega pain in the ass. I recommend doing bin4ry's root, then qemu's root, then SIDELOAD superuser. That last step made all the difference for me.
Click to expand...
Click to collapse
Already did that in one cmd, bin4ry worked fine so I progressed to the qemu root but I kept getting stuck at step 3. Not sure what to do now, and what do you mean by sideload superuser?

Using your computer, download the superuser apk, transfer it to your kindle's storage, find it via your file manager and install it.
Sent from my Amazon Kindle Fire2 using xda premium

haberdashery said:
Already did that in one cmd, bin4ry worked fine so I progressed to the qemu root but I kept getting stuck at step 3. Not sure what to do now, and what do you mean by sideload superuser?
Click to expand...
Click to collapse
I never ran the Qemu tool, as I was rooted after the first tool. Are you sure you are not rooted already?
Sent from my Amazon Kindle Fire2 using Tapatalk HD

chronicfathead said:
I never ran the Qemu tool, as I was rooted after the first tool. Are you sure you are not rooted already?
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
You see...this is something I don't quite understand. We know the Bin4ry root method works for all 2nd Generation Kindle Fires. I've tested it and had it tested several times before adding it to the SoupKit. It works, 99.999% of the time
Sooooooo...
If the Binary method works for all Kindle Fires (it does) then why are people still trying to Qemu root on top of the Bin4ry root? Something about that just doesn't make sense to me.

chronicfathead said:
I never ran the Qemu tool, as I was rooted after the first tool. Are you sure you are not rooted already?
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
I went into ES file manager and checked allow root explorer in the settings but it gave me a notification saying that my phone was not allowed to do this. I will try to just install superuser on my kindle now and see if that works.

haberdashery said:
I went into ES file manager and checked allow root explorer in the settings but it gave me a notification saying that my phone was not allowed to do this. I will try to just install superuser on my kindle now and see if that works.
Click to expand...
Click to collapse
jimgreat said:
Using your computer, download the superuser apk, transfer it to your kindle's storage, find it via your file manager and install it.
Sent from my Amazon Kindle Fire2 using xda premium
Click to expand...
Click to collapse
Just installed superuser on my kf2 but when I opened it up it gave me this error, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

soupmagnet said:
You see...this is something I don't quite understand. We know the Bin4ry root method works for all 2nd Generation Kindle Fires. I've tested it and had it tested several times before adding it to the SoupKit. It works, 99.999% of the time
Sooooooo...
If the Binary method works for all Kindle Fires (it does) then why are people still trying to Qemu root on top of the Bin4ry root? Something about that just doesn't make sense to me.
Click to expand...
Click to collapse
My thoughts exactly....
So as of now, I am reseting my kf2 back to factory default and just rooting it with Bin4ry, lets see how it goes.

help for you
haberdashery said:
I have tried every method of rooting my Kindle Fire that I've come across, I have my Android Composite ADB Interface installed correctly, I have all my java installed correctly, I have the Android SDK files installed correctly, I have both qemu and runme.bat folders installed correctly, everything seems right, yet I'm still not able to root my device. As of right now, my problem is with the last step, its with the Qemu root. Qemu will take me all the way to step 3 then give an error and stop, this error is attached.
I'm not sure what to do from this point on, but I assume that I am missing a critical file. If anyone could help me, it would be much appreciated.
This was the last method I tried: http://forum.xda-developers.com/showthread.php?t=2075959
Thank you.
Click to expand...
Click to collapse
I also "spent" hours trying to root, backup and install CM10 on my KF2 software version 10.2.3 and later updated to 10.2.6, before finally succeeding.
The information is in multiple threads on XDA.
After succeeding i was motivated in collecting and putting everything in one place ( i created a small blog on this specific subject):
someonelikesIT.wordpress.com
it has all the pointers towards every step described in XDA threads.
Hope it helps you achieve your goal.
It is not easy like next-next-next but not impossible (no IT background required but good understanding of english and some IT basic skills).
Good luck!

[Q] Problem Unrooting Kindle Fire HD 8.9"

I'd really appreciate some assistance on this one...
I'm attempting to unroot my Kindle HD 8.9, but it's resisting my efforts. I originally rooted using the Bin4ry method (r25), but lost it when Amazon forced 8.3.1 on me. The second time, I used Kindle Fire First Aide and then also used it to disable OTA. I've now tried unrooting it with all of these methods, yet I can still access root directories in ES FIle Explorer:
1) Unroot option in KF First Aide. Says it's successful, but it isn't.
2) Unroot option in Bin4ry. It says it fails and tells me to go into the SuperSU.apk itself and select the unroot option.
3) Unroot option in SuperSU.apk. It removes the SU app, but it doesn't unroot the device.
4) Re-enable the OTA and take the 8.4.6 build. Every time I've gotten an OTA upgrade, it has unrooted the device. This time it didn't. Now I'm running on 8.4.6 and still rooted. I reinstalled the SU app, and tried unrooting options 1-3 again, and again none of them worked.
I have done a factory reset after each one of these. None of them have made a difference.
I've also noticed that I still don't have my Amazon ads on the lockscreen. I disabled them using Kindle Fire First Aide and they didn't come back when the rest of my system apps got cleared.
Thank you in advance for any help you can provide!

You could tell kffa to do a system restore, and them from there I think if it doesn't auto-update, you can simply delete /system/app/superuser.apk and then /system/xbin/su, and possibly busy box, I think that was put on there in the rooting process, I suggest removing the su binary last as to avoid possibly getting the other files stuck on there and having to reroot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Thanks for your help, Stunts513!
It now appears unrooted and doesn't have superuser installed anymore, but ES File Explorer can see the root directory and change things in /system even though I have the "root" setting turned off.
I think I'm going to call it good. Everything is working fine and it looks standard to a normal user.

[Q] Kindle hd 8.9 stuck in slow mode after failed re root

My kindle hd 8.9 was re rooted using bin4ry v31 after the last ota update 8.4.8. It worked fine. Now there was another ota update to 8.4.9 on 6/14/14. I tried using the same method as before. ADB is enabled in my kindle, I am seeing Android Composite ADB interface. when I plug the kindle in. I got through part of the re root, where it rebooted, and now it is extremely slow, has a black screen with white cracked lines to slide in open, and although some things work they are very very slow. Please can someone either help me re root or unroot it so that the kindle runs normally. I don't know what mode that slow one is, but you can't do much of anything. I tried to roo a few times, and tried to put in the stock kindle update and re run it, but nothing is working to get it out of the slow mode. Right now my computer can see and put things onto the kindle, and when trying to root, it seems like it is trying to work, but since the kindle is slow, I don't know if it is getting stuck and not finishing.
Can you help me figure out what is wrong?

benee16 said:
My kindle hd 8.9 was re rooted using bin4ry v31 after the last ota update 8.4.8. It worked fine. Now there was another ota update to 8.4.9 on 6/14/14. I tried using the same method as before. ADB is enabled in my kindle, I am seeing Android Composite ADB interface. when I plug the kindle in. I got through part of the re root, where it rebooted, and now it is extremely slow, has a black screen with white cracked lines to slide in open, and although some things work they are very very slow. Please can someone either help me re root or unroot it so that the kindle runs normally. I don't know what mode that slow one is, but you can't do much of anything. I tried to roo a few times, and tried to put in the stock kindle update and re run it, but nothing is working to get it out of the slow mode. Right now my computer can see and put things onto the kindle, and when trying to root, it seems like it is trying to work, but since the kindle is slow, I don't know if it is getting stuck and not finishing.
Can you help me figure out what is wrong?
Click to expand...
Click to collapse
Yep sucks for us for now it seems
Mine is in the same state. To unslow mo it all i found that works is using recovery mode to erase every single thing on it. This will speed it back up to normal. Beyond that i don't have a clue what to do.
You can enter recovery mode if you dont know how by pressing volume down and power. Or dl droid explorer run it click the multi colored shield icon and reboot to recovery.
I would hold off for now though. As one of these guys may have a way to save you all the head aches i have now. I had psp emulator playstation emu nintendo ds dolphin aka game cube and wii all running properly now all gone. go figure. Pain in the rear to get em all running properly. Oh worst bit loosing my crisis core newgame + save lvl 35+ with all items etc etc. Was gona put the hurt on every thing LOL
Oh and if theres any amazon employees lurking and reading great job on becoming a apple clone wanabe In other words amazon you all need to get a grip. People want to customize their tablets and have something that runs like mad with out regards to warranty. We want our tablets the way we want them not the way you want them. No one likes apple with their forced updaties etc

benee16 said:
My kindle hd 8.9 was re rooted using bin4ry v31 after the last ota update 8.4.8. It worked fine. Now there was another ota update to 8.4.9 on 6/14/14. I tried using the same method as before. ADB is enabled in my kindle, I am seeing Android Composite ADB interface. when I plug the kindle in. I got through part of the re root, where it rebooted, and now it is extremely slow, has a black screen with white cracked lines to slide in open, and although some things work they are very very slow. Please can someone either help me re root or unroot it so that the kindle runs normally. I don't know what mode that slow one is, but you can't do much of anything. I tried to roo a few times, and tried to put in the stock kindle update and re run it, but nothing is working to get it out of the slow mode. Right now my computer can see and put things onto the kindle, and when trying to root, it seems like it is trying to work, but since the kindle is slow, I don't know if it is getting stuck and not finishing.
Can you help me figure out what is wrong?
Click to expand...
Click to collapse
Factory reset is always better than flashing and other serious tinkering. kindle hd 8.9 is still rootable with 8.4.9 update, I did it and another member KatanAlive have done it.

What method did you use to root? There are a few different methods. used bin4ry v31 I used the old special option, then also tried the old option.

akb1ajay said:
Factory reset is always better than flashing and other serious tinkering. kindle hd 8.9 is still rootable with 8.4.9 update, I did it and another member KatanAlive have done it.
Click to expand...
Click to collapse
Ive tried various tools etc. While it seems i am able to get root i can not for example view the root directory in adb shell. I can kill any process under ps list even ones ran by root. Again the root directory shows as empty under ls. Running the superuser app that does show under apps seems t do nothing (im assuming this is because root is already active by this point) It does load but nothing in log window. Also it remains stuck running extremely slow. I can not install google frame work etc.
What i want to do is just go with a custom rom and be done with this mess. After all if amazon managed to force updates on kindles with ota disabled and blocked once they will likely be able to do so again. So theres zero point in staying on a stock rom even downgraded and or rooted.
Now the only problem there is it seems rom update requires fastboot? If this is not the case what are the steps to go about it by a different means? Or what methods other than fastboot cables are there to force it in to fastboot with out ripping in to the kindlefire hd 8.9 in my case?

benee16 said:
What method did you use to root? There are a few different methods. used bin4ry v31 I used the old special option, then also tried the old option.
Click to expand...
Click to collapse
I used manual method described in this thread and yesterday another member also used this same method to root the Kindle with update 8.4.9 http://forum.xda-developers.com/showthread.php?t=2069117
I have been extensively reading this forum for rooting Kindle Fire HD 8.9 and I have seen people failed just because of a simple mistake or not starting afresh. Many people were able to overcome their anomalous problem just by a factory reset and then starting again the process of rooting.
No one knows at which step problem started to appear until you clarify completely that what method you were following, or did you install some other drivers mentioned in another method, or did you interrupted the progress, or any other tinkering you had had done earlier with Kindle.
Every method pre assumes that your device is in default condition and your PC has favourable environment for the completion of the rooting process. Like a meber was following the process of rooting and when a stage came to enter his Amazon password, he entered the password but the process could not be continued, because his Kindle was not registered , so even after entering the correct password the process was aborted. Later he registered his Kindle and started agin and it was rooted.

So true what you've said about it not being a fresh root. I am going to try a few more times to root, then do a factory reset. My kindle could use a fresh start, but I thought I'd try just for future knowledge. If anyone else comes back from the slow kindle stage, please contribute what you've done to fix it because it may help someone else resolve their issues.

I decided to do a full restore. Then I was able to use a bin4ry script for kindles to root. Now I am having difficulty getting google play to work again. I keep getting an error not enough space on the partition \system. Free up 6MB in system and try again. I put a version of google market on to see if there would be a difference. I was able to open it, but nothing will download. Anyone else have any experience with this problem?

benee16 said:
I decided to do a full restore. Then I was able to use a bin4ry script for kindles to root. Now I am having difficulty getting google play to work again. I keep getting an error not enough space on the partition \system. Free up 6MB in system and try again. I put a version of google market on to see if there would be a difference. I was able to open it, but nothing will download. Anyone else have any experience with this problem?
Click to expand...
Click to collapse
If you have rooted Kindle "not enough space" problem can be easily resolved. Is your Kindle rooted?

Yes my kindle fire hd 8.9 is rooted. I currently have version 8.4.9 software from amazon.

benee16 said:
Yes my kindle fire hd 8.9 is rooted. I currently have version 8.4.9 software from amazon.
Click to expand...
Click to collapse
I too have had this low space problem after updating to 8.4.9. I was despaired but after searching the internet for 2/3 hours I found the solution. First thing you need to do is to get Titanium Backup from somewhere. It has the capacity to convert system app to user app and this will free up some ROM space so you can install Google Play afterward. Convert one by one some system apps that are not critical to Kindle's functioning, to user app. For example, you can convert Silk browser, Amazon Video, Amazon music, Kindle tutorial, Office Suite to user app. The moment you have above 20 MB free space in ROM you can install there Google Play. I am not sure if a free version of Titanium Backup have this functionality or not, I have installed a pro version of it. If free version is of no use then get a pro version from somewhere. I think you know where to get it from. Good Luck.

Wow thanks so much for the info. I did not have the pro version of titanium. Instead I used /system /app mover which is a free app. I changed a few system files to user files like suggested and am now able to use google play. I made sure I could download apps from it also, and it worked just fine. Now I have to re download apps I lost when I had to restore.

benee16 said:
Wow thanks so much for the info. I did not have the pro version of titanium. Instead I used /system /app mover which is a free app. I changed a few system files to user files like suggested and am now able to use google play. I made sure I could download apps from it also, and it worked just fine. Now I have to re download apps I lost when I had to restore.
Click to expand...
Click to collapse
:good:
would not you press Thanks Button?

AFTV1 Downgrade issue

I've seen that some people were able to successfully downgrade AFTV1 after rooting with Dirtycow. I'm able to get root, but downgrade doesn't seem to work and I don’t know what I’m doing wrong.
I have an amazon fire TV V1 with 51.1.4.0_User_514006420 software version. I downloaded the 51.1.0.2_user_510058520 update, renamed it to update.zip, followed the guide (here: http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/) for changing the ROM. When I do adb reboot recovery I get this message:
“System update was not successful. Your amazon fire tv will restart in a few minutes and should resume normal operation.”
When it restarts, it’s still on the same version I had. I’ve tried pushing the stock recovery image like the bottom of the upgrade/downgrade guide suggested, but it doesn’t seem to work. Does someone have any other ideas on how to get this to work?
I checked that the update checks out with the md5 hash. I just can’t get it to work. What should I try to do next? Is there a better guide? I'd like to install a pre-rooted ROM.

On the off chance that Amazon changed the 51.1.0.2 image they are serving, try downloading and using the one from here. Then follow my guide here to install it. You should also check the md5 hash value of the 51.1.0.2 image AFTER it has been transferred to the FTV1 by following this guide.
If you still have problems, copy and paste your entire ADB/shell text here so I can see if you did anything wrong.

@AFTVnews.com thanks for the response! I checked the md5 and it seemed to have matched. I re-ran through the steps an it appears I may have put command in cache instead of cache/recovery. It pushed successfully.
Now... it seems like that version of AFTV is strange. It has a lock screen and my aftv remote won't allow me to unlock it. Here is an image of what I see: Locked Amazon fire TV Screen so I can't open it to run towel root. Any ideas?
Update: I was able to get passed the lock screen by clicking a bunch of buttons on the remote at the same time. I'm rooted again! I'll continue the guide! Thanks for your work on this!
Update2: I'm running the latest version of the rooted software. Thanks for the guides!

uofirob said:
@AFTVnews.com
Update2: I'm running the latest version of the rooted software. Thanks for the guides!
Click to expand...
Click to collapse
Awesome. Glad it worked out.

Last night, I stopped after the custom latest rooted version of the ROM was installed. I keep getting "Amazon is unable to connect to the service" when going to the different menu options. Do I have to disable my firewall rules on my router, or was it just an oddity?
AFTVnews.com said:
Awesome. Glad it worked out.
Click to expand...
Click to collapse

I confirmed that I'm still getting the unable to connect to service last night. Should I just do a factory reset? Would that help? At this moment, the only way for me to launch apps is to go through System -> Manage Applications and it's really annoying. I was able to confirm that Kodi was able to connect to the internet, so I know that it's not the connection.

uofirob said:
I confirmed that I'm still getting the unable to connect to service last night. Should I just do a factory reset? Would that help? At this moment, the only way for me to launch apps is to go through System -> Manage Applications and it's really annoying. I was able to confirm that Kodi was able to connect to the internet, so I know that it's not the connection.
Click to expand...
Click to collapse
Since you're rooted and on the latest prerooted ROM, you should remove the domain blocks on your router/firewall. It sounds like that's the issue. Just be sure you have done method 1 at the very least from my update blocking guide. You can also do method 5 to be extra safe.

I tried removing the firewall blocks but I still get "We are currently unable to contact our servers." Should I re-add the firewall blocks and factory reset?
UPDATE: I was able to resolve this by signing in to my amazon account. Apparently for some reason it signed me out. Thanks for all of your help!
AFTVnews.com said:
Since you're rooted and on the latest prerooted ROM, you should remove the domain blocks on your router/firewall. It sounds like that's the issue. Just be sure you have done method 1 at the very least from my update blocking guide. You can also do method 5 to be extra safe.
Click to expand...
Click to collapse

Firetv2: need help unblocking updates, unrooting, etc

Hi guys. I have a FireTV 4k box. The 2nd gen one.
When I bought it way back upon release a few years ago, I rooted it, used it for a bit, and put it in a box. Just recently I took it back out and started using it again.
Whatever method I used to root it etc is unknown, as it was afew years ago, and I can't find anything similar anywhere online. At the time, downloader wasn't a thing, and you had to adb in and sideload apps.
I am currently on 5.2.6.3
The box won't update at all.
I adb' into the box, and found SU doesn't work. I was able to get temp root via mtk-su and successfully ran the pm unhide com.amazon.device.software.ota and pm enable com.amazon.device.software.ota commands.
The firetv will now at least SEARCH for updates (where it wouldn't before) but doesn't find any to install.
The manage_recovery command to check status won't run. Says manage_recovery not found.
I'm not sure what to do next.
I just want it back to completely stock.
I'm having issues with apps working, but upon restart of the firetv the somehow get transferred to a non-existent sd card and will no longer run.
Netflix in particular.
Can you guys give any guidance here?

zx7ninja said:
Hi guys. I have a FireTV 4k box. The 2nd gen one.
When I bought it way back upon release a few years ago, I rooted it, used it for a bit, and put it in a box. Just recently I took it back out and started using it again.
Whatever method I used to root it etc is unknown, as it was afew years ago, and I can't find anything similar anywhere online. At the time, downloader wasn't a thing, and you had to adb in and sideload apps.
I am currently on 5.2.6.3
The box won't update at all.
I adb' into the box, and found SU doesn't work. I was able to get temp root via mtk-su and successfully ran the pm unhide com.amazon.device.software.ota and pm enable com.amazon.device.software.ota commands.
The firetv will now at least SEARCH for updates (where it wouldn't before) but doesn't find any to install.
The manage_recovery command to check status won't run. Says manage_recovery not found.
I'm not sure what to do next.
I just want it back to completely stock.
I'm having issues with apps working, but upon restart of the firetv the somehow get transferred to a non-existent sd card and will no longer run.
Netflix in particular.
Can you guys give any guidance here?
Click to expand...
Click to collapse
I know you wish to go back to stock but perhaps you may wish to use the new and improved root (Magisk or Supersu) and upgrade your box that way.
The Sloane 2nd generation Firetv Box can now be fully unlocked. This will allow you to upgrade your box to a more recent firmware.
A simple step by step guide can be found here :
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
Hope this helps
Regards

That is a good idea, and may work. I'll give it a shot and see what happens, thanks!
Hopefully it fixes whatever bug is causing apps to flag as installed on a non-existent SD card and no longer run.
All I'm looking for, really.

zx7ninja said:
That is a good idea, and may work. I'll give it a shot and see what happens, thanks!
Hopefully it fixes whatever bug is causing apps to flag as installed on a non-existent SD card and no longer run.
All I'm looking for, really.
Click to expand...
Click to collapse
Yeah it's just really old firmware tbh so the cert.zip and/or the ota update apks are probably deprecated.
Goto unlock root twrp unbrick Sloane thread here :
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
Just have a read through the OP on page one and familiarise yourself. Follow it to the letter and you'll be able to update your box no problem.
If you need any help just ask and someone will be around to help you out if need be.
Regards

Is there an advantage of doing this over the pre-rooted rooms flashed in TWRP? I have a rooted fire TV v2 that I have done periodic updates on but it seems like it always has another update to do. Updates are blocked but it pops a message randomly saying there is and update giving 60 seconds to respond or it reboots trying to update. Would this method of root/updates be easier or more up to date?

ottoguy said:
Is there an advantage of doing this over the pre-rooted rooms flashed in TWRP? I have a rooted fire TV v2 that I have done periodic updates on but it seems like it always has another update to do. Updates are blocked but it pops a message randomly saying there is and update giving 60 seconds to respond or it reboots trying to update. Would this method of root/updates be easier or more up to date?
Click to expand...
Click to collapse
Definitely unlock Sloane with this new method.
IMO you have FULL control over the box. Also you have more easier management of your root access (Magisk Manager)
OTA can be handled easily either by adb command or use an app such as luckypatcher to disable/enable ota onscreen.
I would recommend this unlock to anyone wanting a more upto date root and fireos.