Database Users

Kindle Fire lost root. Rooted with Burrito Root

Interesting issue I found today.
I have an Amazon Kindle Fire that I rooted using the Burrito Root method as described in the stickied thread above entitled: "Video guide to rooting etc..."
I followed the instructions as presented in the You Tube video, and achieved root.
I loaded the android market and downloaded the apps I had previously with no dramas. They all run fine.
Last night I downloaded Voodoo OTA Root Keeper as described in another thread.
I got to playing around with it today, and it said I did not have root access. Used the root checker utility as posted in the you tube video previously mentioned, and it too says no root. Attempted to use root explorer, and again no root. Power off and back on, same deal.
Weird to say the least. As far as I know, I have not had an update to the kindle firmware (current version: 6.2.1_user_3103920) which appears to be unchanged since I rooted. There were no issues when I rooted, and all functioned as it should have (rooted I mean)
The only thing I did do in the previous week was download an amazon movie to the device.
Any ideas on WTF happened?
I had been considering installing TWRP...now I am wondering if I should re-root using the same method, or uninstall the stuff I put on in the originl root, and just load TWRP, and do it that way?
Thanks for any input.

Burrito Root gives you root through ADB. In order to get permanent root that's usable by applications such as Root Explorer you need to push the su binary and install the superuser.apk. Not sure if that was covered in whatever video you watched, but there should be instructions and download links kicking around here and rootzwiki somewhere.

Easiest way is to use this http://forum.xda-developers.com/showthread.php?t=1399889 and use option 2 then 3. should be good to go after that.

skourg3 said:
Burrito Root gives you root through ADB. In order to get permanent root that's usable by applications such as Root Explorer you need to push the su binary and install the superuser.apk. Not sure if that was covered in whatever video you watched, but there should be instructions and download links kicking around here and rootzwiki somewhere.
Click to expand...
Click to collapse
For clarification, as I failed to mention it in my original post.
Superuser.apk was installed, as were all commands done through ADB as prescribed...it appeared to have worked flawlessly. Until now. LOL
I am new to the fire, not new to android.
It is rather puzzling, as I have never experienced this type of issue before.

Re use ota root keeper and restore your root
Sent from my Kindle Fire using xda premium

silvertrd said:
For clarification, as I failed to mention it in my original post.
Superuser.apk was installed, as were all commands done through ADB as prescribed...it appeared to have worked flawlessly. Until now. LOL
I am new to the fire, not new to android.
It is rather puzzling, as I have never experienced this type of issue before.
Click to expand...
Click to collapse
Superuser.apk and the su binary are separate things. These are the original instructions. Not sure what the video you watched suggests.
The su binary goes into /system/xbin and you need to:
Code:
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
When Superuser.apk is installed it gets put into /data/app. If you've only done one, but not the other, that's most likely causing your issue.
*Edit* In your original post you mentioned messing around with OTA Rootkeeper. There's a checkbox that backs up the su binary. Maybe it was unchecked when you temporarily unrooted? There's also a button that deletes the su binary backup. Very possible one of these led to your issue.

phunky123 said:
Easiest way is to use this http://forum.xda-developers.com/showthread.php?t=1399889 and use option 2 then 3. should be good to go after that.
Click to expand...
Click to collapse
I had looked at that. My question doing it using that method:
Do I need to uninstall/delete anything from my previous root? or will that program overwrite superuser, etc?
ghost_og:
The video I watched was the same video you link to.
I copied and pasted all of the commands into the adb shell as nat3mil describes.
I wonder where I went wrong? Weird.
Can I just connect the kindle to my computer, run burrito root, and then re-push the commands via adb as described ? I just don't wanna bork it up and brick it.

Veritass said:
Re use ota root keeper and restore your root
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Great idea! Just now tried that after seeing your suggestion. No joy. FML.

silvertrd said:
Can I just connect the kindle to my computer, run burrito root, and then re-push the commands via adb as described ? I just don't wanna bork it up and brick it.
Click to expand...
Click to collapse
It should be fine. I remember having to run it twice and I never went through and deleted anything. Here's something interesting: I checked both /system/bin and /system/xbin when I was rooted and unrooted. Even though I originally installed su to /system/xbin, OTA Rootkeeper places it into /system/bin upon restoring root.
I'm not saying you should do that, but just thought I'd bring it up. Maybe that has to do with why you lost root privelages out of the blue.
Also, I know certain Superuser.apk's were not working properly. The one included in the zip file at Androidpolice is actually com.noshufou.android.su-1.apk. Perhaps try using that one instead?
*Edit2* I just looked at the official thread and noticed he updated the zip and it now uses Superuser.apk. Not sure if Androidpolice ever updated their zip as well.

