So, in my journey of rooting, upgrading, attempting to root again, failing, unlocking, flashing, etc, I'm wondering if my observation directly relates with why root works for some people after the upgrade, but others who seemingly do the same thing have a "half" root, meaning, apps no longer have root access, but you can still get it via ADB with a "adb shell and then su - root"
My quick and dirty story is:
I was on ICS .30 all lock and stock, and rooted, using debugfs method...
I took the update to JB
Everything seemed OK until I did a data wipe to resolve a looping problem
After that, I had "half root" and couldn't get it back to where apps had access to it, despite the fact I backed up with OTA rootkeeper...
Here is my guess - my superuser install was NOT in the /system/app directory. I installed straight from the market, and it worked just fine on ICS, but when JB came out, and permissions, particularly to /data were redone, it broke me.
However, others used different methods for getting superuser into their device. I'm wondering if those that had no trouble at all had superuser installed in /system/app, and survived the OTA, while people like me did not.
I did try to simply move the suerpuser.apk to /system/app after making the mount read-write, but it gave some kind of "cross link" error and refused. Anyway, perhaps someone will read this prior to update and take precautions, and perhaps survive the OTA.
i'm guessing that you didnt have 'OTA Survival' checked in the superuser settings.
rickykemp said:
i'm guessing that you didnt have 'OTA Survival' checked in the superuser settings.
Click to expand...
Click to collapse
Can't remember but certainly possible.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Can't remember but certainly possible.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
do you have a binary in /usr/we-need-root i had to run that binary via adb to get UID0 and than re mount /system/ partition as RW vs RO and copy the same binary there to /usr/sbin/su
I am still on ICS. I rooted with debugfs. Root check came back successful last night. now I have a half root today.
---------- Post added at 03:15 PM ---------- Previous post was at 03:09 PM ----------
And I have a 300TL so I cant switch out my ROM version because I dont want to loose the LTE driver. I just need to root to get Ubuntu running on it.
I had similar problem. had root for every app until i removed the app. installed apps kept root but could not install any new apps with root. had to manually update the su binary. fortunately i still had root with es file explorer and could copy it into system/bin.
i was locked and stock rooted.
Sent from my ASUS Transformer Pad TF300T
if I re-run debugfs, it goes all the way through. and gets root remotely.[frustrated]
And to top it off, since I have a 300TL, the firmware is an oddball build. 9.44.45.3
---------- Post added at 04:20 PM ---------- Previous post was at 04:03 PM ----------
root OTS keeper says that the device is rooted, but that the app can't gain root access. No other root checker app even gets that far. WTF?
Reilly1812 said:
I had similar problem. had root for every app until i removed the app. installed apps kept root but could not install any new apps with root. had to manually update the su binary. fortunately i still had root with es file explorer and could copy it into system/bin.
i was locked and stock rooted.
Sent from my ASUS Transformer Pad TF300T
Click to expand...
Click to collapse
i'm in the same situation as you, can you help me and and let me know which files need to get copied and from where to where? the help is appreciated.
my searches turned up this thread -> http://forum.xda-developers.com/showthread.php?p=34197309
follow the first post. perform the download of the su binary. extract it. it creates folders and stuff you don't need. just copy the su file and paste it on top the the existng su in system/bin. make sure the permissions are as the post indicated.
root notifications and prompts for root access should start working again.
this process works if you have at least one app that will give you root. I always have system mounted r/w in es file explorer so that's not an issue.
good luck!
Sent from my ASUS Transformer Pad TF300T
If you have an existing such in system, you should be able to access root via adb. Simply type such at a prompt and you'll get a # prompt, meaning root.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
if you can log as root in adb shell why dont just push su executable and chmod +x it manually from it?
Su binary need suid excate bit, means chmod 04755 /system/bin/su
Sent from my GALAXY Cooper
NixZero said:
if you can log as root in adb shell why dont just push su executable and chmod +x it manually from it?
Click to expand...
Click to collapse
If my memory is correct, when I tried to copy files into system I received some type of link error and it didn't copy. Can't hurt to try.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Reilly1812 said:
my searches turned up this thread -> http://forum.xda-developers.com/showthread.php?p=34197309
follow the first post. perform the download of the su binary. extract it. it creates folders and stuff you don't need. just copy the su file and paste it on top the the existng su in system/bin. make sure the permissions are as the post indicated.
root notifications and prompts for root access should start working again.
this process works if you have at least one app that will give you root. I always have system mounted r/w in es file explorer so that's not an issue.
good luck!
Sent from my ASUS Transformer Pad TF300T
Click to expand...
Click to collapse
This hasnt really helped me... i even rebooted after, still no dice. Notifications work now but is always a denied notification unless it's those apps that had it before.
Edit - and now root explorer won't mount system as R/W
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Related
Is anyone else in the same boat as me, where they updated prior to instructions reading to move SU to xbin????
I have the SU in my app drawer, I have loaded setcpu and other root programs like barnacle, but I CANNOT for the life of me get the other half of the root apps to work because it says I DO NOT have SU permissions.... like Root Explorer for example.
I wouldn't mind sbf'n it back to 2.1 and then back to 2.2 again at all, just not quite sure what to do.... an ideas?
I was in the same boat as you after upgrading to 2.2 even though I thought I did the xbin step correct, guess not.
Anyways, the only way I fixed it was to completely flash my phone, I didn't mind doing this because it's always nice to start with a fresh install.
This guide was the best for me, simple and includes all necessary links.
http://forum.xda-developers.com/showthread.php?t=758907
Make sure you have busybox installed. There is an appliaction in the market that will download it..
Sent from my DROIDX using XDA App
If you didnt move su to xbin, you will HAVE to sbf your x and redo everything to get 2.2 with root. Thats what happened to me.
I did this also...half root and stuff. I used astro to install the su apk off my sd card. I didn't have the ninja guy in my app drawer though. But could run set cpu. Not root explorer. I just again installed the su apk from sd. And it showed up in my app drawer. And I was able to install root explorer. Just my 2's
Sent from my DROIDX using XDA App
A fix without adb
To anyone that has run into this problem I have a solution. This is for everyone that missed the step on keeping your root access. If you have su in xbin and still won't work this will work for you.
(Open terminal emulator) type the following:
/system/xbin/su
Then you should see a #
Run "mount -o rw,remount /dev/block/system /system"
Run "mv /system/bin/su /system/bin/su.bak"
Run "cd /system/xbin/"
Run "cp su ../bin/"
Then you should have your root access again!
and one more thing, don't type the word run or put the " " in this code
Same thing happened to me as well, I SBF'd back the first run and did everything EXCEPT the moving su to xbin, and well.... I had to do it all over again, took a bit of time, but now root works again.
Chris
I (without heeding the warnings) decided it would be a good idea to delete certain apps (including Hero of Sparta, Lets Golf, etc.) once I got my tablet rooted. Luckily, there are two A500's in my household, so I was able to copy the /system/app directory from the other untouched tablet.
Problem is, I can't seem to copy the directory (or any apps from it) into my tablet. I've used both ASTRO and File Manager HD, but in both, the 'paste' command is greyed out. It's as if I don't have the necessary permissions.
So, what's going on?
did you set the Read-Write permission on that directory?
Post removed
No, thanks for the reminder.
Upon attempting to edit permissions, though, using a terminal emulator, I get an error after typing this:
Code:
su
cd /system/app
chmod 777 /system/app
And the error I get is:
"Unable to chmod /system/app: Read-only file system"
Zen_Jackal said:
No, thanks for the reminder.
Upon attempting to edit permissions, though, using a terminal emulator, I get an error after typing this:
Code:
su
cd /system/app
chmod 777 /system/app
And the error I get is:
"Unable to chmod /system/app: Read-only file system"
Click to expand...
Click to collapse
Silly question, but do you have your system rooted?
Yes, I do. Using GingerBreak as I'm still waiting on that 3.1 update
Zen_Jackal said:
Yes, I do. Using GingerBreak as I'm still waiting on that 3.1 update
Click to expand...
Click to collapse
OK, then try a file explorer like Root Explorer and you should be able to set the rights ro R/W and copy your files over.
Root Explorer worked like a charm. I'm suprised File Manager HD doesn't perform those functions. I got a good feeling when I saw that Root Explorer was requesting superuser permission.
Zen_Jackal said:
Root Explorer worked like a charm. I'm suprised File Manager HD doesn't perform those functions. I got a good feeling when I saw that Root Explorer was requesting superuser permission.
Click to expand...
Click to collapse
Glad to hear that worked. Root Explorer is what I use. Have been for over a year. I think File MAnager HD can also do it, but it is not as straight forward ad Root Explorer. Have fun.
BTW the permission setting 0777 means anyone can access it (or any other application), for the sake of having a better security the permissions should be changed to 445 so only root can access and execute those files (I'm not sure if APKs are considered excutables if they are not the 444 will be the right setting)
Sent from my A500 using Tapatalk
AndroidPolice has the downloads and instructions for a new method of rooting. Just tested it, it *does* in fact work.
You will need ADB access (which, if you've rooted before, you probably already have).
I can confirm this works.
Is there any reason to do this if we are still rooted and have the secured rooted ROM installed? Should I wait until/if Amazon pushes the updated on top of my rooted 6.2.1?
Noob questions: Assume that the app goes on the KF of course. Where do the Superuser files get placed? Already have Superuser on the KF from previous root so can I skip this step?
Thanks!
cant find the drivers for my kindle??????? need help
i keep getting devce not found.....
movieaddict said:
cant find the drivers for my kindle??????? need help
i keep getting devce not found.....
Click to expand...
Click to collapse
I am not sure if we are talking about the same thing but I think they are included in the Kindle Fire Utility.
Masssy said:
I am not sure if we are talking about the same thing but I think they are included in the Kindle Fire Utility.
Click to expand...
Click to collapse
run install_drivers.bat from Kindle Fire Utility 0.6
Nice. Just regain root for 6.2.1.
did that , nothing
Not working here. Noticed that when I hit Root on the new app on the KF, I get this info which was not in the directions. Anyone else? Should these steps be done and in what sequence combined with the published instructions?
Final Steps
On your computer run the following commands:
adb kill-server
adb root
adb shell
Enjoy.
Hellcat6 said:
Not working here. Noticed that when I hit Root on the new app on the KF, I get this info which was not in the directions. Anyone else? Should these steps be done and in what sequence combined with the published instructions?
Final Steps
On your computer run the following commands:
adb kill-server
adb root
adb shell
Enjoy.
Click to expand...
Click to collapse
only one not in the instructiosn was adb kill-server and its not really needed.
adb root <-- what you likely missed
Root was made (I guess...).
But I still can't install the market. Because I can't mount system to R/W (with root manager or kindle utility).
Is it normal? :/
Cholo981 said:
Root was made (I guess...).
But I still can't install the market. Because I can't mount system to R/W (with root manager or kindle utility).
Is it normal? :/
Click to expand...
Click to collapse
root explorer mounts the system in r/w just fine.
this root works as advertised
ota rootkeeper still works for a temp unroot to watch amazon video.
as far as i can tell everything is the same except we're using superuser app so you have to allow each app permission, it's the only real change i can see
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
jcase said:
only one not in the instructiosn was adb kill-server and its not really needed.
adb root <-- what you likely missed
Click to expand...
Click to collapse
i needed to use the kill-server command to get my computer to pick up the kindle after the update... others may as well so it's good info
screwyluie said:
root explorer mounts the system in r/w just fine.
this root works as advertised
ota rootkeeper still works for a temp unroot to watch amazon video.
as far as i can tell everything is the same except we're using superuser app so you have to allow each app permission, it's the only real change i can see
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
i needed to use the kill-server command to get my computer to pick up the kindle after the update... others may as well so it's good info
Click to expand...
Click to collapse
Thanks for the suggestion re: OTA Rootkeeper! Rooted earlier today, but had trouble unrooting to watch videos, and now that's solved!
I haven't got my fire yet but these instructions don't seem very clear; do I have to keep the tablet connected to the PC at all times? Or do I execute the sudo app on the tablet, and then connect it to the PC so I can run the adb commands?
screwyluie said:
root explorer mounts the system in r/w just fine.
Click to expand...
Click to collapse
I meant root explorer (I wrote root manager indeed).
If I click on the "mount R/W" button, it doesn't do anything. :/
EDIT: Done. I had to push vending.apk by adb... dunno why.
jcase said:
only one not in the instructiosn was adb kill-server and its not really needed.
adb root <-- what you likely missed
Click to expand...
Click to collapse
Working now! Figured out that when installing the script in ADB from the directions, I was not leaving a space before each instance of "/system". Duh. Got Market working again as well. Thanks Developers!
Hellcat6 said:
Not working here. Noticed that when I hit Root on the new app on the KF, I get this info which was not in the directions. Anyone else? Should these steps be done and in what sequence combined with the published instructions?
Final Steps
On your computer run the following commands:
adb kill-server
adb root
adb shell
Enjoy.
Click to expand...
Click to collapse
You need to finish the job with these steps (taken from the androidpolice post):
Code:
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
Help! I'm stuck at this step:
adb install com.noshufou.android.su-1.apk
The prompt says it can't find the file. What am I missing?
Thanks!
---------- Post added at 04:47 PM ---------- Previous post was at 04:01 PM ----------
I think I figure it out. The Fire is rooted again. I just need to fiddle with OTA Rootkeeper to be able to watch video streaming again.
Thank you for this thread.
I can run all the steps i just gotta be able to remove the original superuser app that i had before this one. Can someone please tell me how to go about this.
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)
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