Database Users

Frak! Fat fingered permaroot - root is now an unknown user

Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.

vettejock99 said:
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
Try the alternative method in my guide with rage instead of visionary and see if that helps. One thing is does is reinstall su and busybox. Also, make sure that you have deleted the PD15IMG.zip from your sdcard so that this doesn't happen again.

Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!

just either use the stock rom in the downgrading post, or flash one of the new ones i.e. icedglacier or Gorillas's. iceglaciers seems to be pretty functional right now gorillas is awesome just has a few kinks he's working on

vettejock99 said:
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
try this (you should be s-off) and assuming you have busybox already installed.
run rage to get su in your terminal then run the following command in the terminal
busybox mount -o remount,rw /system
busybox chown 0 /system/bin/su
busybox chmod 4755 /system/su
install the superuser.apk if it's not already installed
make sure everything is working by opening a adb shell and typing "su" to verify.
use your phone normally and try rebooting after a few hours. hopefully the fs cache flushed and root is fixed permanently.

mrpanic7 said:
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
Click to expand...
Click to collapse
Okay, first things first - guess I have to try to see if I can even get S-OFF again or if I've completely screwed myself.
Going to try the alt root method, but I think I have been and it wasn't working. So unless me being tired at 1am was the cause, I may need some more help. Thanks.

Okay, followed the s-off guide, and ran the busybox commands posted above, and I am back to S-OFF and now I get "permission denied" instead of "unknown user root". I think this is progress, but still can't flash because I don't have root. I noticed opening Superuser keeps FC'ing...

Please post questions in Q&A section.

just follow this guide here, which you are already familiar with. it's for temp root using rage. but since your phone has the eng hboot with s-off it should become permanent once the FS flushes out to disk (flash)
http://forum.xda-developers.com/showthread.php?t=797042
follow the guide for root and mainly to get the su files installed just in case your's didn't instal properly prior. when you are done just type "sync" multiple times in your terminal
wait a while an hour or so. then reboot to verify that it's permanent.

Same thing happened to me with the unknown root user. What finally fixed it for me, was redoing the adb commands that put those files on your device so you could use rage. Once it re put the files on my phone, I did the rage commands again and it worked
Sent from my HTC Glacier using XDA App

Thanks, everyone! I am working again, and I cannot tell you how much I appreciate the help. I was THIS CLOSE to giving up on this phone.
Thanks again.
Mark

Unlock Problem: Permission Denied??

I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.

If I root the phone, will that work?
Also, what are some good programs to copy the EFS folder?
Sorry for all the questions.

I'm fairly certain you have to be rooted

I am rooted as of 10 mins ago.
I tried to unlock it and I still got the same thing.
It says Permission Denied
Anyone have any ideas?

Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.

molson24 said:
Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.
Click to expand...
Click to collapse
in Terminal?
type:
su
(and hit enter)
before the command that needs superuser permission.

Also you probably would be better off just pulling the whole efs folder.

molson24 said:
I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.
Click to expand...
Click to collapse
for permission denied try this:
open terminal emulator on your phone (download it from the market if you dont have it yet)
or you can type "adb shell" without quotations into the dos prompt and do it from there.
and type:
su
chmod 777 /efs/nv_data.bin
exit
exit
then in the dos prompt try:
adb pull /efs
or if you just want nv_data.bin:
adb pull /efs/nv_data.bin
if you need further help, this was written for the 19000 but it should help you anyways.
http://www.communityhosting.net/sgsunlock/i9000.html

You need to copy your nv_data.bin from your phone to your pc
You should see a folder made in the repair_nv_data folder like this Sauverarde_efs_apres_reparation
Move your nv_data.bin there along with nv_data.binvierge and repairation_nv_data.jar and Step2 and Step 4
Run Step 2 again and then Step 4 after its done creating the new nv_data.bin
I can't remember but I think you have to delete nv_data.md5 and a few others from your phone first

Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol

molson24 said:
Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol
Click to expand...
Click to collapse
lol yeah I can see that happening
I've accidently denied su permission a few times myself even when I do notice the pop up
well congrats!

Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?