ghost_og:
Thanks!
I will give it a shot, and report back later this evening.
Regards,
SilverTRD

install busybox from the market and try again

KFU will tell you if it is rooted or not. just connect KF to your pc and run no harm going that far.

I am in the same situation as you are, same steps. Rooted with BR, but didn't root all the way, yet was still able to put the market apps.

My kindle Fire (non-HD) just "lost" root too!!!
No idea how it happened.
I successfully rooted last summer with the KFU and have temp un-rooted/re-rooted MANY times with OTA Rootkeeper . I went in yesterday to root, but the buttons were gone in Rootkeeper and it shows that I'm NOT rooted.
I tried to update/reinstall Superuser but I probably just made things worse.
Is there any way for me to get root back without losing all of my data??
If not, I suspect that I have to go back to KFU and do the root process again, but will this brick my Kindle???
Thanks all!

If you used KFU the first time it should work again as long as you can get good communication and the driver is still installed correctly. Do you still have twrp and fff? if so just flash modaco if you`re on stock no wipes needed and you will never have to worry about loosing root again http://forum.xda-developers.com/showthread.php?t=1439916

Thepooch said:
If you used KFU the first time it should work again as long as you can get good communication and the driver is still installed correctly. Do you still have twrp and fff? if so just flash modaco if you`re on stock no wipes needed and you will never have to worry about loosing root again http://forum.xda-developers.com/showthread.php?t=1439916
Click to expand...
Click to collapse
Thanks Thepooch! I'm at work now, so I'll have to wait until I get home to my laptop to try.
I had no problems with the driver or communication, so that "shouldn't" be an issue.
The root process with KFU actually went painfully smoothly when I did it over the summer so hopefully second time will be the same.
I still have twrp and fff, but I'm not sure what you mean by "just flash modaco if you`re on stock", but I'll come back if i brick.
While losing my data would suck, I won't lose much sleep if I have to wipe it.

Thanks again Thepooch.
Took less than 5 minutes to get the root back with KFU.

[Tut] Gain Back Root on Chickcharney Update! [Easy!]

Hey all OUYAins!
So recently I updated my OUYA to Chickcharney and lost root access *cue crying*
I tried installing RootMyOuya1.1 by WonderEkin but it didn't install. So I snooped around for different rooting methods such as ReRoot script by Eldon McGuiness (You can take a look at his script here).
The method that worked perfectly fine for me was to download a piece of software called Kingo (here). Simply download and install it and connect your OUYA to your computer via USB and click Start Root. Wait for the software to root your OUYA and it will eventually reboot. You should now have SuperSU installed with root access!
I hope this thread helps anyone having difficulty with getting root access on Chickcharney!

I'm assuming the device needs to already have been rooted prior to trying Kingo ROOT? I just got my system on Thursday and since I'm new it forced me to download the Chickcharney update and I can't figure out what the best way is to root my OUYA.

i just got one on friday and the same thing it updated automatically
i use this to root my system it still works
http://forum.xda-developers.com/showthread.php?t=2350900

my ouya was rooted before the update. yesterday I tried Kingo and it said "already rooted", but I had no root permission. So I clicked "root again" and after a minute or so my ouya was rooted again properly.
Thanks Sn0wdune

joserod1980 said:
i just got one on friday and the same thing it updated automatically
i use this to root my system it still works
http://forum.xda-developers.com/showthread.php?t=2350900
Click to expand...
Click to collapse
I tried that to root it but it said it couldn't find the Ouya. I'm running the latest update Chickcharney on mine. Do I need to wipe it to run the root?

circledrag said:
I'm assuming the device needs to already have been rooted prior to trying Kingo ROOT? I just got my system on Thursday and since I'm new it forced me to download the Chickcharney update and I can't figure out what the best way is to root my OUYA.
Click to expand...
Click to collapse
Well not neccessarily. It should still work in any case!
circledrag said:
I tried that to root it but it said it couldn't find the Ouya. I'm running the latest update Chickcharney on mine. Do I need to wipe it to run the root?
Click to expand...
Click to collapse
That's odd. Are you sure you have your OUYA connected via USB properly and the drivers are correctly installed?

