Database Info

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.

Root was succesful, superuser is installed, but I don't have Root access.

I rooted my Motorola Charm with superoneclick 1.7, or atleast I thought I did. superoneclick 1.7 did say the rooting was succesful and I have superuser installed.
But when using Link2SD it says I didn't have root access. So I checked with Root Checker and apparantly Link2SD is correct. This is what Root Checker has to say:
Root Access is not properly configured or was not granted.
Alternate su binary location:
/sbin/suermission denied
SU binary not found in the system delcared PATH
Does anyone know what could be the issue? And if not, then would anyone know what is the safest way to proceed from here? I already have superuser and superoneclick says it is Rooted, I'm not sure what would happen if I were to root it again.

I had the same problem with my Milestone, rooted it using AndRoot. I used Superuser to update the su binaries, but still nothing. Then a simple reboot fixed it

My Milestone2 rooted successfully by SuperOneClick 1.3 ,
you can use the 1.3 version to root

milest0ne2 said:
I had the same problem with my Milestone, rooted it using AndRoot. I used Superuser to update the su binaries, but still nothing. Then a simple reboot fixed it
Click to expand...
Click to collapse
Edit: after a second reset it worked! Thank you very much!

[Q] problem With SU in CM9 beta 2

The Root Apps such as No-frills, Root explorer does not Prompt for SU permission therefore I am unable to use them
I used basic root checker to check root access it says "your device is not rooted"
I went to SU app to check for apps if they were denied the permission
But there no Apps in the LOG list...
I tried reflashing the ROM twice dint worked
I had flashed this over Creed's ROM 1.6 ?
Please help

[Q] Is a Partial Root possible?

Please excuse me if this has been covered elsewhere but I have done a search and can't find anything that applies to my Transformer or the problem I have.
I used Razorclaw to root my Transformer when it was on Honeycomb, and Voodoo OTA rootkeeper to retain it when I upgraded to a later version of HC. And then again when the first ICS update came out. However when the .17 OTA came out, in my haste to try and fix the problems that came with the first ICS update, I hit 'install' without thinking. I should have made sure voodoo had a fresh backup and temporarily unrooted the TF (as I had done on previous updates).
So after the update I checked with both Titanium Backup and Voodoo which indicated I did not have root. I selected the 'restore root' option in Voodoo and it then indicated I had regained root access.
So now the three apps that I had granted root access prior to the upgrade (Titanium Backup, ES File Explorer and Voodoo) still have root access, but whenever I try a new app that requires root it says I don't have root. And checking in Superuser the 3 apps above are listed as allowed, but no other requests are even logged.
So my question is how can I have some apps that require root working, yet new requests are denied? And is there a simple way to fix it? I don't want to uninstall Superuser in case that loses me root completely (and permanently) and when I try to update Superuser it fails to gain su and stops.
Edit:TF is running Stock firmware, just rooted.

Look to see if you SU in system/xbin if not look in system/bin and copy SU from there to system/xbin

baseballfanz said:
Look to see if you SU in system/xbin if not look in system/bin and copy SU from there to system/xbin
Click to expand...
Click to collapse
This did not fix it I'm afraid, but thank you for your suggestion. It's almost like Superuser is frozen and won't allow anything else root access. I see there is a 'Superuser Update Fixer' App on the Market (oops I mean Google Play Store) but I'm not sure if that will solve the problem I have as it seems to require root access to work...

dingbatt said:
This did not fix it I'm afraid, but thank you for your suggestion. It's almost like Superuser is frozen and won't allow anything else root access. I see there is a 'Superuser Update Fixer' App on the Market (oops I mean Google Play Store) but I'm not sure if that will solve the problem I have as it seems to require root access to work...
Click to expand...
Click to collapse
Try running ViperMod (option 1) again to get full root.

dingbatt said:
This did not fix it I'm afraid, but thank you for your suggestion. It's almost like Superuser is frozen and won't allow anything else root access. I see there is a 'Superuser Update Fixer' App on the Market (oops I mean Google Play Store) but I'm not sure if that will solve the problem I have as it seems to require root access to work...
Click to expand...
Click to collapse
I don't think you have root. I had same thing happen, literally almost exactly and its because I did not have proper root. Use vipermod to get root back and you'll see everything will work like normal
Sent from my Transformer TF101 using xda premium

Thank you both baseballfanz and eminembdg (I pushed the thanks button) Vipermod Option 1 did the trick. I now have full root access restored. The biggest problem I had was I couldn't find any Win7-64 ADB drivers so had to go and pull the old Win7-32 laptop out to get everything to work properly.
Still can't see why I had partial root permissions though. I thought it was all or nothing. Kind of like being a bit pregnant.

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.