molson24 said:
Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?
Click to expand...
Click to collapse
Unlocking should not break your downloads (At least I've never heard of it happening) but you'll be fine flashing any rom you like, without having to unlock again.
are you still on t-mobile just unlocked?
orare you on a different carrier now that your unlocked?
the main things to be careful of when flashing roms is:
be careful going from froyo (2.2 JK2/JK6) back to eclair (2.1 JFD/JI6) its a little tricky, but not too bad.
and be careful with lag fixes, if you use one always disable it before flashing. (I never found them very useful myself anyways)
going from JFD to JI6 and back should be fine though.
if you want a completly clean slate then you can use Odin and it still wont re-lock your phone.
you might even find that you like some of the roms out there better than the stock one
I know I did.

[Q] Rooting GT540

Hello all,
I'm kind of a newbie, but able to follow step-by-step instructions.
I've tried two different methods of rooting my phone, the password method (android.modaco.com/content/lg-gt540-optimus-gt540-modaco-com/310737/how-to-root-your-lg-gt540) and using Z4 Root. I assumed the first one had worked, but somehow not. When I tried with Z4, it installed Super User and gave me the option to "un-root", but testing it in adb and terminal emulator inevitably ended with a "failed to link su CANNOT LINK EXECUTABLE" message. Apps like Titanium Backup won't work either. I tried factory reset, and when I restarted it Super User was still there, but when I opened it, it gave a message saying that there was a new su update. I okayed it to install but it failed and said it was placed on the SD card. Super User instructed me to reboot in recovery mode and install it from there, but I wouldn't know what to do with it.
Anyone know where I went wrong, or have a foolproof method of actually getting my phone rooted? Thanks so much!

laurengirl said:
Hello all,
I'm kind of a newbie, but able to follow step-by-step instructions.
I've tried two different methods of rooting my phone, the password method (android.modaco.com/content/lg-gt540-optimus-gt540-modaco-com/310737/how-to-root-your-lg-gt540) and using Z4 Root. I assumed the first one had worked, but somehow not. When I tried with Z4, it installed Super User and gave me the option to "un-root", but testing it in adb and terminal emulator inevitably ended with a "failed to link su CANNOT LINK EXECUTABLE" message. Apps like Titanium Backup won't work either. I tried factory reset, and when I restarted it Super User was still there, but when I opened it, it gave a message saying that there was a new su update. I okayed it to install but it failed and said it was placed on the SD card. Super User instructed me to reboot in recovery mode and install it from there, but I wouldn't know what to do with it.
Anyone know where I went wrong, or have a foolproof method of actually getting my phone rooted? Thanks so much!
Click to expand...
Click to collapse
What version of android version u r running with?

It's a 1.6 :/

The password one should work for 1.6
Sent from my GT540 using XDA App

Universal Androot?
laurengirl said:
Hello all,
I'm kind of a newbie, but able to follow step-by-step instructions.
I've tried two different methods of rooting my phone, the password method (android.modaco.com/content/lg-gt540-optimus-gt540-modaco-com/310737/how-to-root-your-lg-gt540) and using Z4 Root. I assumed the first one had worked, but somehow not. When I tried with Z4, it installed Super User and gave me the option to "un-root", but testing it in adb and terminal emulator inevitably ended with a "failed to link su CANNOT LINK EXECUTABLE" message. Apps like Titanium Backup won't work either. I tried factory reset, and when I restarted it Super User was still there, but when I opened it, it gave a message saying that there was a new su update. I okayed it to install but it failed and said it was placed on the SD card. Super User instructed me to reboot in recovery mode and install it from there, but I wouldn't know what to do with it.
Anyone know where I went wrong, or have a foolproof method of actually getting my phone rooted? Thanks so much!
Click to expand...
Click to collapse
You obviously know I don't have this phone =], but read something somewhere about Universal Androot from market. I don't know if you got this on my FB or whatnot. GL

Thanks, but same message:
link_image[1638]: 1841 could not load needed library 'libbinder.so' for 'su' (load_library[984]: Library 'libbinder.so' not found)CANNOT LINK EXECUTABLE
Titanium backup still cannot acquire privileges. I've tried universal androot now as well.

laurengirl said:
It's a 1.6 :/
Click to expand...
Click to collapse
why don't you upgrade to 2.1 or 2.2

Check whether u have file libbinder.so in ur system/lib folder.
If u don't have
Exatract it from .zip and change the name to libbinder.so then past this folder in system/lib
I am not sure whether it will work or not. it is kind of workaround

Thanks, I ended up unrooting it with z4, doing a factory reset and formatting the sd, and then rerooting with androot and now it works! No idea why it worked this time and not the three or four times before... I guess tenacity pays off. I appreciate the help!!

[Q] unable to get su when attempting root

I am trying to root my phone and am running into trouble early. I have watched the videos & followed instructions. Somehow I am either missing something or my phone is jacked somehow.
I made sure it's not in fast boot, USB debugging & unknown sources are on. I have tried visionary r14 & r11. I have also tried multiple factory resets.
OK, I use visionary with set system r/w after root checked. I go from there to Term. Emulator & when I type su it shows "unknown user root" without the quotes. I've tried to continue but it gives me other errors and S is always on when I check.
I've searched Google & the forums and haven't found much that's been able to help me.
If anyone has seen this I would appreciate the help. Thanks!

Visionary (r11 & r14) are only temp root tools. You must use one of the two methods (both are in my signature) to turn s-off. As long as your s-on you will not be able to permaroot your phone.
Once you turn off the phone, and turn it back on you've lost Root Access. and that's why it's given you that error. If you pull the battery wait about 30 seconds, put the battery back in. Then temp root you should see a "superuser" icon appear. Once you see that try your SU command from terminal emulator. The other thing you can try is setting up your ADB (link in signature). Navigate to the c:/adb folder then typing in ADB shell. You should see a $ sign appear. Type SU from the Command Prompt and it should ask you to approve the SU access on the phone. once you've gained temp SU access you can proceed with one of the two methods i've got posted to finish turning s-off.

It's the temp root I'm getting stuck at. I do get the superuser icon after I do the temp root. I go directly to emulator and type in su and that is when it tells me "unknown user root". I will try the ADB method when I get home from work if nothing else is figured out before that.

Same deal for me. Not sure if my MT4G is a newer model or what. I've literally done EVERY set of instructions and youtube videos on rooting and keep getting stuck at the same place. Typing su into terminal emulator and getting unknown user root. I have reset my phone, taken the battery out for five minutes and re-inserted it. I have tried both visionary 11 and 14 versions and clicked temp root. Once the temp root process completes and comes back to visionary+ I go straight to terminal emulator, type in su and get unknown user root. Unlike dbharr I DO NOT get a superuser icon after temprooting with visionary. It's not like i'm fudging up any part of the process here. I'm stuck at like step 2 of the rooting process. Any ideas anyone?
Software version is 2.2.1

You may have a newer chip set and may only be able to root with s-off by using the gfree route. It was the only thing that worked for me.
In my situation I had visionary installed, root folder in the root of my sd card, and followed the unlockr method for root access.
I temprooted and checked temp root on boot and rw one too.
I ran terminal emulator, typed in the commands and the process ran and looked like a success.
I powered my phone down and boot into hboot and s-on showed up.
I tried the same process and factory reset between tries.
I then found out there was another way to get perm root with s-off using a similar process.
I factory reset and placed visionary apk and gfree folder on the root of my sd card.
I went on the android market and installed root explorer (there plenty others you can use it only need to be able to access your root) and also terminal emulator.
I installed visionary and temp rooted (using same temproot method from unlockr.com) my phone I downloaded the gfree file and extracted it on my cpu then moved it to the root of my sdcard.
Then using your root explorer go into gfree folder and copy the file called "gfree" and only this file.
The go into the root of the phone and your going to paste that into the local folder in /data/local/
From there you type in a few commands in terminal emulator. It will run thru a process then power down.
Boot into hboot and verify it shows s-off
If so reboot phone. When your phone boots up visionary should have temp rooted your phone.
If so Open up visionary and uncheck temproot on boot and click attempt perm root. Your phone will reboot and you have perm root. Verify by typing su in terminal emulator and then if you get # your good to go.
If you dont get s-off try factory reset and repeat process, you should be able to find the instructions if you search gfree and it should come up but if im not mistaken its a stickie on the developement forum
Hope this helps!
HTC Glacier
Perm-rooted S-off

If root.sh method is not working, use gfree + visionary method. Worked for me as a charm.

People, please bother to read before answering questions. Marking below the important part of the question that everyone is missing:
corollatercel said:
Same deal for me. Not sure if my MT4G is a newer model or what. I've literally done EVERY set of instructions and youtube videos on rooting and keep getting stuck at the same place. Typing su into terminal emulator and getting unknown user root. I have reset my phone, taken the battery out for five minutes and re-inserted it. I have tried both visionary 11 and 14 versions and clicked temp root. Once the temp root process completes and comes back to visionary+ I go straight to terminal emulator, type in su and get unknown user root. Unlike dbharr I DO NOT get a superuser icon after temprooting with visionary. It's not like i'm fudging up any part of the process here. I'm stuck at like step 2 of the rooting process. Any ideas anyone?
Software version is 2.2.1
Click to expand...
Click to collapse
To corollatercel:
If Visionary doesn't temp-root your phone, you could attempt it using SuperOneClick (google it) from PC, using rageagainstthecage or psneuter method. Just substitute the steps for temp-root using Visionary to temp-root using SuperOneClick.

Jack_R1 said:
People, please bother to read before answering questions. Marking below the important part of the question that everyone is missing:
To corollatercel:
If Visionary doesn't temp-root your phone, you could attempt it using SuperOneClick (google it) from PC, using rageagainstthecage or psneuter method. Just substitute the steps for temp-root using Visionary to temp-root using SuperOneClick.
Click to expand...
Click to collapse
Thanks, this is the answer I was looking for. An alternate method of temprooting. I will try this and post results. Thanks Jack.

Ok you guys may think i'm kidding but I tried both methods outlined
Here:
SuperOneClick trying both psnueter AND gingerbreak options
http://forum.xda-developers.com/showthread.php?t=803682
And
Here:
RageagainsttheCage
http://forum.xda-developers.com/showthread.php?t=792016
and even after superoneclick says its rooted AND says says success when it asks if I want to test root by sending su command, whenever I go into terminal Emulator and type in su I get permission denied or unknown user root whenever I tried su through adb shell through Dos on my machine. I dunno what is it with my device. I did all of this after fresh factory resets just so you all know. I dunno my MT4G must have a newer chipset that's not vulnerable to the current exploits is all I can say. I've follow these instructions to the letter more than twice each time factory resetting just to make sure things are fresh. Still no dice.

I never did get mine working. I did get a warranty replacement & had it rooted within 10 minutes of being out of the box. That makes me think it was something with the phone. Best of luck to others with the same problem.

dbharr said:
I never did get mine working. I did get a warranty replacement & had it rooted within 10 minutes of being out of the box. That makes me think it was something with the phone. Best of luck to others with the same problem.
Click to expand...
Click to collapse
Yeah unfortunately am not in that same position. It sucks. Guess i'm stuck with it for the moment. Only reason I really wanted to root and upgrade was so I could download netflix. I went from the G2 to the MT4G and had NO idea it was just compatible with certain devices. I've tried different versions of the netflix app on here too but they all require you to have root. Hopefully they make the app compatible soon.

Here's an update everyone. I was FINALLY able to get everything working. I had to use a tool called Z4root to gain temproot. You can imagine my relief AND also frustration after I installed z4root and things just started running just the way it was supposed to. I gained temp root in a matter of minutes and after doing so I was able to use the gfree method to perform all other functions that are a part of the rooting process. And for the record ALL other tools did not work for me:
- Both versions of visionary + 11 and 14
- SuperOneClick using psnueter AND rageagainstthecage exploits
Just thought I'd share. Thanks a lot guys. I had already put my mytouch on cl for sale or trade for a G2 because I thought my device could not be rooted or anything. until about 1 o clock in the morning I got it workin...ha.

Thats sweet man im glad you got it done, only difference I was avle to use visionary
Sent from my HTC Glacier using XDA App

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.