Sn0wdune said:
Well not neccessarily. It should still work in any case!
That's odd. Are you sure you have your OUYA connected via USB properly and the drivers are correctly installed?
Click to expand...
Click to collapse
The driver's wouldn't install because I had to turn off driver signing. I got it working after that with Ouya Toolbox root... even though it was crashing part way through. I had to run the TEST version of Ouya Toolbox and just forced the root and I guess it was fine because it appears to be rooted.

KingRoot works

I tried the OS 4.5.2 rooting from the forum and that did not work. I tried KingRoot and its works. Can someone test this on OS 4.5.3 or higher OS please
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Sent from HDX 7 OS 4.5.2 Rooted

Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.

Sometimes you have to tried several times the last time I fail too but the second works. I dont know what cause it
Sent from HDX 7 OS 4.5.2 Rooted

PsymH said:
Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.
Click to expand...
Click to collapse
From what I've heard, 4.5.4 can't be rooted. If you have a 3rd generation HDX, then you have to first downgrade to 3.2.8 and then manually update to 4.5.2.

Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.

rabaker07 said:
Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.
Click to expand...
Click to collapse
You obviously understand the risk and assume you tried alternate (Moto) drivers along with different cables and host ports to confirm diagnosis. Note cables/ports that work on one device may not on another - especially finicky HDX hardware.
You're probabky not going to get a high confidence response to your KingRoot question as most take the full step of unlocking. Plus age of device and waning interest. Good luck.

Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul. The risks come in when you attempt to flash a ROM and it fails by partially loading and overwriting/erasing critical files without completing (loss of power mid flash!) or if the ROM is incompatible in some way and you are unable to flash your previous ROM. That's where bootloader recovery software comes in (TWRP and the like). So that you can access the system before loading (or failing to load) the ROM, and flash over it or flash a backup.
Moral of the story is that YES, Kingroot works on HDX 3rd Gen on 4.5.5.3. I tried it last night and it worked. I now have access to the root directory. Oh, the places you'll go!!
Sent from my Pixel 2 XL using Tapatalk

rabaker07 said:
Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul.
Click to expand...
Click to collapse
Nope; root attempts can yield a bootloop or otherwise dysfunctional device. Glad all worked out for you.

Ouch. I didn't realize that. It always seemed very benign and I've never had it go wrong. I guess I'm used to devices that are designed to be accessible. Fortunately my HDX rooted without a hitch.

Amazon has posted the Fire 5.1.1 update for 4th gen Fire Tablets!

OMG!
Amazon has finally posted the Fire 5.1.1 updates!!!
http://www.amazon.com/gp/help/custom...e_sb_swupdates
WOO HOO!

i only just found out this morning that they finally created a successful root for the last update (figures). I woke up and found my kindle with an Android tablet look to this update. How long til this can be rooted? Or does anyone think that the computer downgrade method will still work?

Well, it seems Fire OS 5.1.1 is already rootable with Kingroot, as I just did so successfully not five minutes after upgrading

what version of kingroot would work? i am using a kidle fire hd 6 (4th gen) and ive tried the latest i could find (4.8) and someone suggested i try 4.0, yet both failed multiple times. Oh, and my brother is somehow non-upgraded and is still at 4.5.5 yet i cant root his either.

WaywardOne said:
Well, it seems Fire OS 5.1.1 is already rootable with Kingroot, as I just did so successfully not five minutes after upgrading
Click to expand...
Click to collapse
I am going to update to this version today. Can you please provide me link to detailed steps (video if possible) for me to root and install GAPPs.
Thanks

It's quite simple really, I just downloaded the latest apk from the official website, kingroot.net, and ran it. As for GAPPs, however, I'm not sure which method to use just yet.

But I did too and it failed. I'm using a kindle fire hd 6 (4th gen) and kingroot is proving to be ineffective on all versions available and any competitor rooting systems. All claim it's not vulnerable to root and it fails every time. Sometimes it even reboots, but when I open kingroot, it claims it failed.
Update: just tried it again, failed again. Says it cannot root and that there is no root strategy available. Why am I not able to root?
Update 3minutes later: HFS it worked!!! Idk why it worked now, but thank you!

