For some reason even after using each subsequent one click root method, including the latest andromeda flasher, I cannot install Busybox. It says that the phone is either not nand unlocked or isn't rooted. I also cannot use remount in adb as it says it is not found. Any ideas as to why?
sporkisfaster said:
For some reason even after using each subsequent one click root method, including the latest andromeda flasher, I cannot install Busybox. It says that the phone is either not nand unlocked or isn't rooted. I also cannot use remount in adb as it says it is not found. Any ideas as to why?
Click to expand...
Click to collapse
The only way I have found around this myself is to go back to stock kernel. Then install the Joey 2.2.4 root exploit install not the noobl kernel and then install the latest busy box .... and superuser
Try installing titanium backup, open it, hit problems and install busy box from there.
Aridon said:
Try installing titanium backup, open it, hit problems and install busy box from there.
Click to expand...
Click to collapse
This seemed to install busybox inside of TiB so thats good. Also I already have superuser. Everything about the root seems to work ok however trying to remount in adb still is a no go.
Copy and paste your console here so we can take a look at it
Aridon said:
Copy and paste your console here so we can take a look at it
Click to expand...
Click to collapse
How do I console? Sorry a bit of a nub when it comes to stuff like that.
That is to say, what exactly do you want to see? My cmd prompt or something on my phone?
Related
Once you have achieved root (see other thread), to update the Superuser.apk to the latest version, run these commands:
Code:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /system/app/Superuser.apk
pm uninstall com.noshufou.android.su
Then search on the market for Superuser and download the one by ChainsDD. Confirmed working on latest Droid2 2.2 ota.
EDIT: To be safe, go to Settings>Applications>Manage Applications and find Superuser. Then clear the data. This should prevent any of the Superuser issues discussed.
sorry..new to the whole android scene. are there any advantages to updating the superuser app the the latest version and can this command be input on the droid itself through the terminal app?
metman87 said:
sorry..new to the whole android scene. are there any advantages to updating the superuser app the the latest version and can this command be input on the droid itself through the terminal app?
Click to expand...
Click to collapse
i like the interface much more and its got a new autoaccept after 10 seconds if you arent paying attention when the popup shows. it's up to you. i'm sure future root tools will just include it.
alright thanks. is it as simple as installing the new version and uninstalling the old? or does one need to enter the command prompts listed above?
metman87 said:
alright thanks. is it as simple as installing the new version and uninstalling the old? or does one need to enter the command prompts listed above?
Click to expand...
Click to collapse
that is what the commands do. unfortuantely, the old version is on the system partiton. this means that we must first mount the system and read/write and then manually delete the old version ourself. then the new version can be easily downloaded through the market. anyways, adb shell means it's done via your computer so its very easy to copy and paste like 3 commands.
Instructions work perfectly... thanks!
I need Mac instructions
Sent from my DROID2 using XDA App
greg25 said:
I need Mac instructions
Click to expand...
Click to collapse
These instructions are not specific to the OS on your computer, they work with anything.
Perfect!
Worked great! Thank you!
Instructions worked fine (I just made them up for Linux), but the newest SuperUser is giving me weird results. Every program that requests root access will ask me numerous times, like it never remembers that I gave the app access. Like removing one app with titanium will it will ask me 4 seperate times to accept or deny permission. Other apps do this also. Anyone have a copy of the old apk I could reinstall? Anyone have any ideas or suggestions?
Thanks
n0yd said:
Instructions worked fine (I just made them up for Linux), but the newest SuperUser is giving me weird results. Every program that requests root access will ask me numerous times, like it never remembers that I gave the app access. Like removing one app with titanium will it will ask me 4 seperate times to accept or deny permission. Other apps do this also. Anyone have a copy of the old apk I could reinstall? Anyone have any ideas or suggestions?
Thanks
Click to expand...
Click to collapse
I had the same thing happen to me. Launch the new superuser app and go to settings. Unselect and reselect Notifications. Apparently it shows it being checked, but you have to recheck it for the actual setting to get saved.
After I did this, it only asks once for a program, and then I never see it again.
facelessuser said:
I had the same thing happen to me. Launch the new superuser app and go to settings. Unselect and reselect Notifications. Apparently it shows it being checked, but you have to recheck it for the actual setting to get saved.
After I did this, it only asks once for a program, and then I never see it again.
Click to expand...
Click to collapse
Nice, thanks!
I had that issue too. I ironically un-installed superuser and re-installed it and it worked fine too
I used Root Explorer to delete the old Superuser.apk from /system/app. Then I rebooted and installed the new version from the market. Worked great.
jmonte345 said:
I used Root Explorer to delete the old Superuser.apk from /system/app. Then I rebooted and installed the new version from the market. Worked great.
Click to expand...
Click to collapse
that works too though without having the superuser apk and rebooting, that could be a little dangerous for others hence my adb tutorial. no need for a restart either. could easily just use root explorer, delete the old, download new from market.
Worked great
I just renamed Superuser.apk to .bak then tried to install. Don't forget the last step. I had to adb (I was using terminal emulator) to do the last step then installed fine and removed Superuser.bak.
Thanks I like the New look.
yeah i can't get superuser from the market to install, keeps telling me unsuccessful
jerseyh22accord said:
yeah i can't get superuser from the market to install, keeps telling me unsuccessful
Click to expand...
Click to collapse
I had the same problem. I rebooted my phone and then it installed fine. Not sure if it's risky to reboot once you remove the apk or not. However, it didn't cause any problems for me.
jmonte345 said:
I used Root Explorer to delete the old Superuser.apk from /system/app. Then I rebooted and installed the new version from the market. Worked great.
Click to expand...
Click to collapse
I basically did the same thing except I renamed instead of deleting it. Well, once I installed SU from the market, I can't find the .apk file even though it's running and launching correctly. I assumed it would be called superuser.apk in the system/app folder but only my old renamed superuser.bak is there. I'm just worried if there is an update in the future, I won't be able to rename since I can't find the .apk file. Anyone know where the .apk file is for this new version of superuser?
facelessuser said:
I had the same thing happen to me. Launch the new superuser app and go to settings. Unselect and reselect Notifications. Apparently it shows it being checked, but you have to recheck it for the actual setting to get saved.
After I did this, it only asks once for a program, and then I never see it again.
Click to expand...
Click to collapse
Tried this, and it didn't work for me. With Titanium Backup in particular, it will literally ask upwards of twenty times for permission. It's insanely annoying. Any other tips?
Sent from my DROID2 using XDA App
Okay so I updated my Nexus S to 2.3.2 through ROM Manager, and when I tried to flash the Trinity kernel after I updated I ROM Manager said it was gonna shut down my phone to flash it, but it just sat there. Then I tried different functions in ROM manager, but I got "Error running privileged commands" (or something like that) I then checked Superuser and ROM Manager was simply not in the list. It did not say that it was declining access, but it also didn't say it was allowing. I decided that I would restore to my backup, but when I went into the recovery it was not the ClockworkMod recovery. It was the stock recovery, but I didn't have any options. At that point I decided to uninstall ROM Manager and install it again hoping it would ask for privileges. It did not.
Any ideas?
open ROM manager and flash clockwork recovery (the first thing on the menu)
When I try to do that I get "An error occurred while attempting to run privileged commands!"
Taquitoz said:
When I try to do that I get "An error occurred while attempting to run privileged commands!"
Click to expand...
Click to collapse
Sounds like you're not rooted.
If you're not rooted, the only way you're going to get into clockwork is to use fastboot.
I'm pretty sure that I'm rooted. I was running on Trinity prior to the update. And I still have Superuser.
Superuser apk doesn't necessarily mean you're still rooted with proper permissions.
At least check your /system/bin directory for the su binary (different than the superuser app) and that it has executable permissions.
You could also open a terminal app on the phone and just type su and hit return.
Okay so I downloaded a terminal emulator and typed 'su'
I got permission denied. Does this mean I have to root my phone again? If I will will I have to delete all data?
Taquitoz said:
Okay so I downloaded a terminal emulator and typed 'su'
I got permission denied. Does this mean I have to root my phone again? If I will will I have to delete all data?
Click to expand...
Click to collapse
Yes, it means you must root again.
No, you won't lose everything again if you follow these instructions: http://forum.xda-developers.com/showthread.php?t=931865
Good luck.
edit: you just need to get into clockwork (via fastboot) and then re-run the su update zip file, it will reinstall the su binary and fix any bad permissions.
Sorry for asking for the specifics, but could you explain how one could go about doing that?
Boot into fastboot.
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Boot to recovery.
Mount system.
Flash a zip from the SD card and select the superuser .zip.
Taquitoz said:
Sorry for asking for the specifics, but could you explain how one could go about doing that?
Click to expand...
Click to collapse
The link I provided gives step-by-step instructions on how to do it, and links to more complicated steps if you're not too sure about them.
The post just above this does give the basic steps, though.
I tried searching on the forum for a13 allwinners zeepad 7.0 but can't find anything.
I bought this from amazon,
Android version:
4.0.4
Model number:
A13MID
Kernel Version: 3.0.8
Can someone help me root this tablet?
Anyone? :|
Baoish said:
Anyone? :|
Click to expand...
Click to collapse
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
:good:
deeno33 said:
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
Click to expand...
Click to collapse
So, just install su and it will work?
deeno33 said:
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
Click to expand...
Click to collapse
My daughter just got one of these devices for Christmas, as well. I saw this post as well and thought "Great, I don't have to do the part" so, I installed SuperUser, when I went to update the su binary, which was shown as "Legacy" it got all the way to where it needs to remount the / file system as rw, and to my surprise, it wont remount. Another thing I noticed was that even though it does have su installed, I can't get to the point to where the app even asks for root permission. I tried to update Busybox, as well, and it wouldn't let me even do that... The version which is installed to the tablet appears to be 1.18, but when SuperUser goes to update the su binary it reports back as being the same as the installed version, which I know for a fact that it is not. So while I do in fact have root, it seems to only be a partial root. Anyone willing to throw around some ideas as to where I can go from here to A) get the / file system to remount rw, and B) get SuperUser, an updated su binary and an updated Busybox installed so that I can a full root going and get down to business to installing CWM and CM10 installed and running on here for her.
Any help would be appreciated,
Matt
Yes there is A Solution To This Via A Simple App
meskes said:
My daughter just got one of these devices for Christmas, as well. I saw this post as well and thought "Great, I don't have to do the part" so, I installed SuperUser, when I went to update the su binary, which was shown as "Legacy" it got all the way to where it needs to remount the / file system as rw, and to my surprise, it wont remount. Another thing I noticed was that even though it does have su installed, I can't get to the point to where the app even asks for root permission. I tried to update Busybox, as well, and it wouldn't let me even do that... The version which is installed to the tablet appears to be 1.18, but when SuperUser goes to update the su binary it reports back as being the same as the installed version, which I know for a fact that it is not. So while I do in fact have root, it seems to only be a partial root. Anyone willing to throw around some ideas as to where I can go from here to A) get the / file system to remount rw, and B) get SuperUser, an updated su binary and an updated Busybox installed so that I can a full root going and get down to business to installing CWM and CM10 installed and running on here for her.
Any help would be appreciated,
Matt
Click to expand...
Click to collapse
all zeepads come prerooted and shouldnt block u from updating or to have root access (download root checker) from market
Ur Binarys Should Still Update And Say Current If U Download New Binary Just Wont Show Up Till Reboot
If u Want To Stop This Error While Not Having To Reboot Everytime
Ya This IS Annoying to Do Everytime But Simple solution
THis Proplem IS Do To The Tablet Having A Stock Kernel That Doesnt Allow System Read/Write Access
This Is Why SuperUser Fails Cause It Needs Write Access To The Devices File System...(system/xbin/su)
Which means to Remount system after updating to take Affect And Most Stock Devices Do Not Allow This
so if u updated and it said current version ur ok this is to prevent anymore errors in the future
superuser can have different error witch mean different things just cuz u get one doesnt mean
they didnt take affect but remount of system is the most common error check superuser faq
1.Download Mount System R/W App From PlayStore And Install And Open.
2 .Allow Root Access To The App Then Select Mount System R/W Button
3. Press Home Button And Navigate To SuperUser App And Then Try Updating Binary
This Method Should Work For You
Hope This Works For You
As for cwm and cm9/cm10 it depends if u have a8 or a10 device a13 are not yet supported
MikeG_MG56 said:
all zeepads come prerooted and shouldnt block u from updating or to have root access (download root checker) from market
Ur Binarys Should Still Update And Say Current If U Download New Binary Just Wont Show Up Till Reboot
If u Want To Stop This Error While Not Having To Reboot Everytime
Ya This IS Annoying to Do Everytime But Simple solution
THis Proplem IS Do To The Tablet Having A Stock Kernel That Doesnt Allow System Read/Write Access
This Is Why SuperUser Fails Cause It Needs Write Access To The Devices File System...(system/xbin/su)
Which means to Remount system after updating to take Affect And Most Stock Devices Do Not Allow This
so if u updated and it said current version ur ok this is to prevent anymore errors in the future
superuser can have different error witch mean different things just cuz u get one doesnt mean
they didnt take affect but remount of system is the most common error check superuser faq
1.Download Mount System R/W App From PlayStore And Install And Open.
2 .Allow Root Access To The App Then Select Mount System R/W Button
3. Press Home Button And Navigate To SuperUser App And Then Try Updating Binary
This Method Should Work For You
Hope This Works For You
As for cwm and cm9/cm10 it depends if u have a8 or a10 device a13 are not yet supported
Click to expand...
Click to collapse
Sorry for bringing up an old thread, but I got the a13 and was wondering if anyone was making a cm9/cm10 rom for it as well. I have the a13. I tried to Google and can't find any info about any custom roms for this device.
I used kingRoot version 4.1 Any newer version would not root it.
Hi All,
I have screwed up my android which was perfectly fine with a perfect root. Please help me to restore the root access !!!
Here is my problem description:
I have a Sony Xperia Miro which was perfectly rooted.
Model : ST23i
Android : 4.0.4 ICS
Build : 11.0.A.5.5
The root verification using app 'root checker basic' was successful.
Now I had few of my company apps and bank apps which wouldn't work in rooted device. But I never wished to lose my root status. So I was searching for the ways to hide root access from these apps. I even came across apps exclusively built for this purpose (hidemyroot/OTA root keeper) But due to some bad comments about these apps, I decided to try manually
The idea was to fool the apps when checking the root access.
At first I renamed the super user apps at the location /system/apps. to some invalid file(super.txt)
This did the trick for couple of apps which weren't working before in my mobile. However couple of apps were still failing.
The next thing I did was renaming .su to ku in the below location /system/bin/.ext
Then I verified Root Checker Status, still it displayed "u have root access"
Then I went to /system/xbin and renamed the following.
.su to ku
.busybox to busyboxk
.dexdump to dexdumpk
Then I tried Root Checker Basic again. And got the message "device don't have proper root"
But still my apps were not working. Then I did the most foolish thing which was restarting the device.
BAM.. !!!! I lost my root access permanently. Now I don't have superuser app. And I m not able to use 'Root explorer', to rename back the files to its original state.!!! And most ironic thing is my company app still saying I have root access. I tried after deleting its cache and data. The result was same !!
How can I restore my root access ? Please help
one update
Since I renamed the superuser and superSu applications, I couldn't use them.
Today I installed both of them using package installer.
But they doesn't seem to work as they can't find su binary installed
See the attached
appviz said:
See the attached
Click to expand...
Click to collapse
Do you have a Custom Recovery setup and if so did you make a backup after root?.
keifus.rahn said:
Do you have a Custom Recovery setup and if so did you make a backup after root?.
Click to expand...
Click to collapse
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
appviz said:
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
Click to expand...
Click to collapse
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your device. The same thing happend to me awhile back :/ If you want to save your apps use titanium back up or app backup & restore and add a custom recovery like cwmr so if this happens agen you wont have to reroot. if you are still having problems with your apps for work boot your phone into recovery and go to advanced then fix permisions if you have any other questions or any problems just let me know.
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
keifus.rahn said:
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
Click to expand...
Click to collapse
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
appviz said:
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
Click to expand...
Click to collapse
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
keifus.rahn said:
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
Click to expand...
Click to collapse
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
appviz said:
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
Click to expand...
Click to collapse
That's Awesome :highfive: I'm glad the hear that you got everything working correctly and with your company apps too. :victory:
Thank you for sharing with me and everyone. You never know if some one out there is having the same problem and this could really help them out one day.
I tried to root this almost unbranded tablet (turbo x strike ii) with cydia impactor,it successfully pushed the busybox and su but there was no root access when i checked with root checker.
Then i tried to root with kingo, said it was successful but still no root.
Then i tried v root, said successfull as well, installed the chinese superuser but still no root access.
Can it be rooted or wipe it all out?
If i am to wipe it all out how can i do that with an unrooted unbranded tablet which i have no rom or the means to flash it?
It sounds like more trouble than is actually worth but any suggestions will do, thanks in advance!
Well it is half rooted I suppose, but you will have to go to /system/bin and if you see "su" its rooted. If not then you'll need to find a way to push a su file there.
TheArc said:
Well it is half rooted I suppose, but you will have to go to /system/bin and if you see "su" its rooted. If not then you'll need to find a way to push a su file there.
Click to expand...
Click to collapse
in /system/xbin there is a "su" file, but i can't push anything or even mount the system into rw with the "mount:read-only file system"error i get. thanks for the help!
So you actually have it rooted but its not working as its supposed to. Is there any recovery available for the device?
TheArc said:
So you actually have it rooted but its not working as its supposed to. Is there any recovery available for the device?
Click to expand...
Click to collapse
cwm doesn't support the device But i am able to boot into recovery from "adb reboot recovery" if thats what you meant, just tried it!
Why don't you try and re-root it using the same method.
TheArc said:
Why don't you try and re-root it using the same method.
Click to expand...
Click to collapse
I used another root method by flashing a zip from recovery, thanks for the help! But this other crazy thing is that despite being rooted and apps tha require permision work, i cannot remount the /system to get the play store there. I tried flashing gapps, tried with /system/app, root explorer, es explorer, mount /system, adb remount and nothing all i get is "mount:read-only file system". Any ideas?