Database Info

Anyone know how to know if charge is rooted

I downloaded terminal from market and ran su and said permission denied? any ideas?
I ran odin and rooted altered beast rom as well
Sent from my SCH-I510 using XDA Premium App

Do you have the Superuser app installed? The su binary requires this to work properly.

imnuts said:
Do you have the Superuser app installed? The su binary requires this to work properly.
Click to expand...
Click to collapse
when i read this i realized it wasnt but even after i installed it it still gave me the same problem on terminal, idk if it the actual rom that i installed or what?

first of all, did you root your phone? by any method? if you did, download titanium backup from the market, and when you open it, it will tell you that you dont have root access, press the problems? button, and it will prompt you with a box that has the option to get busybox, just press that button and most of the times this will fix this root permission issue

I lost root- perhaps thru flashing new recovery?

I rooted my Zoom wifi long ago. Flashed all the various Tiamat kernels and followed bigrushdog's 3.1 update with no problems. I recently flashed the CWR RC 4 over the updated 4.0.1 version in Rom Manager. I now see that all my apps requiring root don't work. I have Super user app but don't get the request to grant su anymore. I tried upgrading Super user within the app but it fails and writes a zip update to SD card which is supposed to be flashed through Recovery but doesn't (I suspect because the file is a 0 byte file!).
Any suggestions on how to get root back?
[Solved]: Seems it was a result of trying to upgrade Superuser that I lost root. See the last post below and the solution Almighty1 offers. It worked and I have root back......
Sent from my Xoom using XDA Premium App

tangiers said:
I rooted my Zoom wifi long ago. Flashed all the various Tiamat kernels and followed bigrushdog's 3.1 update with no problems. I recently flashed the CWR RC 4 over the updated 4.0.1 version in Rom Manager. I now see that all my apps requiring root don't work. I have Super user app but don't get the request to grant su anymore. I tried upgrading Super user within the app but it fails and writes a zip update to SD card which is supposed to be flashed through Recovery but doesn't (I suspect because the file is a 0 byte file!).
Any suggestions on how to get root back?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
There is a problem with the latest recovery version in Rom Manager. The recovery from solarnz is probably not at fault, but maybe the interaction of the two. You wil lneed someone with more knowledge than me to help you get root back, but this issue really needs attention. There are several updates to apps that seem to be breaking our Xooms, and there should be pinned warnings or the developers should be making everyone aware of these conflicts as soon as they find out. I had problems and I'm sure a lot of other folks have have problems with these incompatible app updates as well.

Thanks for that. It almost seems like Superuser is "degrading" in the sense that I had a number of apps reflected in the Superuser app as having been granted root (but not Rom Manager). However, I couldn't add new apps to it. And when I cleared Superuser data and reinstalled it, none of the apps that required root (and which had worked before) would work.
I also think that the writing of a 0 byte zip update file by the Superuser app indicates a problem.
I suspect the solution may lie with fastboot and re-pushing Superuser and CHMOD(?) file permissions but like you, I am nervous to play with these sort of things. My Xoom is working and until I have the need to change the ROM, root doesn't matter to me....

after reading this I checked and also had lost root. I had not checked after after flashing 4.0 in rom manger. Superuser was still there but my apps did not have access. I tried flash a new recovery, reflashing Tiamat nether worked. Anyway from adb
adb remount
adb push su /system/bin/
adb shell
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app/
I then rebooted and had root... updated Superuser as I had an older one in my platform-tools and all is well I then flashed the lastest recovery in rom manger and still have root.
Hope this helps

Thanks. I will give it a try this evening when I get back from work.
Also found this: http://forum.xda-developers.com/showpost.php?p=14643716&postcount=340 which seems similar to your solution.

This is why I hate CWR. I wish we had Amon RA recovery.

[Q] Rooted 2.3.4 Mesmerize; Now what...?