WaywardOne said:
It's quite simple really, I just downloaded the latest apk from the official website, kingroot.net, and ran it. As for GAPPs, however, I'm not sure which method to use just yet.
Click to expand...
Click to collapse
I used the latest apk from kingroot.net and it failed at %25.
Somehow I able to install google services & playstore without root using this
https://www.youtube.com/watch?v=MgeXdR92Sx0
edit: after reboot and try few more times finally it rooted. Once it pass 25% mark it goes very fast. Yay!!

5.3.1 ROOT! :)

Kingroot now roots 5.3.1!
If you are having trouble installng cm 12.1, try the supertool or @wtfjajaja's instructions.
wtfjajaja said:
try it a few times, i encountered the same problems as well
here's what i did
1. factory reset through recovery
2. root with kingroot, (it worked for me after 2 to 3 tries)
3. installed supersu-me 6.7
4. update su binary
it's important here! don't restart yet, my device bricked few times here
5. install flashfire 0.53
6. follow the steps to install cm12.1 under flashfire from here
7. enjoy
Click to expand...
Click to collapse
Supertool: http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Bricked?: http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Fingers crossed! I can't wait to start flashing roms!

If you're root then maybe you can use flashfire to flash a rom just like 5.1.2

tonibm19 said:
If you're root then maybe you can use flashfire to flash a rom just like 5.1.2
Click to expand...
Click to collapse
Flashfire needs supersu
or Cmsu to work.

hooks024 said:
Flashfire needs supersu
or Cmsu to work.
Click to expand...
Click to collapse
Try rootjunky's supertool after rooting to see if it can install it.

.
tonibm19 said:
Try rootjunky's supertool after rooting to see if it can install it.
Click to expand...
Click to collapse
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1

DoctorDark_ said:
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1
Click to expand...
Click to collapse
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.

marvelous news!!!

DoctorDark_ said:
Kingroot now roots 5.3.1! Hopefully someone can quickly push out a toolkit.
Click to expand...
Click to collapse
Would you add the 5.3.1 version in the title ???

tonibm19 said:
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.
Click to expand...
Click to collapse
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.

Nice I will try it out.

Good chance the latest versions of Kingroot (always evolving) will also work for those on FireOS 5.1.2.1-5.1.4. Worth a try before attempting a rollback to 5.1.2.

I couldn't get super sume to work.

not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)

ttcontributor said:
not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)
Click to expand...
Click to collapse
Not good - earlier builds of Kingroot froze around 29% before crapping out. Make sure you have the latest Kingroot app. Also try a factory reset (warning: you will loose personal apps/data) and do not register with Amazon during subsequent device initialization. This proved effective for some in the past. Recognize the community is still learning; expect some failures along the way.

Davey126 said:
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.
Click to expand...
Click to collapse
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.

-Yami- said:
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.
Click to expand...
Click to collapse
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.

Davey126 said:
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.
Click to expand...
Click to collapse
Come check my browser, I've read every single thread on the forums man, the thing is 5.1.2 is not same as 5.3.1 and device has locked bootloader and anti-rollback.
So it is not like my Motorola with unlocked bootloader, I am not sure if I always can save the device and also I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
So I had to make it clear everything works for 5.1.2 also will work for 5.3.1
Now I have to convert kingroot to supersu somehow (can't find the option under supertool like you mentioned.)
Your approach was a little bit harsh on me m8
It doesn't say "What can be done on 5.1.2 also can be done on 5.3.1" anywhere, it says the opposite everywhere.
So someone had to clear it out. Thank you for your help, It really helped me a lot.

-Yami- said:
Come check my browser, I've read every single thread on the forums man...
Click to expand...
Click to collapse
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
-Yami- said:
I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
Click to expand...
Click to collapse
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu

Davey126 said:
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu
Click to expand...
Click to collapse
The reason that I cannot return device to amazon is, shipment will cost more than the actual device from here to amazon, and I got it as a gift.
and Thanks so I missed out the part that Supertool automates the conversion when I click install Flashfire, thank you.
Now after this post everybody jumping right onto 5.3.1 root gonna know it, and the guy on first page have used Super Sume, so he probably would use
Supertool if he knew.