[Q] How to tell if rooted correctly? - Kindle Fire General

I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!

crimsontide said:
I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!
Click to expand...
Click to collapse
If you used BurritoRoot and you were able to successfully install the Market, then you likely have root.
Easiest and simplest way to 100% know is connect your KF to your PC. Run the following:
Code:
adb shell
su
If it says "su: Permission Denied" you don't have root (or at least it is not currently enabled). If it just gives you a prompt run:
Code:
id
If it comes back and says "uid=0(root) gid=0(root)" then you are good.

Make sure you use the superuser posted in the burritoroot post. There was one posted originally that was no good with the kindle fire but they updated to a working one.
Sent from my HD7 T9292 using XDA Windows Phone 7 App

if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
http://www.mediafire.com/?jj8sx4ojvq9i198

litotamez said:
if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
I tried that app and it reports, "Sorry, you don't have root access."
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac devices
List of devices attached
7766000600000001 device
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell
$ su
su: permission denied
$
Looks like I have some more work to do, and I am not sure where to start.
I have installed on the KF:
BurritoRoot: Kindel Fire Edition 1.0.0
version 1.0.0
SuperUser version 3.0.6
Click to expand...
Click to collapse

Ok I went back and re-ran everything. Had to uninstall SuperUser in the middle, but things seem to be working better now!!!
HTML:
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac root
adbd is already running as root
Traveler:KindleFireRootMacLinux crimsontide$ adb push su /system/xbin/su
-bash: adb: command not found
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac push su /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chown 0.0 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chmod 06755 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
4426 KB/s (785801 bytes in 0.173s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
2858 KB/s (785801 bytes in 0.268s)
pkg: /data/local/tmp/Superuser.apk
Success
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac reboot

Related

What is the correct way to add the SuperUser app?

Alright so I installed Haykuro's Hero rom the other night. I noticed su worked fine in terminal emulator, but I couldn't tether cause root apps weren't working. Figured I would try adding the Superuser.apk so that apps requiring root would work for me. I couldn't locate instructions on how to go about doing so and had to wing it a bit.
This is what I tried and it seemed to work...kinda.
Extracted su binary and SuperUser.apk from another build (Haykuro's 6.0r1)
adb push su /system/bin
adb push SuperUser.apk /system/app
All the apps that require root are working, but the SuperUser app is not asking for confirmation on new permissions request. So if I am correct in my assumption, su privileges are being granted to any app that makes a request for them.
If someone would care to elaborate on how this is properly done, I would greatly appreciate it.
If I remember correctly from when Haykuro release the Ion this is all that he said to do. i have done this also and it concerns me as the SuperUser app is give you the option to allow access and it is not working. No safe guard for the phone.
Below code is assuming you have already taken/have the su app from another build it can be found in the system/bin.
Code:
adb remount
adb push su /system/bin
adb push su /system/xbin
adb shell chmod 4775 /system/xbin/su
adb shell chmod 4775 /system/bin/su
You may also have to clear all data in the SuperUser.apk if you already have it installed. Do this by going to settings> applications> manage applications > Superuser permissions > clear data. But now my phone is asking for superuser permissions. I found this in another Thread but this is a windows.exe file the above codes would work for those who dont use windows and can't run the .exe file that you download there like myself.

DROID - Busybox Works, Then Doesn't

So I was trying to install Busybox on my DROID to use Metamorph and some other root applications. Stericson said I should be able to download via DroidSwap, but that didn't work so I went for the manual installation.
Following these instructions (http://www.novoda.com/blog/?p=3) I was able to successfully install Busybox on my phone. I typed busybox in the terminal and got a list of commands, I typed cp in the terminal and got the Copy syntax.
So I exited the terminal and went to perform something else and going back into the terminal I typed busybox again, except this time I get "busybox: busybox not found" ... I even navigated back to /data/busybox and if I do an ls of that directory the busybox file is in there, but I still get the "not found" when trying to run it.
Any thoughts as to why it would work once and now it doesn't.
Your best bet is probably to install it to /system/bin so it's in your path. Then you don't have to navigate anywhere to run busybox.
Just put the busybox binary into /system/bin and chmod to 755.

[Q] Rooting a rooted Verizon Droid 2 to Gingerbread 4.5.601.A955.Verizon.en.

Does GingerBreak work with this version of Gingerbread 4.5.601.A955.Verizon.en.us? My phone is currently rooted with Z4Root 1.3. Is there an easy way of doing this?
Sam
Use the d3 root method. Works fine.
CM7GB-601
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I have the phone in PC Mode (instead of Mass Storage.) I don't know if that makes a difference.
The D3 Method worked great for me and my wife's phone.
Hi everyone,
I have the same question as CSSZiegler, but want to expand on it a little bit...
I have a Droid 2 that was rooted with Z4Root 1.3 several months ago. I also have SetCPU, SuperUser and Titanium Backup. No custom ROMs installed. Big Red just pushed down GB, and of course, I've lost root access. I'd like to regain root again without losing any contacts, Handcent messages, etc. I've read on several forums that the D2 can be rooted just like the D3 with a simple "one-click" operation referenced by quarky42 earlier.
Any opinions or experience with this? I greatly appreciate any and all assistance!
update
My phone downloads the update, I click install now... it reboots and starts the install, then about 35% of the way through, it turns to a triangle with ! Inside. Phone reboots and displays message software update failed. Anyone know where to find a logfile or have any suggestions?
Droid2 android 2.2.. rooted. No custom rom.
Did you fully SBF to stock using RSDLite?
Also http://forum.xda-developers.com/showthread.php?t=1246673 has a flashable version.
I will as soon as I get a computer again, thanks for the link. Unfortunately my mobo died yesterday. So I was hoping for an alternative solution. It would also be nice to keep all my texts.. I'll google that one.
So any ideas on the logs or an alternative solution?
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
Ardalee said:
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
Click to expand...
Click to collapse
I answered the thread you started with the process to un root and put your phone back to stock.
acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
Awesome! That did the trick, thanks for the info
808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
I would SBF back to Froyo with RSDLite and install the OTA GB from phone info updates. After that use the D3 one click root method and you're golden.
droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.
acavallini said:
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.
Click to expand...
Click to collapse
I searched the phone's sd card.. I couldn't find it... do you know where adb.exe is located?
The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.
idefiler6 said:
The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.
Click to expand...
Click to collapse
Finally got it to work... now.. I used motorola one click root.exe where you use the exe on the computer. Just out of curiosity, is there a one click method to unroot? Thanks!

[q] help needed on 6.2.1

Hi all,
I got my KF few days back, Rooted it, before I could install the android market, got forced update to 6.2.1. 2 days ago saw this new root method using BurritoRoot. Tried rooting it, seems successful, however, now when I arrived at the home page, I cant even open the Superuser app at all. It goes the same for the Root Explorer - prompting:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on. Click ok and restart the app and try again. Make sure u respond correctly to the Superuser prompt." Then it comes with a force close.
Seriously I do not know whats wrong with it, now i cant even use the root explorer for me to install Android Market.
Anybody can help me with it?
Million Thanks.
did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033
b63 said:
did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033
Click to expand...
Click to collapse
Im using the ROOT INSTALL - Method 1 and I downloaded the file from Rootzwiki, apparently the file is named "com.noshufou.android.su-1.apk". and I used the following commands:
adb root
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
So which means I should use the Superuser -2.apk instead?
What should I do now? Download the Superuser-2 file and repeat the whole process again???
thanks.
yes - the new version seems to be the only one working with burritoroot
consider to use KFU to make things easier:
http://forum.xda-developers.com/showthread.php?t=1399889
should be option 2 (permanent root with superuser)

how to allow root for apps?

I have a nvidia shield tv with full android 6.
adb root and and adb remount is working, so I have root access on shell level.
Also I have /system/xbin/su which goes into root if I do not use "adb root".
But root for apps does not work. No app gets root access, RootChecker says "no".
I installed Superuser.apk but this did not help.
What is missing?
I see that this:
java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
Caused by: java.io.IOException: Permission denied
I saw that RootChecker tells me "SELinux enforcing", is this the problem?
I do not want to download any ready-made root miracle and flash the whole device.
Since I have adb root, I can adb push everything.
Just flash su.zip and all will be fine.
I don't need SuperSU. I want to root my device i.e. that apps can execute su.
I have /system/xbin/su but it seems that apps cannot use it.
SuperSU is required to give root access to apps, even with full Android. You will need to flash the zip file from TWRP recovery.
How does SuperSU work?
As far as I understand, there is a /system/xbin/su which is called by apps wanting root access.
This su binary then starts the app to verify access. Right?
Not sure, but I think that su is just for adb and maybe system apps.
On my system I have "adb root" access. But apps do not have root access, I do not have supersu or su.

Categories

Resources