I'll try to keep this as short and simple as possible:
I am a total newb to the touchscreen, smart-phone, I just got a USCC Samsung Mesmerize SCH-i500, came installed w/ 2.3.4 Gingerbread & I just had to reflash it w/ USCC EH09 root using Odin 3 v1.85, now, everything I have "hacked" in the past (PSP (both fat & slim), iPod Touch, etc) I've always had to use step-by-step instructions (I am not a dev & know absolutely nothing about programming) & the same applies here.
So, it has root access & BusyBox (I don't even know what that is) installed, so my question is what was the point?
What exactly can/should I do from here? Any suggestions?

well, with a rooted android device you can
*remove bloatware (you're wasting your root if you don't do this)
*system-wide adblock (my personal fav)
*change boot animations
*flash custom ROM
*free wifi tethering
*overclock the CPU
and more!

Thank you for the answer, I'll look into these things but on a side note: my su app keeps saying that theres an update available for my su binary & every time I tap update it goes through the process & less than half-way through it pops up a message saying: "This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager."
I have tried to use ROM Manager, I even bought the Premium version, either way it gives me the same message, even after doing the Fix Permissions option, is there a way to manually allow su access to the files it needs to overwrite/update?
Oh, and, yes, I have allowed it when su asked, so now I'm at a loss....

Xeno Templar said:
Thank you for the answer, I'll look into these things but on a side note: my su app keeps saying that theres an update available for my su binary & every time I tap update it goes through the process & less than half-way through it pops up a message saying: "This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager."
I have tried to use ROM Manager, I even bought the Premium version, either way it gives me the same message, even after doing the Fix Permissions option, is there a way to manually allow su access to the files it needs to overwrite/update?
Oh, and, yes, I have allowed it when su asked, so now I'm at a loss....
Click to expand...
Click to collapse
I had the same issue today, couldn't update SU.
but after I had updated the terminal emulator, I was able to update SU.

Fixed the Problem with updating SU Binary
Recently updated my device with a new rom and was unpleasantly surprised to not be able to update my SU binary with either the application itself or CWM. I am not sure that this is the best way to handle the problem, but I found a solution that worked for me.
1. Open "System/XBin" in RootExplorer (or a similar app)
2. Mount the drive as R/W using the button up at the top left
3. Open the superuser app and update the binary from within the app
4. There may be an error in the log about the device not being able to remount the drive properly, but the update WILL occur.
5. Use RootExplorer to open the directory again and mount as R/O.
I hope this helps!

How do I root a13 zeepad 7.0 tablet?

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.

HELP changes in BUILD prop

Recently i added few codes into build prop of phone and after changes i installed busybox.
When i tried flashing SuperSU_v2.46 via TWRP,after rebooting system it again asks me to update SU binaries?
Did i do some steps wrong in busybox?

ssnanda0143 said:
Recently i added few codes into build prop of phone and after changes i installed busybox.
When i tried flashing SuperSU_v2.46 via TWRP,after rebooting system it again asks me to update SU binaries?
Did i do some steps wrong in busybox?
Click to expand...
Click to collapse
Any time you flash or install SuperSU, it always asks you to update su binaries the first time you open SuperSU after flashing it or installing it.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Any time you flash or install SuperSU, it always asks you to update su binaries the first time you open SuperSU after flashing it or installing it.
Click to expand...
Click to collapse
But before i tried to add and change with busybox, Super Su zip installs apps and does not ask to update binary.

ssnanda0143 said:
But before i tried to add and change with busybox, Super Su zip installs apps and does not ask to update binary.
Click to expand...
Click to collapse
Any time, and I mean, ANY TIME you flash SuperSU or install SuperSU, the first time you actually open the SuperSU app, it prompts the user to update the su binaries, this is a default action, it is SUPPOSED to do this. I've had to this on every device that I've ever installed SuperSU on and I've used it on many different devices.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Any time, and I mean, ANY TIME you flash SuperSU or install SuperSU, the first time you actually open the SuperSU app, it prompts the user to update the su binaries, this is a default action, it is SUPPOSED to do this. I've had to this on every device that I've ever installed SuperSU on and I've used it on many different devices.
Click to expand...
Click to collapse
But i never faced this update problem but after i tried changes with busybox and build prop this problem started.. I dont know what these files changed that affected Super SU..

Do i need to upload my zip file to check

ssnanda0143 said:
Here's the zip i am attaching with this reply
Click to expand...
Click to collapse
I'm trying to tell you that it isn't "a problem", it is completely normal. It isn't anything to be concerned about. It is doing exactly what it is supposed to do.
Sent from my LGL84VL using Tapatalk

https://drive.google.com/file/d/1-6PCt-NHTxBAySig4vlZ5Mp377BDD8iO/view?usp=drivesdk
This SuperSU Flash file whenever i used after reboot system from twrp recovery it never asks to update Su binary and reboot again

This SuperSU Flash file whenever i used after reboot system from twrp recovery it never asks to update Su binary and reboot again
Click to expand...
Click to collapse
But now its keep on asking so what mistake i did am unable to get.

ssnanda0143 said:
But now its keep on asking so what mistake i did am unable to get.
Click to expand...
Click to collapse
The only mistake you made is not allowing it to update the binaries when it asked. Just update the binaries and reboot the device and you're done.
Stop freaking out like something is wrong, it isn't. I told you, it is doing EXACTLY what it is supposed to do.
Do want to continue using SuperSU? If the answer is yes, update the binaries.
Sent from my LGL84VL using Tapatalk