Develop Bugs

[Q] OTA RootKeeper not giving me the option to Temp Unroot???

Hi all..
I Rooted my Fire using KFU..
Then I installed OTA-RootKeeper
But I dont get the option to do a Temp Un-Root...
Any suggestions? It lets me Protect root but that is all it lets me do..
I did notice on the check boxes for "Root Permission has been granted" is not checked.. Could this be the cause??? And if so how do I fix? I thought KFU gave me root permission?
Thanks!

I think you did not install superuser.apk on your kindle. Without it having root is pretty useless for apps. Superuser gives you an option to allow root access to the app. If you already have superuser you may have it disabled for OTA. Otherwise a problem may have occurred with the rooting process. Tell me if this works.

That was it.. Thank you VERY much...
Wonder why KFU don't include superuser..

Glad it worked for you Not sure though why it is not included in kfu though I know in the past when you manually rooted the kindle super user would automatically get installed therefore it remain on the kindle unless you wipe. Though I guess you could recommend it to the developer to add.
Sent from my Galaxy Nexus using xda premium

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] "Permission Denied" from ES FE on rooted KF2

First off, let me say that I'm completely new at this, and quite honestly have no idea what I'm doing.
I just rooted my Fire with this guide, Bin4ry's root worked successfully and superuser was installed and everything. However, when I tried to launch Qemu's Root, the program didn't really do anything, it just stopped at 'daemon started'. But since superuser was installed, I figured everything was okay and went on to follow this guide to installed google play. The Google Services installed fine, but whenever I try to move the Vending.apk into the correct folder, ES FE just returns 'Permission denied.'
Does this mean that the root wasn't successful? How can I fix this and get google play on my kindle?

Edit: whoops wrong device forum. Principle should be the same though.
Have you checked root via suchecker to confirm root?
Most likely you haven't given su permission to ES yet. Under tools in ES go to Root Explorer and then select the mount option. Give it Read/Write permissions and then you should be able to move it.
Sent from my LG-P769 using xda app-developers app

What he said I settings on es explorer if it says root check it
Sent from my GT-P3110 using xda app-developers app

That worked great, thanks Protomartyr. It's working fine now.
EDIT: However, I'm getting a lot of 'Your device isn't compatible' for apps like Chrome, Duolingo, etc. and it's not letting me install them. They probably are compatible, but I can't seem to get around Play's not allowing me to install them. Is there any way to make Play allow me to install them?

Glad I could help
Play store incompatibility can be bypassed by:
changing the DPI (depending on what ROM you are running)
OR
Using an app such as Market Helper to temporarily "spoof" your device as something else (i.e. tricking the Play store to think your kindle is a nexus 7 so you can install apps that can run on it)
I am not familiar with the kindle fire 2 (I have a HD 7" ), so hopefully someone with a KF 2 can give you more specific instructions!
Sent from my LG-P769 using xda app-developers app

[Q] Kindle fire 2nd gen update 10.4.1 re-rooted

Hello I rooted my kindle fire 2nd edition when it was version 10.3.1. Everything was working fine then I turned it on one day and the root I installed stopped working. I looked at the version number and it had changed to 10.4.1. I re-rooted it with the same tools I used the first time. It worked fine for a few minutes then I started getting the message pop ups [the process com.google.process.gapps has stopped] then [es taskmanager has stopped]. When I go to the google apps it starts the same pop ups again [google play services has stopped]. Everything seems to work ok. I tried to reinstall the google apps and framework and vending pak. Nothing will get rid of the pop ups. Any help would be greatly appreciated.

Same thing happened to me, sort of. I found superuser failed to grant permissions after re-rooting. Uninstalled superuser and installed superSU and everything reset a right after a reboot.
Sent from my KFOT using xda premium

Red Screen
Red Cross154 said:
Same thing happened to me, sort of. I found superuser failed to grant permissions after re-rooting. Uninstalled superuser and installed superSU and everything reset a right after a reboot.
Sent from my KFOT using xda premium
Click to expand...
Click to collapse
My superuser and all the apps worked fine until I red screened it. I tried to put twrp on it using this thread [http://forum.xda-developers.com/showthread.php?t=2100963]. I have a red screen now. I am working on a fastboot cable to restore my original image. I read in another post after I red screened mine that Amazon tried to close the hole to prevent rooting. They almost have. I now have it back to version 10.2.3 using KFU. I also used it to re root it. I tried installing TWRP again using the same thread and boot looped it. I used the Kindle fire system image utility to un loop. I am now back to a rooted kf2 researching another way to install twrp.

I could swear I had the setting set to off with respect to automatic firmware updates, but either way my previously rooted Kindle 2nd generation did get the newest firmware. What is cool in my case, at least so far, is the Google play store still works perfectly fine, I can still order whatever I want from it. Also my ADW launcher still works fine, I can still switch in between the normal carousel Kindle stock interface or go over to an Android type of setting using ADW. Not sure about wallpapers but I don't really care as all I really wanted when I rooted was to be able to install the Google play store and be able to use whatever I wanted to use and I can still do that. I no longer have root though, Kindle free opens and tells me the kindle is improperly rooted and root checker tells me I am not rooted. Is there an easy way to reroot this or should I just leave well enough alone? I am afraid the next firmware update will finish the job on me and I have no way to stop that now (not that it worked the first time I set it to not update lol)

Reinstalled Twrp
I tried the thread [http://forum.xda-developers.com/showthread.php?t=2100963] for installing TWRP again and it worked perfectly. I now have twrp running. Next I will try to flash cm10.1 and gapps. Wish me luck. :good: I would like to thank Hashcode and all the other developers for the step-by-step instructions. I am now running CM10.1 and it works great.

[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.