Ive successfully rooted my kindle(twice), verified through root checker, but when I downloaded busybox( stericson) and double checked for root I get and error message. I did not know this was the original issue the first time. I ended up unrooting and rerooting. The second time the first thing I did after initial root check was to install busybox and this is how I know that is the issue. The main reason I need it is so I can use ad-hoc switcher to tether. I tried other versions of busybox installer but they wouldn't download. I'm looking for an alternative to unrooting and rerooting, but I will if I have to. Also, a busybox installer that works and doesn't unroot my kindle would be nice. The error is as follows:
Superuser Application status: ...installed.
System file
properties for root access: alternative location check command: ls-l/shin/su:
Result: /shin/suermissions restricted and denied access
Standard location
check command: ls-l/system/bin/su:
Result: lrwxrwxrwx root root 2011-12-29 8:52
Su->/system/bin/busybox
Analysis : file:/system/bin/busybox
Alternative location
check command: ls-l system/shin/suck:no such file or directory
Analysis: file /system/chin
Adb shell default User:
Adb shell setting for standard access, stored in default.prop, is configured as: shell(non root) User -to.secure=1
(I did try to access these files to see if I could alter them and it would not let me into them.)
And thanks to all the great help and guides that have helped me root my devices.
Sent from my Kindle Fire using xda premium
read this thread:
http://forum.xda-developers.com/showthread.php?t=1359600
at the end there are all nessesary things for a successful thetering including download sources
good luck !
I will try to download busybox differently next time but that doesn't change the fact that my device is now not showing that im not rooted and I don't know how to undo what busybox did to my settings. Do I need to unroot and reroot or is there an easier fix.
Sent from my Kindle Fire using xda premium
the question is how did you root ? temporary or permanent ?
i recommend the KFU for such stuff - it makes it a lot easier
if you'r rooted permanently with superuser then everything should be ok
as you suggested i would try to unroot and root permanent with KFU
then you can decide to uninstall your busybox version or not and try an other version
I rooted permanent via kfu. Will unroot and reroot again and see if I can make it work this tome. Thanks.
Sent from my Kindle Fire using xda premium
Related
So, I'm rooted. S=OFF, I get su access in Terminal, and I have the latest busybox installed in /system/bin. But, after a reboot of the device I can only get R/W access to certain parts of the directory structure - /system is unfortunately not one of them.
Now, here's the weird part: When I start the app Busybox Installer (downloaded from the market), the app searches for busybox installations and tells me I have the latest in /system/bin (this I already know). Once I have started this Installer without doing anything else, I can gain full R/W access to /system.
So, there seems to be some sort of strange busybox issue and how it relates to system R/W access. Is the latest busybox incompatible with this stock ROM?
Root explorer issues
I am also having the same issue I can not get R/W access in the system folder. I have been trying to re-map the Genius button. I am able to remove "bloatware" by using Titanium backup. I definitely have permanent root on the phone, so I am confused by this issue. I have been searching and have not seen other similar complaints. I tried the busybox from the above post but still am not able to R/W access.
You need the latest version of root explorer. Will solve the issue.
Sent from my HTC Glacier
Hi
I have rooted my Fire with zergRush and confirmed with adb shell
Code:
# id
uid=0 gid=0
but after rebooting the Fire it seems to have gone as the prompt returned to $
Is this usual?
I'm on a MAC and the Fire is 6.2. I can root again but obviously it would be good if it remained after a reboot.
Any help would be much appreciated
edit: but now I'm not so sure.. SU from adb shell returns 'not found' and when running a terminal app I have on the Fire the prompt is $ and SU returns 'permission denied'.
I'm not really one who should answer this as I'll not really up on the different exploits used for rooting but...
My understanding was that zergRush got you a temporary root which was enough to enable you to remount /system as RW which then let's you install su and busybox and the superuser.apk which then gives you permanent root.
Sent from my Kindle Fire using Tapatalk
Like bsoplinger said,
zergRush is the exploit most are using to gain root, and then while having root allow you to install tools which survive the reboot cycle to continue to provide root from that point on.
Busybox, su and superuser are those tools.
Thanks very much, certainly gives me more to go on although I'm a bit confused as to when I should be installing tools using adb and when I should be using a file manager. Probably neither and I have the wrong end of the stick no probs.. on on
edit: I think I've got it... can't thank you enough your advice has saved me hours I'm sure but I will wait till the morning. I'd rather brick it with a fresh head than the one on my shoulders now.
The method is similar to the original Root tutorial before but with help of kindleroot_androidpolice.apk released from http://www.androidpolice.com as more obstacles in 6.2.1.
1. Download kindleroot_androidpolice.apk
http://www.androidpolice.com/2011/1...on-kindle-regardless-of-its-software-version/
2. Copy kindleroot_androidpolice.apk to your Kindle Fire device and install it.
3. Run it! Click Agree > You Rock > Root
4. Now you can connect your Kindle fire to your PC with USB line.
For the Windows System:
Start > Run > CMD
Code:
cd C:\Program Files\Android\android-sdk\platform-tools
(I installed the SDK by default so you can see my directory above that way)
If you installed your SDK to C:\Android then you should
Code:
cd C:\Android
If you download some guy's package for ADB and unzipped it to C:\adb, simply you should enter command
Code:
cd C:\adb
5. Download the latest version for SuperOneClickv2.3.2-ShortFuse from official site http://shortfuse.org/?p=171
Unzip the package and Run SuperOneClick.exe
Click Root Button
Unfortunately you will find that the commands will stop at WaitForDevice.
What should we do now?
6. Don't be panic! Just Run these lines in your command window:
Code:
adb root
adb kill-server
adb remount
Everything is okay now and the commands will be continued to END
Root completely
You can check SuperUser working well again on your KF
Screenshot images and package files are post in a Chinese Kindle Fire Forum, just check them at:
http://www.92kindle.com/thread-2905-1-1.html
Damn I think I'm gonna try that after installing 6.2.1 but it better work.
Sent from my Kindle Fire using Tapatalk
Anyone tried this method yet and can confirm that it works?
The method on androidpolice works. I am running 6.2.1 rooted right now!
Course BurritoRoot works, with a name like that it has to
edit
trollololololol
Actually this method works better. There seems to be a problem with the su program on androidpolice. It gives root alright but some programs don't get root access for some reason. SuperOneClick works better.
jlocohustler said:
Actually this method works better. There seems to be a problem with the su program on androidpolice. It gives root alright but some programs don't get root access for some reason. SuperOneClick works better.
Click to expand...
Click to collapse
i dont know if u read! but superoneclick was broken after last update, and jcase was nice enough to root this blindly so we could root !!!
jlocohustler said:
Actually this method works better. There seems to be a problem with the su program on androidpolice. It gives root alright but some programs don't get root access for some reason. SuperOneClick works better.
Click to expand...
Click to collapse
SuperOneClick can not root 6.21. Hence the use of BurritoRoot in the OP.
Methods to gain root are the same, since they use the same app to do it.
There was a problem with the su binary on AP but its been replaced.
I can verify the Android Police method works just fine without the SuperOneClick. Triedit twice, rooted then unrooted so I could watch Prime Video, then rerooted so I can install OTA Rootkeeper so I could watch video without unrooting. Only difference for me was I had SuperUser already from my pre-6.2.1 root but its the same as the the one AP distributes.
FYI my computer is a Mac so this was executed from shell.
Ibis, can you give me some more information on how you did this on a Mac?
I tried and it seemed to work but don't think it took as I cant copy the framework Apk to system/apps and when I try to run market it force closes with a vending error.
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)
I have Samsung Intercept from Sprint with Android 2.1, locked. Tried to root it with SuperOneClick 2.3.3. It seems device is rooted (it is not failed during the rooting, and Root Checker shows phone is rooted). SuperUser was installed.
su in /system/xbin
remounting system with read only access
I used simple Root and not Shell Root. I installed Titanium Backup but was unable to start it. I've got the following error:
Could not acquire root privileges. This app will not work. Verify rom is rooted. Attempt was made using /system/xbin/su command.
In Titanium: Root access failed.
So, it seems I'm able to install non-market app but unable to run it, because SU failed to recognize it.
How to root this phone in a right way? Should I unroot it and make Shell Root? Will this unlocked the bootloader? Would this affect the wifi and other phone functions? If the system was mounted with read access only how to get write access rights?
Thank you for your suggestions
I was able to apply temporary root by InterceptRoot software. Unfortunately, permanent root on my device doesn't work.